388
edits
No edit summary |
No edit summary |
||
Line 692: | Line 692: | ||
| 0xf00c || 0x0811c6f8 || 9 || UI_CreateItemNotification(p=position, t=sprite?) | | 0xf00c || 0x0811c6f8 || 9 || UI_CreateItemNotification(p=position, t=sprite?) | ||
|- | |- | ||
| 0x3535 || 0x0811d4f4 || 2 | | 0x3535 || 0x0811d4f4 || 2 || Map_LoadGraphics(t=?, c=?, d=?) | ||
| | |||
|- | |- | ||
| 0x4383 || 0x0811dfbc || 11 || | | 0x4383 || 0x0811dfbc || 11 || | ||
Line 725: | Line 718: | ||
| 0xe4b1 || 0x08121adc || 2 || | | 0xe4b1 || 0x08121adc || 2 || | ||
|- | |- | ||
| 0x11d4 || 0x08121bd4 || 385 | | 0x11d4 || 0x08121bd4 || 385 | ||
| Video_LoadTileSet(t=type, c=part ids, d=tile set file id, m=tile map file id, s=load offset) | |||
t: Type; only two relevant cases: If 0 (=BG0), then load offset will be ''forced'' to 0x400 tiles, irrespective of the m and s keywords. Otherwise, the m and s keywords are used.<br> | |||
c: [[Tile set file]] part IDs to load (1-n)<br> | |||
d: Tile set file ID<br> | |||
m: [[Tile map file]] ID, only used to determine the load offset.<br> | |||
s: Load offset in tiles<br> | |||
''Load offset explanation'': Tiles are copied into VRAM starting at that offset. By specifying different load offsets for different tile sets, multiple tile sets can coexist in VRAM simultaneously. If both m and s are specified, m takes precedence. | |||
|- | |- | ||
| 0xca7d || 0x08122370 || 31 || | | 0xca7d || 0x08122370 || 31 || |