Glitch City RAM manipulation (Cut abuse): Difference between revisions
Jump to navigation
Jump to search
Content added Content deleted
>ISSOtm m (→Reaching the correct place: Corrected my previous (missclicked) edit.) |
>ISSOtm m (→Possible values: Added the TileBlockDex.) |
||
Line 67: | Line 67: | ||
==Possible values== |
==Possible values== |
||
Obviously, we need the value of the byte we want to change to spawn a cuttable tree. Good news, there is a few values that do just that |
Obviously, we need the value of the byte we want to change to spawn a cuttable tree. Good news, there is a few values that do just that. |
||
Here is a conversion table for hex value <-> 2x2 tile block, called the TileBlockDex : |
|||
[[File:TileBlockDex.png]] |
|||
You can see that a few blocks have CUTtable trees on them ; they are summarized in the tables below. |
|||
Hexadecimal conversion table : |
Hexadecimal conversion table : |
||
Line 87: | Line 93: | ||
|6E |
|6E |
||
|} |
|} |
||
Refer to [[The Big HEX List]] for corresponding Pokémon, Items and Attacks. |
|||
Decimal conversion table : |
Decimal conversion table : |