Misused: The Dev Team Thinks Of Everything

Right. Anything else?

Without the "everything" part, if any one instance of an unlikely action leading to bonus content qualifies, I don't see much of a difference between this and Easter Egg.

Kinda wanna call it The Dev Team Anticipated That, but that sounds like a phrase.

Easter Egg does overlap heavily, and I don't see why it shouldn't be able to. Not all Easter Eggs are this trope since some of them aren't responses to actions, just little bonuses (i.e. the hidden Luigis in the one recent Mario game I can't remember the name of).

I disagree. An Easter Egg is a response to the actions required to find/unlock/activate it. Whether the response is important or "just a little bonus" is a rather ambiguous distinction.

I'm clearly doing a bad job at explaining this, so I'll just say I know these tropes are distinct from each other and hope someone else can do a better job at saying why.

Yeah, I know I'm lazy. Sue me.

Is there anyone who isn't lazy who wants to take a stab at improving Sandbox.The Dev Team Thinks Of Everything?

Part of the misuse involves people just gushing about attention to detail, so there should be a line saying that it has to be in response to a player's actions.

Problem is, just about every action in a game is the result of player actions...

Besides, it's on the current description as well.

Stuff like having characters take off their shoes inside buildings in a game taking place in a Japan analog has nothing to do with player actions bar walking into the right room (and there are a lot of right rooms). Besides, there is nothing obscure, counterproductive, or out-of-the-way about examples like that.

I'm blind.

Maybe add a line in the second paragraph about counterproductive or counterintuitive actions getting this result.

I dont see the fact that Inside Shoes or taking them off to enter a house in a game is really this. All that is is Shown Their Work and only if the game itself was not made in Japan.

That is like saying ooh the car drives on the left hand side of the road! Or that school girl has a book bag going to school! Well duh. It is just an element of every day life that is supposed to be there.

edited 18th Jan '15 11:15:30 AM by Memers

I think the only reason why that was added in the first place is because that "detail" wasn't depicted within the main games before (since the animations of the overworld sprites were severely limited before gen 6 {which took advantage of the fact that the "sprites" were simply 3D models and not only made the animations smoother, but also added in some more}).

@111: It's actually me who's blind - I was referring to the first sentence of the last paragraph (which I mistook as saying it's this trope).

edited 19th Jan '15 6:35:26 AM by KarjamP

It seems as though the "Rework the trope to be about the game being programmed to cover each and every possible response the programmer could think of." option is quite popular, to the point where it has the ratio of 2:1 as of this post (compared to its competitor "Rewrite the definition to be more clear (and cleanup all misuse)." Which is 1.75:1).

Well then since both ideas have support then what about a transplant and make both tropes?

• Detail In Video Games which IMO should not apply to modern games, and far too far into the gushing department.
• Dev Teams Prepared For That probably with the name The Dev Team Thinks of Everything

I personally think that the first one is just Shown Their Work World building edition but meh.

edited 20th Jan '15 6:50:23 AM by Memers

Like I said, it's far too restrictive because the developers missing anything, no matter how small or irrelevant, would disqualify examples on the basis that it doesn't fit the Exactly What It Says on the Tin definition people are trying to make for it. It is physically impossible to have programmed answers for every possible scenario.

EDIT: On second thought it can work, but only In-Universe and if the audience can't test the authenticity of the statement.

edited 20th Jan '15 10:08:32 AM by Karxrida

Then what will we do with the current trope name?

According to site policy, the sheer amount of wicks to The Dev Team Thinks of Everything means we can't just get rid of the name.

This is why, I presume, that "trope transplant" is in the red.

You me when I posted this post.

edited 20th Jan '15 10:06:26 AM by KarjamP

Keep it and put in the description that it's not meant to be taken literally if the misuse is that much of an issue. Preferably in large, bold letters.

Darn straight I did.

edited 20th Jan '15 10:09:05 AM by Karxrida

One trope could get the name, prefer the latter, but it can just be a redirect if people really want.

Nothing's bad with making the old trope name a redirect and change this thing's name.

Again, maybe Trivial Programmed Scenarios?

What's trivial about this trope?

Guys? "Trope transplant" is in the red at -5.

In other words, several people think that's a bad idea.

The only things we should consider is either "Rewrite the definition to be more clear (and cleanup all misuse)" or "Rework the trope to be about the game being programmed to cover each and every possible response the programmer could think of" since they have the highest number and second highest number, respectively and, in fact, are both nearly at the minimum ratio of 2:1 in order for a consensus to be reach.

edited 21st Jan '15 5:42:28 AM by KarjamP

Second one is actually at 1.25 as of this writing.

Now it's 1.40:1.

Let's not be nitpicky about the fact that the ratios are volatile.

Anyway, "Rewrite the definition to be more clear (and cleanup all misuse).", as of this post, is at 2.13:1.

Another Duck's proposed rewritten description at @97 is looking more and more viable at the moment, at least to me. I propose we wrap this up, finish up the draft of the rewritten description, replace the current description with this one and start a cleaning up project.

I am not going to call the crowner for that option, folks. It's unacceptably open-ended on its own.