Difference between revisions of "Riven RMAP resources"
From A look inside The Link @ wiki
(import) |
m (TOC) |
||
| Line 1: | Line 1: | ||
| + | <noinclude>{{Riven}}</noinclude> | ||
There's just one RMAP resource per Mohawk file. Its function is to assign a unique code to each card. The resource is just a block of records, each having the following structure: | There's just one RMAP resource per Mohawk file. Its function is to assign a unique code to each card. The resource is just a block of records, each having the following structure: | ||
Revision as of 04:15, 6 February 2008
| Riven | |||
| Mohawk | Overview | ||
| BLST | CARD | FLST | HSPT |
| MLST | NAME | PLST | RMAP |
| SFXE | SLST | tBMP | tMOV |
| tWAV | VARS | VERS | ZIPS |
| Scripts | Variables | ||
| External commands | |||
There's just one RMAP resource per Mohawk file. Its function is to assign a unique code to each card. The resource is just a block of records, each having the following structure:
| unsigned long | card_code |
The corresponding card is the one with resource ID equal to the record index, so the record count in the RMAP is equal to the greatest ID of CARD resources. The card code is used when going to another stack with command 27: it specifies the destination card in the new stack.
If you are familiar with the engine "b3hn" debug shell, the CyanCardID value is exactly the card code specified in the RMAP resource.
