Don't hardcode OAM addresses
To display sprites, a program builds a display list in the first 160 bytes of a 256-byte page of WRAM, sometimes called "shadow OAM". Then the program copies it to OAM ($FE00-$FE9F) during vertical blanking (mode 1) by writing the high byte of the display list's address to $FF46. For example, if it places the display list at $C200-$C29F, it writes $C2 to $FF46.
Occasionally, programmers get the idea to define variables so as to hardcode the position of a particular actor in the display list, using code similar to the following:
player_oam_base = SOAM + $00 player_y = player_oam_base + $00 player_x = player_oam_base + $01 player_tile = player_oam_base + $02 player_palette = player_oam_base + $03
In all but the simplest cases, hardcoding OAM addresses of actors is an anti-pattern because it limits the ability to do several things:
- Separate the motion of the camera from motion of game objects
- Change the size of a cel later on, in case some cels need more sprites than others
- Draw a cel half-offscreen
- Reuse movement logic among multiple actor types
- Turn objectionable dropout into less objectionable flicker by varying from frame to frame which sprite appears earlier in OAM
A better way:
- Keep separate variables for each actor's position in world space that are stored outside of the display list. Also keep variables for the camera's position.
- Each frame, clear a variable denoting how many bytes of shadow OAM have been filled so far.
- Each frame, fill shadow OAM from start to finish based on the position of the actor, plus the position of the individual sprites within the actor's cel, minus the position of the camera.
- Clear the Y coordinates of unused sprites.
That way, you can perform flicker by varying the order in which actors are drawn during step 3. And if you skip drawing a sprite because it is offscreen, you can skip increasing the OAM used variable.