Differences

This shows you the differences between two versions of the page.

--- super:data_locations:sprite_obj_locations [2020/03/05 00:48] – Notes for the sprite object table mccad
+++ super:data_locations:sprite_obj_locations [2020/03/07 16:20] (current) – Finishing and using your new sprite objects mccad
@@ Line 36: / Line 36: @@
 | 0A    | Dust 1     | #$0000        | |
 | 0B    | Dust 2     | #$0000        | |
-| 0C    | Unused? Explosion     | #$0000        | |
+| 0C    | Small explosion from the large enemy death AI     | #$0000        | |
 | 0D    | Small health pickup     | #$0000        | |
 | 0E    | Large health pickup     | #$0000        | |
@@ Line 140: / Line 140: @@
 Custom spritemaps for sprite objects can be placed anywhere within the bank. Assuming you really know what you're doing, you could also potentially write a custom instruction to load a spritemap from a long address, but without doing so, spritemap load instructions can only be preformed using short addresses.
+----
+===== Finishing and using your new sprite objects =====
+Once you have assembled all of your desired spritemaps, and have written an instruction list which utilizes them, all that is left to do is add the entry to your Sprite Object Pointer table, and call it ingame.
+In order to add the new Sprite Object to your pointer table, simply add the address of your instruction list to the pointer table. Make note of this new pointer's location within the table, as you will need to use this index within the table to spawn your sprite object. Once again, this index can be calculated by dividing the new pointer's offset from the start of the table by 2.
+In summary: Sprite Objects are driven and controlled by their Instruction Lists, which point to and animate their spritemaps.

User Tools

Site Tools

Differences

Page Tools