Talk:Move variations: Difference between revisions

m
Line 180: Line 180:
:::::Minor problem with that though. Ember, Flamethrower and Fire Blast (and probably others but those are the big ones) all have a 10% chance of causing burn. Moreover, they're all Fire attacks. If we go solely by effect, then that makes them variations of each other. So then we have moves that are multiple variations in one. Is that really ok? I mean, I can see it going either way...
:::::Minor problem with that though. Ember, Flamethrower and Fire Blast (and probably others but those are the big ones) all have a 10% chance of causing burn. Moreover, they're all Fire attacks. If we go solely by effect, then that makes them variations of each other. So then we have moves that are multiple variations in one. Is that really ok? I mean, I can see it going either way...


One possibility is to split it into two things, where there are moves that are strictly exact copies of each other minus type and specific effect (not % chance of effect though, that has to say the same), and then other moves that just do the same thing but are not exact copies. Like, if I want to look for moves that cause Burn, there could be a category that I could go to and look there, and likewise for moves that cause trapping, or moves that hit everyone on the field. Does that sound reasonable? [[User:Dragoness|Dragoness]] 01:14, 15 January 2009 (UTC)
:::::One possibility is to split it into two things, where there are moves that are strictly exact copies of each other minus type and specific effect (not % chance of effect though, that has to say the same), and then other moves that just do the same thing but are not exact copies. Like, if I want to look for moves that cause Burn, there could be a category that I could go to and look there, and likewise for moves that cause trapping, or moves that hit everyone on the field. Does that sound reasonable? [[User:Dragoness|Dragoness]] 01:14, 15 January 2009 (UTC)


== Protect? Detect? ==
== Protect? Detect? ==
445

edits