Mord's Blog

If you can spare a byte or two to keep track of what objects collided, that might be helpful, especially if you run the main game loop at 30Hz but can run the flicker routine at 60Hz.

If you can spare a byte or two to keep track of what objects collided, that might be helpful, especially if you run the main game loop at 30Hz but can run the flicker routine at 60Hz.

 

I ended up using two bytes to help track the gates afterwards. RoomGateKey, and GateMask. GateMask was used to help generalize the routine used for gate movement and key-gate collisions. All I have to do is have the gate's AI set their values. Loading a new room will (eventually) set both of those to 0 to make sure we don't have the code messing up objects it shouldn't be touching.

 

RoomGateKey equals the object ID of the key to trigger it. GateMask is essentially a bit selector to use on the CastleGates byte. (CastleGates keeps track of whether each gate in the world is open or closed.)

 

I just finished debugging the new code and the gate collisions now appear to be 100% reliable. I'll update the main blog entry with a beta for 0.018 - the next thing (and last thing for this version) is the conversion to a 16k rom format. Should be a lot easier to do this time now that I've separated different portions of the code.