This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
super:data_locations:sprite_obj_locations [2020/03/07 16:12] – Identified an entry i thought was unused mccad | super:data_locations:sprite_obj_locations [2020/03/07 16:20] (current) – Finishing and using your new sprite objects mccad | ||
---|---|---|---|
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. | 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' | ||
+ | |||
+ | In summary: Sprite Objects are driven and controlled by their Instruction Lists, which point to and animate their spritemaps. |