nesdev.org

Ok I understand. So I create an array for each object attribute, with the length of the maximum object count? object_x: .db $00,$00,$00,$00,$00,$00,$00,$00 object_y: .db $00,$00,$00,$00,$00,$00,$00,$00 ;keep going I barely know about CPU cycles and the cost of instructions. Would this method be less...

thanks for your reply.
I already thought about that but i want to keep things consistent.
My idea was to create a system that I can apply to any future project. Like a template.
I don't know if it's a good idea for such a limited system

Hello guys! I'm pretty new to NES development and tried creating my first dynamic object manager. Each object contains of 16 byte (x,y,sprite_address_high,sprite_addres_low,sprite_count,update_address_high,update_address_low, <some object related variables > ) I built a generic update function that ...