A format will inherit rulesets and banlists from any rules specified in its ruleset which contain their own rulesets or banlists. For instance, UU can inherit OU's rules and bans, while adding its own tier bans and weather bans.
More specifically, if the rule under which something is banned has a name (e.g. "Evasion Clause"), inform the user that it's banned under that particular rule.
The Kyurem formes get Fusion Bolt/Flare and Freeze Shock/Ice Burn *in place of* Glaciate and Scary Face, so checkLearnset should not recurse down to the base Kyurem forme.
- the original names BattleItems etc have been deprecated; please use:
- Tools.getItem() accessor method if possible
- Tools.data.Items for lower-level access (e.g. iteration)
- app.js was also rearranged a bit
- replace Tools.foo with Tools.mod('gen4').foo for gen 4 tools
- mods are stored in mods/modname/ in the same directory structure as data/
- mods modify base data
- further documentation coming soon in mods/modding.md
When a Pokemon has been released but its prevos haven't (e.g. Mamoswine and Lucario), it can't learn any moves exclusive to its prevos. For instance, DW Mamoswine can't learn Ice Shard.
- DW-exclusive moves are now illegal on Pokemon without their DW ability.
- Released Pokemon with no DW ability (e.g. Gastly, Koffing, Chimecho) are checked as both DW and non-DW.
Gen 1-4 PKMN with mimic glitch used to be able to use their DW abilities
with mimic glitch moves due to an incorrect check in the mimic glitch
learnset checker
- Pokemon with a different DW ability from their prevo are now handled properly.
- The problem message now changes depending on whether an illegal move is incompatible with the Dream World.
- Problem messages now display the name of each Pokemon only if the Pokemon has been explicitly given a nickname. Otherwise, it just displays the species.
- Poison Heal Gliscor with Roost is now covered under standard DW legality.
- Ability legality checking is triggered by an 'Illegal' ban, instead of a 'Standard' rule
- So is moveset legality checking
- Banning 'Legal' is now meaningless, since it's redundant with 'Illegal'
All of the data received from the client is now validated, with the assumption that it only has JSON code (as far as I know; I may have forgotten something)
