[ SECRET POST #6336 ]

[case]

⌈ Secret Post #6336 ⌋

Warning: Some secrets are NOT worksafe and may contain SPOILERS.


01.



__________________________________________________



02.



__________________________________________________



03.
[DND, LOTR, Nope, The Thrilling Adventure Hour]



__________________________________________________



04.



__________________________________________________



05.
[Erma]



__________________________________________________



06.

















Notes:

Secrets Left to Post: 02 pages, 39 secrets from Secret Submission Post #906.
Secrets Not Posted: [ 0 - broken links ], [ 0 - not!secrets ], [ 0 - not!fandom ], [ 0 - too big ], [ 0 - repeat ].
Current Secret Submissions Post: here.
Suggestions, comments, and concerns should go here.

Comments

[fscom]

01. https://i.imgur.com/23mOo1f.png

[(Anonymous)]

Wait, so... you're complaining that your experience of a game is being tainted by the inclusion of something you haven't actually encountered in the game? Forgive me if I'm not understanding, but "it's not even a thing in the game" doesn't gel with "why did they have to include this thing in the game".

[(Anonymous)]

Not OP but it looks like the mention of that character being their childhood sweetheart IS in the game but the actual relationship isn’t (although if that’s in the game in the secret or its predecessor is unclear to me).
Either way, it’s making a ship canon and I can understand finding that OOC or unnecessary or canon/fandom killing.

[(Anonymous)]

Almost. It's an official infographic from the twitter but it's not (yet) mentioned in the game proper. But since the graphic is official, the ship is considered canon.

[(Anonymous)]

"Childhood sweetheart" doesn't necessarily mean it's a current ship, though? Like I can think of plenty of canons with characters who had childhood sweethearts but didn't end up with them in the end.

[(Anonymous)]

OP
Yeah that's kinda the way I interpret it so far (even though the ship still doesn't make sense). Like, childhood sweetheart can mean several things - either a one or both sided kiddie crush that fizzled out OR a relationship that dates back to a person's childhood and still exists... I personally go with "one sided kiddie crush" because nothing else makes sense in this case and I'll be glad if the game never actually mentions it (they actually also "sank" a different ship for some people because they construed a pseudo- family relationship that wasn't there in the original game.). It just bug me because, again, a reciprocated ship would be incredibly OOC.

I'm mainly happy that what little fandom there is for the game seems happy to ignore it as well, for the utmost part.

[(Anonymous)]

It's a character background infographic from the official twitter account of the game, so this ship would be considered canon in the game universe even though it wasn't mentioned in the actual game so far.
And the "so far" is kinda the issue because now, I can ignore the infographic throwaway but it could very well become a thing in-game then I couldn't ignore it as well anymore. The game only came out, what, two months ago so a lot could yet happen.

[(Anonymous)]

Sorry, gonna continue my policy of not caring about the lore of free-to-play mobile games. I refuse.

[(Anonymous)]

For the life of me I can't figure out the game name based on the logo. Afkii Journey? Afkai? Afk II?

[(Anonymous)]

The original game was AFK Arena and this is an RPG sequel spinoff (but not really because AU to the original game) so... I guess it's AFK 2 Journey (or just AFK Journey).

[(Anonymous)]

ayrt
Thanks!

[(Anonymous)]

the stylized "II" kinda looks like an N to me so I read it as "A FKN JOURNEY"

[(Anonymous)]

Hahaha, that's hilarious! I can't unsee it now.

[(Anonymous)]

OP
Ha! I love that.

[(Anonymous)]

Trying to figure out what an asspull means.

[(Anonymous)]

The same as pulling something out of thin air, something without any basis in canon/the characterisation, in this case.

[(Anonymous)]

Thank you!