b27ddb4ae2
* Allow BDSP moves to be learned via HOME relearner * Update team-validator.ts Commented out my changes to see if this was causing a test to fail; turns out my code isn't at fault. * Update team-validator.ts * Don't get learnset for Pokemon that don't exist in BDSP Without the isNonstandard check, the learnset will be taken from the base learnsets.ts file, which could result in detecting moves that are actually not from BDSP. * Fix BDSP legality * Update team-validator.ts * Fix test and learnsets * Update data.js * Prevent illegal transfers to/from BDSP Nincada from outside BDSP cannot be sent to BDSP, Nincada from BDSP cannot be sent to other Switch games, and Spinda cannot be sent from or to BDSP. Currently this has no effect in regular Gen 9, but it technically does in Gen 9 Natdex (I have no idea if anything changes), and it may affect future generations. |
||
|---|---|---|
| .. | ||
| 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