Engine calls (Boktai 1): Difference between revisions

Engine calls (Boktai 1) (view source)

Revision as of 16:54, 14 October 2024

1,508 bytes added , 14 October

no edit summary

VisualWikitext

Raphi

Bureaucrats, Interface administrators, Administrators

388

edits

@@ Line 152: / Line 152: @@
 | 0xb4b4 || 0x081217d0 || 78 ||
 |-
-| 0x4ae5 || 0x08122bb0 || 28 || Palette related (p=3x palette file ids)
+| 0x4ae5 || 0x08122bb0 || 28 || Load [[Master_file_table|background palette]] file  (p=3x palette file ids)
 |-
 | 0x329b || 0x08123e54 || 6 ||
@@ Line 693: / Line 693: @@
 |-
 | 0x3535 || 0x0811d4f4 || 2
-| Map_LoadGraphics(t=?, c=?, d=?)
+| Video_LoadTileSet(t=type, c=part ids, d=tile set file id, m=tile map file id, s=load offset)
-‘c’ and ‘t’ might be a paired tileset id?
+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.
 |-
 | 0x4383 || 0x0811dfbc || 11 ||
@@ Line 708: / Line 713: @@
 | 0x6255 || 0x08120f84 || 9 ||
 |-
-| 0x7a27 || 0x08121998 || 83 || spawn fog?
+| 0x7a27 || 0x08121998 || 83
+| Video_LoadTileMap(d=file id, t=type, n=layer count, i=layer indices, c=layer IDs)
+d: [[Tile map file]] ID<br>
+t: Type, how layers are assigned to GBA background layers: 0=BG0, 1=BG2+BG3, 2=BG3, 3=BG1, 4=BG1+BG3, 5=BG2+BG1, 6=BG2+BG3=BG1, else=BG2 but invisible in REG_DISPCNT)<br>
+n: Layer count, how many layers to load. Defaults to 1. For example, t=4 and n=1 would load only BG1, t=4 and n=2 would load BG1 and BG3.<br>
+i: Layer indicies: Specifies which layers to load from the tile map file, via indices into its layerDefinition array.<br>
+c: Layer IDs: Specifies which layers to load from the tile map file, by referencing the TileMapLayer.id field<br>
+Precedence for layer selection: keyword i, else keyword c, else defaults to [0, 1, 2].<br>
+If the tile map file contains a tile set, it will also be loaded into VRAM as well.
 |-
 | 0xe4b1 || 0x08121adc || 2 ||
@@ Line 1,026: / Line 1,039: @@
 | 0xbec2 || 0x081ced7c || 19 ||
 |-
-| 0x30ad || 0x081cf048 || 29 ||
+| 0x30ad || 0x081cf048 || 29 || Map_LoadMap(p=[[Map file]] ID, ...=?)
 |-
 | 0x7539 || 0x081cf130 || 40 ||