Dragon WriterWhen I look at this page anymore, I think it's safe and useful to keep a list describing what actual gameplay effects are commonly associated with the effect names. E.g., Everybody knows what to expect when they see a status label like "poison" or "sleep". (Yes, the exact details vary per system, but...) IMHO what needs to be done to the page as-is is get rid of the per-effect example sorting and convert it to one master examples list (alphabetically or per-genre) at the end, like we typically have with most tropes anyway.
edited 24th Nov '12 4:02:33 PM by Stratadrake
Don't let it dieWho are the ones that have called making those YKTTWs? I haven't seen any of them on YKTTW at all. Also, do we also need a Non Standard Status Effects so we can cover some of the shoehorned examples?
Yes, please. Or at least remove the word "Standard" from the index name. This trope gets used for all Status Effects, regardless of whether they are common or unique to a game. Splitting off a "miscellaneous" standard effects trope would be an improvement, but I think leaving room for people to link to the main trope without calling weird, game-specific effects "standard" would be better, because currently the trope name is meaningless cruft.
edited 12th Dec '12 9:36:35 AM by Kurtulmak
Dragon WriterMaybe we can just call it Status Ailment? This is supposed to be only about the negative ones; positive ones go under Status Buff.
edited 12th Dec '12 10:21:20 AM by Stratadrake
Don't let it dieI second that proposal.
Dragon WriterWell, whatever happens IMO we need to at least eliminate the per-effect example sorting. (Since simple renaming wasn't included on the old crowner, if we want to do a PA crowner all over again here it is.)
edited 13th Dec '12 12:45:30 AM by Stratadrake
Don't let it dieWell, I think I'll be the one to do the YKTTWs for the individual Standard Status Effects or Status Ailments whatever we'll call it. I'm planning to set it up somewhat similarly to my improvement YKTTW for Stock RPG Spells in that the individual examples are better suited to the subtropes, and the main page is just about the patterns themselves. I'll make a list of the subtropes for the various status ailments we already have here:
edited 13th Dec '12 8:21:44 PM by WaxingName
Dragon WriterIt's probably better to list those by common spell names ("Petrify", "Death", etc.) instead of the trope names.
Don't let it dieWell, we have to mention the trope names somehow, since they already exist.
Dragon WriterI've got a reworked description and effect list under Sandbox.Standard Status Effects. How does it look? Examples need sorting though.
Rule of Perception. Also, folders?
edited 15th Dec '12 1:58:14 PM by troacctid
Rhymes with "Protracted."
Dragon WriterFolders are part of the original problem - the page's current layout goes roughly like this:
edited 16th Dec '12 7:01:11 AM by Stratadrake
Io vs JupiterI would just call it Status Ailment to make it easier to use in a sentence, and to cover things like MS Saga or EarthBound that have the same effects but give them different names. I also think we should cover things from the effect side, rather than what they're called, for the same reason. Here's what I think we should cover:
No, the other one.Something very close to that, yes. However, that's not Interface Screw. That trope is when your controls are messed with, not your control of the character. It's like calling a Cut Scene an Interface Screw, because you don't have control over your character then.
I also think we should cover things from the effect side, rather than what they're called, for the same reason.But the labelling of status effects is a trope, too. I would like to give a bit of both, really, including effects and common names.
No, the other one.Overall, I think the effects are used more than their names, though. I don't see a game designer thinking about adding an effect called "poison", and then deciding what it does. It happens, sure, but not as standard. However, I think it does vary with which effect. To take one example, I think "berserk" is more often thought up as a named concept, and then fleshed out to a mechanic. The main thing is that effects can be grouped by how similar the mechanics are, while names are discrete entities, and can't be grouped as such.
Io vs JupiterI meant Interface Screw or you lose control of the character. I was thinking about "confusion" effects that randomize the directional pad input (so pressing up makes your character go left, for example) and the like. Sure, we'd still include common labels, but it would be along the lines of "HP Drain: commonly called 'poison', you lose a small amount of HP per turn or period of time" rather than "Poison: drains small amounts of HP per turn, sometimes called other things".
Don't let it dieThat's an even better idea. We already have Damage Over Time, though, so we have one of those covered. Is that what we'll do then?
No, the other one.Fair enough. I'm not sure I see it as the same thing, though. Related, but not the same. It probably depends on how fine grains we use in the list.
Dragon WriterI gave the sandbox another polish. Hmm ... should I try using a table format instead of a list?
Io vs JupiterI think having two lists, one for effect descriptions and one for common effect names, makes the page way too long. I could see a table working, though.
Rhymes with "Protracted."
Perhaps you should switch zombie to a more general 'creature type change.' I know the zombie thing from...FF whatever? is the example most people think of but I'm pretty sure I've seen that sort of thing elsewhere. For example, I think Disgaea 2 had maps with special status effects that would do weird things like turn your character into a dragon. Other games might have things that change your creature type/element and make your vulnerabilities and whatnot change.
edited 18th Dec '12 10:25:14 PM by Arha
TV Tropes by TV Tropes Foundation, LLC is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.
Permissions beyond the scope of this license may be available from firstname.lastname@example.org.