diff options
| author | aaaaaa123456789 <aaaaaa123456789@acidch.at> | 2021-05-30 06:16:03 -0300 |
|---|---|---|
| committer | aaaaaa123456789 <aaaaaa123456789@acidch.at> | 2021-05-30 06:16:03 -0300 |
| commit | 65a327e7331d8a4eff262b4957ae9ad1347e640a (patch) | |
| tree | 9e4f570fcd8991e1006a59d2e48eabe35582b4f3 | |
| parent | 44436ec88a6a8941d83ee1a813bde686ad4275a4 (diff) | |
Forgot to delete a blank line
| -rw-r--r-- | Smashing-rocks-has-a-chance-to-contain-items.md | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/Smashing-rocks-has-a-chance-to-contain-items.md b/Smashing-rocks-has-a-chance-to-contain-items.md index 53a25bd..2bda45f 100644 --- a/Smashing-rocks-has-a-chance-to-contain-items.md +++ b/Smashing-rocks-has-a-chance-to-contain-items.md @@ -80,7 +80,6 @@ We have to define `RockItemEncounter`, and a suitable place to put it would be i + db 48, PEARL + db 64, BRICK_PIECE + db -1 -+ ``` For starters, `RockItemEncounter` will load the `.RockItems` table into `hl`, and then call `Random`, which will load a random byte (i.e., a value between 0 and 255) in `a`. With this random value generated, it performs comparisons against the probabilities encoded in the `.RockItems` table, picking an item with the listed odds (out of 256: in the example, there's a 1 in 256 chance of getting a Max Revive, and a 64 in 256 (or 1 in 4) chance of getting a Brick Piece). |