@pkmn/engine 0.1.0-dev.4eeb346e → 0.1.0-dev.526bb2e1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +28 -25
- package/build/pkg/addon.d.ts +1 -1
- package/build/pkg/addon.js +7 -6
- package/build/pkg/addon.js.map +1 -1
- package/build/pkg/data/layout.json +25 -3
- package/build/pkg/gen1.d.ts +5 -4
- package/build/pkg/gen1.js +46 -30
- package/build/pkg/gen1.js.map +1 -1
- package/build/pkg/index.d.ts +15 -12
- package/build/pkg/index.js.map +1 -1
- package/build/pkg/protocol.d.ts +4 -2
- package/build/pkg/protocol.js +4 -2
- package/build/pkg/protocol.js.map +1 -1
- package/build/test/display.js +29 -12
- package/build/test/display.js.map +1 -1
- package/build.zig +39 -24
- package/package.json +22 -14
- package/src/bin/install-pkmn-engine +11 -6
- package/src/lib/binding/node.zig +45 -140
- package/src/lib/binding/wasm.zig +5 -3
- package/src/lib/common/battle.zig +17 -0
- package/src/lib/common/data.zig +11 -11
- package/src/lib/common/debug.zig +21 -11
- package/src/lib/common/js.zig +118 -0
- package/src/lib/common/optional.zig +60 -0
- package/src/lib/common/options.zig +12 -3
- package/src/lib/common/protocol.zig +239 -178
- package/src/lib/common/rational.zig +353 -0
- package/src/lib/common/rng.zig +10 -10
- package/src/lib/common/util.zig +12 -0
- package/src/lib/gen1/README.md +102 -79
- package/src/lib/gen1/calc.zig +427 -0
- package/src/lib/gen1/chance.zig +1044 -0
- package/src/lib/gen1/data/moves.zig +10 -10
- package/src/lib/gen1/data/species.zig +2 -2
- package/src/lib/gen1/data/types.zig +3 -3
- package/src/lib/gen1/data.zig +59 -38
- package/src/lib/gen1/helpers.zig +439 -32
- package/src/lib/gen1/mechanics.zig +896 -516
- package/src/lib/gen2/data/items.zig +3 -3
- package/src/lib/gen2/data/moves.zig +1 -1
- package/src/lib/gen2/data/species.zig +1 -1
- package/src/lib/gen2/data/types.zig +3 -3
- package/src/lib/gen2/data.zig +33 -22
- package/src/lib/gen2/helpers.zig +9 -11
- package/src/lib/gen2/mechanics.zig +5 -4
- package/src/lib/pkmn.zig +65 -6
package/src/lib/gen1/README.md
CHANGED
|
@@ -28,35 +28,36 @@ list of additional reference [**resources**](#resources).
|
|
|
28
28
|
|
|
29
29
|
The following information is required to simulate a Generation I Pokémon battle:
|
|
30
30
|
|
|
31
|
-
| pkmn
|
|
32
|
-
|
|
|
33
|
-
| `battle.seed`
|
|
34
|
-
| `battle.turn`
|
|
35
|
-
| `battle.last_damage`
|
|
36
|
-
| `side.{active,pokemon}`
|
|
37
|
-
| `side.team`
|
|
38
|
-
| `side.last_used_move`
|
|
39
|
-
| `side.last_selected_move`
|
|
40
|
-
| `battle.
|
|
41
|
-
| `
|
|
42
|
-
| `
|
|
43
|
-
| `pokemon.
|
|
44
|
-
| `
|
|
45
|
-
| `{pokemon,active}.
|
|
46
|
-
| `pokemon.
|
|
47
|
-
| `pokemon.
|
|
48
|
-
| `
|
|
49
|
-
| `
|
|
50
|
-
| `
|
|
51
|
-
| `
|
|
52
|
-
| `active.
|
|
53
|
-
| `active.
|
|
54
|
-
| `volatiles
|
|
55
|
-
| `volatiles.
|
|
56
|
-
| `volatiles.
|
|
57
|
-
| `volatiles.
|
|
58
|
-
| `volatiles.
|
|
59
|
-
| `volatiles.
|
|
31
|
+
| pkmn | Pokémon Red (pret) | Pokémon Showdown |
|
|
32
|
+
| --------------------------------------- | ---------------------------------- | -------------------------------------- |
|
|
33
|
+
| `battle.seed` | `Random{Add,Sub}` | `battle.seed` |
|
|
34
|
+
| `battle.turn` | - | `battle.turn` |
|
|
35
|
+
| `battle.last_damage` | `Damage` | `battle.lastDamage` |
|
|
36
|
+
| `side.{active,pokemon}` | `PlayerMonNumber`/`BattleMon` | `side.active` |
|
|
37
|
+
| `side.team` | `PartyMons` | `side.pokemon` |
|
|
38
|
+
| `side.last_used_move` | `PlayerUsedMove` | `pokemon.lastMove` |
|
|
39
|
+
| `side.last_selected_move` | `PlayerSelectedMove` | `side.lastSelectedMove` |
|
|
40
|
+
| `battle.last_moves.{p1,p2}_index` | `PlayerMoveListIndex` | - |
|
|
41
|
+
| `battle.last_moves.{p1,p2}_counterable` | - | `side.lastMove` |
|
|
42
|
+
| `side.order` | - | `pokemon.position` |
|
|
43
|
+
| `{pokemon,active}.moves` | `{party,battle}_struct.{Moves,PP}` | `pokemon.{baseMoveSlots,moveSlots}` |
|
|
44
|
+
| `pokemon.hp` | `{party,battle}_struct.HP` | `pokemon.hp` |
|
|
45
|
+
| `{pokemon,active}.status` | `{party,battle}_struct.Status` | `pokemon.status` |
|
|
46
|
+
| `{pokemon,active}.level` | `PlayerMonUnmodifiedLevel` | `pokemon.level` |
|
|
47
|
+
| `pokemon.species` | `party_struct.Species` | `pokemon.baseSpecies` |
|
|
48
|
+
| `pokemon.stats` | `box_struct.Stats` | `pokemon.baseStoredStats` |
|
|
49
|
+
| `active.stats` | `battle_struct.Stats` | `pokemon.modifiedStats` |
|
|
50
|
+
| `volatiles.transform` | `PlayerMonUnmodified*` | `pokemon.storedStats` |
|
|
51
|
+
| `active.species` | `battle_struct.Species` | `pokemon.species` |
|
|
52
|
+
| `{pokemon,active}.types` | `{party,battle}_struct.Type` | `pokemon.types` |
|
|
53
|
+
| `active.boosts` | `PlayerMon*Mod` | `pokemon.boosts` |
|
|
54
|
+
| `active.volatiles` | `PlayerBattleStatus{1,2,3}` | `pokemon.volatiles` |
|
|
55
|
+
| `volatiles.state` | `PlayerBideAccumulatedDamage` | `volatiles.bide.totalDamage` |
|
|
56
|
+
| `volatiles.attacks` | `PlayerNumAttacksLeft` | `volatiles.{bide,lockedmove}.duration` |
|
|
57
|
+
| `volatiles.confusion` | `PlayerConfusedCounter` | `volatiles.confusion.duration` |
|
|
58
|
+
| `volatiles.toxic` | `PlayerToxicCounter` | `volatiles.residualdmg.counter` |
|
|
59
|
+
| `volatiles.substitute` | `PlayerSubstituteHP` | `volatiles.substitute.hp` |
|
|
60
|
+
| `volatiles.disabled_{move,duration}` | `PlayerDisabledMove{,Number}` | `volatiles.disable.{move,time}` |
|
|
60
61
|
|
|
61
62
|
- Pokémon Showdown [does not implement the correct Generation I RNG](#rng) and as such its `seed` is
|
|
62
63
|
different
|
|
@@ -68,6 +69,9 @@ The following information is required to simulate a Generation I Pokémon battle
|
|
|
68
69
|
Counter and is not set and cleared in the correct locations. `Pokemon.lastMove` matches
|
|
69
70
|
`PlayerUsedMove` more often so is what the engine attempts to model, despite the implications for
|
|
70
71
|
Counter)
|
|
72
|
+
- `battle.last_moves` doesn't map precisely to cartridge concepts because it is used to track desyncs
|
|
73
|
+
which instead are represented on the cartridge as discrepancies between the two separate battle states
|
|
74
|
+
that exist in the link battle.
|
|
71
75
|
- Pokémon Showdown does not implement the [partial-trapping move Mirror Move
|
|
72
76
|
glitch](https://glitchcity.wiki/Partial_trapping_move_Mirror_Move_link_battle_glitch) and as such
|
|
73
77
|
does not need to keep track of a player's last selected move index (`PlayerMoveListIndex`)
|
|
@@ -98,8 +102,8 @@ The following information is required to simulate a Generation I Pokémon battle
|
|
|
98
102
|
store general information about the battle. Unlike in Pokémon Showdown there is a distinction
|
|
99
103
|
between the data structure for the "active" Pokémon and its party members (see below).
|
|
100
104
|
|
|
101
|
-
Due to layout constraints,
|
|
102
|
-
otherwise be the padding bytes of`Battle` (the `
|
|
105
|
+
Due to layout constraints, details about the last moves for a side are stored in what would
|
|
106
|
+
otherwise be the padding bytes of`Battle` (the `last_moves` field) instead of in `Side`.
|
|
103
107
|
|
|
104
108
|
### `Pokemon` / `ActivePokemon`
|
|
105
109
|
|
|
@@ -198,7 +202,7 @@ above, PP information isn't strictly necessary in Generation I so is dropped. `M
|
|
|
198
202
|
a special sentinel value to indicate `null`. Move PP data is only included for testing and is not
|
|
199
203
|
necessary for the actual engine implementation.
|
|
200
204
|
|
|
201
|
-
In order to workaround various [Pokémon Showdown bugs](#bugs) and to support its protocol in
|
|
205
|
+
In order to workaround various [Pokémon Showdown bugs](#bugs) and to support its protocol in logs,
|
|
202
206
|
additional information is stored in `Move.Data` (`targets`) about what Pokémon Showdown believes the
|
|
203
207
|
`Move.Target` to be (despite the concept of targeting not existing until Generation III when Double
|
|
204
208
|
battles were introduced). More specifically, a move's "targeting" status is required in various
|
|
@@ -282,9 +286,9 @@ padding](https://en.wikipedia.org/wiki/Data_structure_alignment) and
|
|
|
282
286
|
- the active Pokémon's level and current and max HP can always be referred to the `Pokemon`
|
|
283
287
|
struct
|
|
284
288
|
- **`Side`**: `ActivePokemon` + 6× `Pokemon` + active (`3`) + last used (`8`) + last selected
|
|
285
|
-
(`8`)
|
|
289
|
+
(`8`) + counterable (`1`) + last move index (`3`)
|
|
286
290
|
- `order` does not need to be stored as the party can always be rearranged as switches occur
|
|
287
|
-
- **`Battle`**: 6× `Side` + seed (
|
|
291
|
+
- **`Battle`**: 6× `Side` + seed (9× `8` + `4`) + turn (`10`) + last damage (`10`)
|
|
288
292
|
- **`Type.CHART`**: attacking types (`15`) × defending types (`15`) × effectiveness (`2`)[^2]
|
|
289
293
|
- **`Type.PRECEDENCE`**: 29× attacking type (`4`) + defending type (`4`) pairs
|
|
290
294
|
- **`Moves.DATA`**: 165× base power (`6`) + effect (`7`) + accuracy (`4`) + type (`4`) + target
|
|
@@ -295,8 +299,8 @@ padding](https://en.wikipedia.org/wiki/Data_structure_alignment) and
|
|
|
295
299
|
| ----------------- | ----------- | ------------ | -------- |
|
|
296
300
|
| `Pokemon` | 192 | 147 | 30.6% |
|
|
297
301
|
| `ActivePokemon` | 256 | 202 | 26.7% |
|
|
298
|
-
| `Side` | 1472 |
|
|
299
|
-
| `Battle` | 3088 |
|
|
302
|
+
| `Side` | 1472 | 1107 | 33.0% |
|
|
303
|
+
| `Battle` | 3088 | 2310 | 33.7% |
|
|
300
304
|
| `Type.CHART` | 1800 | 450 | 300.0% |
|
|
301
305
|
| `Type.PRECEDENCE` | 232 | 232 | 0.0% |
|
|
302
306
|
| `Moves.DATA` | 5280 | 3960 | 33.3% |
|
|
@@ -331,34 +335,37 @@ does not produce an equivalent to Pokémon Showdown's `|request|` protocol messa
|
|
|
331
335
|
must be gleaned through the `Battle` state). Useful size and offset information can be found in
|
|
332
336
|
the [`layout.json`](../../data/layout.json) which exists to simplify writing driver code.
|
|
333
337
|
|
|
334
|
-
Documentation of the wire protocol used for logging
|
|
335
|
-
[PROTOCOL.md](../../../docs/PROTOCOL.md). Note that the
|
|
338
|
+
Documentation of the wire protocol used for protocol message logging when `-Dlog` is enabled can be
|
|
339
|
+
found in [PROTOCOL.md](../../../docs/PROTOCOL.md). Note that the
|
|
336
340
|
[`pkmn-debug`](../../../README.md#pkmn-debug) tool exists to display the binary protocol and battle
|
|
337
341
|
data in the browser for ease of debugging.
|
|
338
342
|
|
|
339
343
|
### `Battle`
|
|
340
344
|
|
|
341
|
-
| Start | End | Data
|
|
342
|
-
| ------- | ------- |
|
|
343
|
-
| 0 | 184 | [`sides[0]`](#side)
|
|
344
|
-
| 184 | 368 | [`sides[1]`](#side)
|
|
345
|
-
| 368 | 370 | `turn`
|
|
346
|
-
| 370 | 372 | `last_damage`
|
|
347
|
-
| 372 |
|
|
348
|
-
|
|
|
345
|
+
| Start | End | Data | Description |
|
|
346
|
+
| ------- | ------- | ------------------- | ------------------------------------------------------- |
|
|
347
|
+
| 0 | 184 | [`sides[0]`](#side) | Player 1's side |
|
|
348
|
+
| 184 | 368 | [`sides[1]`](#side) | Player 2's side |
|
|
349
|
+
| 368 | 370 | `turn` | The current turn number |
|
|
350
|
+
| 370 | 372 | `last_damage` | The last damage dealt by either side |
|
|
351
|
+
| 372 | 374-376 | `last_moves` | The slot index of the last selected moves for each side |
|
|
352
|
+
| 374-376 | 384 | `rng` | The RNG state |
|
|
349
353
|
|
|
350
354
|
- the current `turn` is 2 bytes, written in native-endianness
|
|
351
|
-
- `
|
|
352
|
-
|
|
353
|
-
|
|
354
|
-
|
|
355
|
-
|
|
356
|
-
|
|
357
|
-
`side[1]`
|
|
355
|
+
- `last_moves` layout depends on whether or not Pokémon Showdown compatibility mode is enabled
|
|
356
|
+
(`-Dshowdown`). In either case it stores the last selected move index and last executed move for
|
|
357
|
+
each player (required to detect desyncs). In the case of the move index, 0 is used as an empty
|
|
358
|
+
value and 1-4 represent actual moves:
|
|
359
|
+
- if `showdown` is enabled byte 372 is used to store the last selected move index of `side[0]` and
|
|
360
|
+
byte 373 is used to store whether or not the side's last executed move would have been considered
|
|
361
|
+
"counterable"; and bytes 374 and 375 store the same information for `side[1]`
|
|
362
|
+
- otherwise the first 4 bits of byte 372 stores the last selected move index of `side[0]` and the
|
|
363
|
+
next 4 bits store whether that side's last executed move would have been considered
|
|
364
|
+
"counterable", with the same information for `side[1]`'s being stored in the second byte
|
|
358
365
|
- the `rng` depends on whether or not Pokémon Showdown compatibility mode is enabled (`-Dshowdown`):
|
|
359
366
|
- if `showdown` is enabled, the RNG state begins on byte 376 and consists of a 64-bit seed,
|
|
360
367
|
written in native-endianness
|
|
361
|
-
- otherwise the RNG state begins on byte
|
|
368
|
+
- otherwise the RNG state begins on byte 374 and consists of the 9 bytes of the seed followed by
|
|
362
369
|
the index pointing to which byte of the seed is currently being used
|
|
363
370
|
|
|
364
371
|
### `Side`
|
|
@@ -485,12 +492,16 @@ Beyond the general bugs listed above, several move effects are implemented incor
|
|
|
485
492
|
Showdown. Some of these moves are [too fundamentally broken to be implemented](#unimplementable) by
|
|
486
493
|
the pkmn engine, but the following moves have their broken behavior preserved in `-Dshowdown` mode:
|
|
487
494
|
|
|
488
|
-
- **Bide**:
|
|
489
|
-
|
|
495
|
+
- **Bide**: Bide's damage can overflow if OHKO moves are involved because OHKO moves work by setting
|
|
496
|
+
the damage to 65535 - Pokémon Showdown doesn't implement this overflow and instead lets Bide's
|
|
497
|
+
damage grow unbounded. Additionally, if the opponent faints after Bide inflicts damage on Pokémon
|
|
498
|
+
Showdown residual damage incorrectly still gets applied to Bide's user.
|
|
499
|
+
- **Counter**: On Pokémon Showdown choices made while sleeping (which should not have been
|
|
500
|
+
registered) can erroneously cause Counter to trigger Desync Clause Mod behavior. Additionally,
|
|
501
|
+
because Pokémon Showdown neglects to zero the last battle damage if a move misses due to immunity
|
|
502
|
+
or invulnerability Counter will occasionally work on Pokémon Showdown when it should fail.
|
|
490
503
|
- **Leech Seed**: Leech Seed fails to heal its source side if a seeded target faints due to
|
|
491
|
-
recoil/crash damage on Pokémon Showdown.
|
|
492
|
-
field with the uncapped Leech Seed damage if the residual damage is applied which has consequences
|
|
493
|
-
for Bide and Counter.
|
|
504
|
+
recoil/crash damage on Pokémon Showdown.
|
|
494
505
|
- **Pay Day**: Pay Day should still scatter coins if it hits (but doesn't break) and opponent's
|
|
495
506
|
Substitute but doesn't on Pokémon Showdown.
|
|
496
507
|
- **Flinch**: Flinching does not get cleared during move selection on Pokémon Showdown and is
|
|
@@ -531,9 +542,13 @@ the pkmn engine, but the following moves have their broken behavior preserved in
|
|
|
531
542
|
glitch](https://glitchcity.wiki/Substitute_%C2%BC_HP_glitch) also fails in many cases due to
|
|
532
543
|
Pokémon Showdown implementing the health check based on floating point division instead of integer
|
|
533
544
|
divison like on the cartridge (meaning the Substitute 1/4 glitch will only occur if the Pokémon's
|
|
534
|
-
maximum HP is evenly divisible by 4).
|
|
545
|
+
maximum HP is evenly divisible by 4). Substitute also incorrectly blocks Dream Eater on
|
|
535
546
|
Pokémon Showdown and will incorrectly still heal 1 HP for any draining moves if the attack does 0
|
|
536
|
-
damage.
|
|
547
|
+
damage. Finally, Pokémon Showdown uses a `subFainted` field to track whether a Substitute was
|
|
548
|
+
broken in order to know when to nullify a move's effect, only it doesn't get cleared at the end of
|
|
549
|
+
the turn and can result in incorrect behavior on subsequent turns with the moves Mirror Move and
|
|
550
|
+
Metronome that invoke `runMove` (which is where `subFainted` gets cleared) on the user but skips
|
|
551
|
+
calling it for the eventual true target.
|
|
537
552
|
|
|
538
553
|
In addition to numerous cases where Pokémon Showdown uses the wrong type of message (e.g. `|-fail`
|
|
539
554
|
vs. `|-miss|` vs. `|-immune|`, e.g. in the case of Leech Seed) which are not documented here, Pokémon
|
|
@@ -603,9 +618,9 @@ the correct control flow):
|
|
|
603
618
|
still gets a turn under the [trapping sleep
|
|
604
619
|
glitch](https://glitchcity.wiki/Trapping_move_and_sleep_glitch), Wrap does 0 damage against
|
|
605
620
|
Ghost-type Pokémon instead of properly respecting immunity, and binding effects are handled in the
|
|
606
|
-
wrong order in the code
|
|
607
|
-
|
|
608
|
-
|
|
621
|
+
wrong order in the code which results in either out of order messaging or, more consequentially,
|
|
622
|
+
Pokémon using Rage/Bide or Thrashing/Charging moves being incorrectly forced to skip a turn when
|
|
623
|
+
the Pokémon using the Binding move switches.
|
|
609
624
|
- **Mimic**: Pokémon Showdown checks that the user of Mimic has Mimic in one of their move slots,
|
|
610
625
|
which means Mimic legally called via Metronome or Mirror Move will only work if the user also has
|
|
611
626
|
Mimic (and the moved mimicked by Mimic called via Metronome / Mirror Move will erroneously
|
|
@@ -613,19 +628,27 @@ the correct control flow):
|
|
|
613
628
|
because Pokémon Showdown deducts PP based on a move's name instead of slot, if Mimic copies a move
|
|
614
629
|
the Pokémon already knows, PP deduction for using either the original move of the mimicked move
|
|
615
630
|
will instead deduct PP for whichever appears at the lower move slot index and the PP will be
|
|
616
|
-
allowed to go negative (effectively allowing for infinite PP use).
|
|
617
|
-
|
|
618
|
-
|
|
631
|
+
allowed to go negative (effectively allowing for infinite PP use). Pokémon Showdown also doesn't
|
|
632
|
+
deduct PP from using Transform if it was copied by Mimic.
|
|
633
|
+
- **Mirror Move**: As covered above, both Substitute and Binding moves misbehave when used via
|
|
634
|
+
Mirror Move (though Pokémon Showdown has its own weird behavior and does not implement the
|
|
635
|
+
[partial trapping move Mirror Move
|
|
619
636
|
glitch](https://glitchcity.wiki/Partial_trapping_move_Mirror_Move_link_battle_glitch) that exists
|
|
620
|
-
on the cartridge).
|
|
621
|
-
|
|
622
|
-
|
|
623
|
-
|
|
624
|
-
- **
|
|
637
|
+
on the cartridge). Additionally, Pokémon Showdown sets the last used move every turn a Pokémon is
|
|
638
|
+
Thrashing instead of just on the turn it is actually selected meaning Mirror Move will sometimes
|
|
639
|
+
successfully mirror a Thrashing move when it should fail. Finally, if Mirror Move copies
|
|
640
|
+
Struggle it should not deduct PP but on Pokémon Showdown it does.
|
|
641
|
+
- **Metronome**: In addition to the issues with binding moves and Substitute, Metronome and Mirror
|
|
642
|
+
Move cannot mutually call each other more than 3 times in a row without causing the Pokémon
|
|
643
|
+
Showdown simulator to crash due to defensive safety checks that do not exist on the cartridge.
|
|
644
|
+
- **Transform**: Transform screws up the effect of Disable, because on Pokémon Showdown, Disable
|
|
625
645
|
prevents moves of a given *name* from being used (e.g. "Water Gun") as opposed to moves in a
|
|
626
646
|
specific *slot* (e.g. the 2nd move slot), and a Pokémon's moves can change after Transform (this
|
|
627
|
-
is not an issue with Disable + Mimic because Mimic happens to replace the same slot).
|
|
628
|
-
|
|
647
|
+
is not an issue with Disable + Mimic because Mimic happens to replace the same slot). Transform
|
|
648
|
+
also has a bad interaction with Pokémon Showdown's buggy Haze implementation, as Haze on Pokémon
|
|
649
|
+
Showdown does not copy unmodified stats, leaving the Transformed Pokémon with incorrect stats.
|
|
650
|
+
Furthermore, transforming and then using Mirror Move / Metronome can result in [glitchy behavior
|
|
651
|
+
and
|
|
629
652
|
softlocks](https://pkmn.cc/bulba/Transform_glitches#Transform_.2B_Mirror_Move.2FMetronome_PP_error)
|
|
630
653
|
which Pokémon Showdown does not implement.
|
|
631
654
|
|
|
@@ -644,7 +667,7 @@ the pkmn engine aims to be as compatible with Pokémon Showdown as possible when
|
|
|
644
667
|
compatibility mode, the implications of these differences are outlined below:
|
|
645
668
|
|
|
646
669
|
- **RNG**: Pokémon Showdown uses the RNG from Generation V & VI in every generation, despite
|
|
647
|
-
the seeds and algorithm being different. Pokémon Red uses a simple 8-bit RNG with
|
|
670
|
+
the seeds and algorithm being different. Pokémon Red uses a simple 8-bit RNG with 9 distinct
|
|
648
671
|
seeds generated when the link connection is established, whereas Pokémon Showdown uses a 64-bit
|
|
649
672
|
RNG with a 32-bit output.
|
|
650
673
|
- **Algorithm**: As detailed in the table below, the algorithm used by Pokémon Showdown in the
|
|
@@ -679,9 +702,9 @@ compatibility mode, the implications of these differences are outlined below:
|
|
|
679
702
|
when they are not relevant:
|
|
680
703
|
- Roar / Whirlwind roll to hit and can "miss" as opposed to simply failing
|
|
681
704
|
|
|
682
|
-
Finally, the **initial
|
|
705
|
+
Finally, the **initial 9-byte seed for link battles on Pokémon Red cannot include bytes larger than
|
|
683
706
|
the `SERIAL_PREAMBLE_BYTE`**, so must be in the range $\left[0, 252\right]$. This has implications
|
|
684
|
-
on the first
|
|
707
|
+
on the first 9 random numbers generated during the battle and has [**non-trivial competitive
|
|
685
708
|
implications**](https://www.smogon.com/forums/posts/9068411/show) (at the start of the battle move
|
|
686
709
|
effects become more likely, the ["1/256-miss" glitch](https://glitchcity.wiki/1/256_miss_glitch)
|
|
687
710
|
cannot happen, Player 1 is more likely to win speed ties, etc) that Pokémon Showdown cannot
|
|
@@ -705,7 +728,7 @@ All of places in the link battle code where randomness is required are outlined
|
|
|
705
728
|
| **Paralysis** (full) | `beforeMove` | Trigger if $X < 63$ |
|
|
706
729
|
| **Poison** (chance) | `Effects.poison` | Trigger if $X < 52$ ($103$ for Smog / Sludge) |
|
|
707
730
|
| **Sleep** (duration) | `Effects.sleep` | <dl><dt>Pokémon Red</dt><dd>Continue generating until $X \land 7 \neq 0$</dd><dt>Pokémon Showdown</dt><dd>Generate $X \in \left[1, 8\right)$</dd></dl> |
|
|
708
|
-
| **Bide** (duration) | `Effects.bide` | <dl><dt>Pokémon Red</dt><dd>Last for $\left(X \land 1\right) + 2$ turns</dd><dt>Pokémon Showdown</dt><dd>Last for $X \in \left[2, 4\right)$ turns</dd></dl>
|
|
731
|
+
| **Bide** (duration) | `Effects.bide` | <dl><dt>Pokémon Red</dt><dd>Last for $\left(X \land 1\right) + 2$ turns</dd><dt>Pokémon Showdown</dt><dd>Last for $X \in \left[2, 4\right)$ turns</dd></dl> |
|
|
709
732
|
| **Disable** (move) | `Effects.disable` | <dl><dt>Pokémon Red</dt><dd>Continue generating until $X \land 3$ is the index of a non-empty move slot</dd><dt>Pokémon Showdown</dt><dd>Generate $X \in \left[0, \|movesSlots\|\right)$</dd></dl> |
|
|
710
733
|
| **Disable** (duration) | `Effects.disable` | <dl><dt>Pokémon Red</dt><dd>Last for $\left(X \land 7\right) + 1$ turns</dd><dt>Pokémon Showdown</dt><dd>Last for $X \in \left[1, 9\right)$ turns</dd></dl> |
|
|
711
734
|
| **Metronome** (move) | `metronome` | <dl><dt>Pokémon Red</dt><dd>Continue generating until $X$ matches the index of a move which is not Struggle or Metronome</dd><dt>Pokémon Showdown</dt><dd>Generate $X \in \left[0, \|validMoves\|\right)$, where $validMoves$ is ordered set of moves with Struggle and Metronome removed <i>(indexes of moves > Metronome will be shifted down)</i></dd></dl> |
|
|
@@ -713,7 +736,7 @@ All of places in the link battle code where randomness is required are outlined
|
|
|
713
736
|
| **Psywave** (power) | `specialDamage` | <dl><dt>Pokémon Red</dt><dd>Continue generating until $X < {3\over2} \cdot level$</dd><dt>Pokémon Showdown</dt><dd>Generate $X \in \left[0, {3\over2} \cdot level\right)$</dd></dl> |
|
|
714
737
|
| **Thrash** (rampage) | `Effects.thrash` | <dl><dt>Pokémon Red</dt><dd>Last for $\left(X \land 1\right) + 2$ turns</dd><dt>Pokémon Showdown</dt><dd>Last for $X \in \left[2, 4\right)$ turns</dd></dl> |
|
|
715
738
|
| **Thrash** (confusion) | `beforeMove` | <dl><dt>Pokémon Red</dt><dd>Last for $\left(X \land 3\right) + 2$ turns</dd><dt>Pokémon Showdown</dt><dd>Last for $X \in \left[2, 6\right)$ turns</dd></dl> |
|
|
716
|
-
| **Binding** (duration) | `Effects.binding` | <dl><dt>Pokémon Red</dt><dd>Last for $\left(X \land 3\right) + 1$ further turns if $\left(X \land 3\right) < 2$<br /> otherwise last for $\left(Y \land 3\right) + 1$ further turns (reroll)</dd><dt>Pokémon Showdown</dt><dd>Last for $X \in \{2, 2, 3, 3, 4, 5\} - 1$ further turns</dd></dl> |
|
|
739
|
+
| **Binding** (duration) | `Effects.binding` | <dl><dt>Pokémon Red</dt><dd>Last for $\left(X \land 3\right) + 1$ further turns if $\left(X \land 3\right) < 2$<br /> otherwise last for $\left(Y \land 3\right) + 1$ further turns (reroll)</dd><dt>Pokémon Showdown</dt><dd>Last for $X \in \{2, 2, 2, 3, 3, 3, 4, 5 \} - 1$ further turns</dd></dl> |
|
|
717
740
|
| **Multi-Hit** (hits) | `Effects.multiHit` | *Ibid.* |
|
|
718
741
|
| **Unboost** (chance) | `Effects.unboost` | Trigger if $X < 85$ |
|
|
719
742
|
|