404
edits
Engine calls (Boktai 1): Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 256: | Line 256: | ||
| 0xb8b9 || 0x081cee2c || 6 || | | 0xb8b9 || 0x081cee2c || 6 || | ||
|- | |- | ||
| 0xc0b0 || 0x081d02c4 || 361 || | | 0xc0b0 || 0x081d02c4 || 361 || Camera_Create() | ||
|- | |- | ||
| 0x430d || 0x081d0bc8 || 920 | | 0x430d || 0x081d0bc8 || 920 | ||
| Line 276: | Line 276: | ||
Copies values into the indexed-ptr. Partial writes are supported (you can specify less values than the size of the indexed-ptr). | Copies values into the indexed-ptr. Partial writes are supported (you can specify less values than the size of the indexed-ptr). | ||
|- | |- | ||
| 0x7636 || 0x08000b98 || 256 | | | 0x7636 || 0x08000b98 || 256 | ||
| Loop(a=argument count of callback, r=number of executions, d=data to loop over, e=callback block) | |||
This is complicated, need some examples... keywords "a" and "r" are always required, keyword "d" is optional: if provided, the loop behaves like a "for each" loop over the provided data, if not provided it behaves like a "for" loop between 0 and r. | |||
|- | |- | ||
| 0x3469 || 0x08000c54 || 141 | | 0x3469 || 0x08000c54 || 141 | ||
| Line 692: | Line 694: | ||
| 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 720: | ||
| 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 || | ||
| Line 1,055: | Line 1,057: | ||
| 0xcaee || 0x081cfa14 || 15 || | | 0xcaee || 0x081cfa14 || 15 || | ||
|- | |- | ||
| 0x2a8c || 0x081cfa6c || 296 || | | 0x2a8c || 0x081cfa6c || 296 || Camera_ConnectToTilemap(...) - Positions the camera on the tile map (call every frame) | ||
|- | |- | ||
| 0x063b || 0x081cfb84 || 37 || Camera_SetBounds(min_x, max_x, min_y, max_y) | | 0x063b || 0x081cfb84 || 37 || Camera_SetBounds(min_x, max_x, min_y, max_y) | ||