29f778f233
- Legacy effect type ``Ruleset`` removed - New type ``RuleValueType`` for ``rule.hasValue`` - New interface ``RuleTableBuildContext`` for ``onValidateRule`` handlers - New interface: ``RuleEventMethods`` extending ``EventMethods`` - ``data/rulesets.ts``: Different tag-discriminated types for ``effectType='Rule'`` vs ``effectType='ValidatorRule'``: ``RuleData`` vs ``ValidatorRuleData``. - ``data/rulesets.ts``: Renamed ``FormatDataTable`` to ``RulesetTable`` - Distinguishes types for formats in ``config/formats.ts`` vs in ``Dex.data.Rulesets``: ``FormatData`` vs ``LoadedFormatData``. - Union type for formats OR rulesets in ``Dex.data.Rulesets``: ``RulesetData`` - Implements ``DexFormats#find|some``, for searches excluding rules. - Remove obsolete comment regarding former lack of support for format.onResidual |
||
|---|---|---|
| .. | ||
| examples | ||
| tools | ||
| battle-actions.ts | ||
| battle-queue.ts | ||
| battle-stream.ts | ||
| battle.ts | ||
| dex-abilities.ts | ||
| dex-conditions.ts | ||
| dex-data.ts | ||
| dex-formats.ts | ||
| dex-items.ts | ||
| dex-moves.ts | ||
| dex-species.ts | ||
| DEX.md | ||
| dex.ts | ||
| field.ts | ||
| global-types.ts | ||
| index.ts | ||
| NONSTANDARD.md | ||
| pokemon.ts | ||
| prng.ts | ||
| README.md | ||
| side.ts | ||
| SIM-PROTOCOL.md | ||
| SIMULATOR.md | ||
| state.ts | ||
| team-validator.ts | ||
| TEAMS.md | ||
| teams.ts | ||
| tsconfig.json | ||
Node.js package
Pokémon Showdown has a Node.js API. It currently only works in Node, not browsers, although we're working on unifying it to work in browsers.
You can install it with the usual:
npm install pokemon-showdown
And you can use it to do the following things:
Simulating battles
See: sim/SIMULATOR.md
Also available as a command-line API!
Validating, generating, and converting teams
See: sim/TEAMS.md
Also available as a command-line API!
Getting Pokédex information
See: sim/DEX.md
Undocumented APIs
Pokémon Showdown's Node.js package has TypeScript definitions for everything it exports, including a lot of undocumented APIs.
Please be aware that any undocumented API is unstable and should not be relied upon not to change. We do not follow semver for undocumented APIs. If you really want to use an undocumented API, remember to pin the exact PS version in your dependencies. You probably also want to follow the API update channel in the Discord server: https://psim.us/devdiscord