Ebb And Flow Of Code Design

Code is a sand castle on a beach. Code design is the rising and falling tides. Some times it will reach up and take a bit of the castle, causing you to rebuild part of it. Sometimes it won't even touch it, or it could completely swallow it whole causing you have to start over.

So why the metaphor you might ask? Because no code is ever concrete, not even when a game is released.

This applies to what I'm currently working on. A new type of collision detection system. I won't get into the finer details or than this. It allows for a greater number of different collisions to go on than before. This is useful considering the number of features that we would like to add in later.

How it works is each entity is assigned to a group. Environment, Stationary Intervactive, Movable Interactive, and Characters. Of couse I might add more to add more filtering. For example bricks, ladders and caged ladders are all assigned to the environment group with a bitmask to filter them. Before I was assigning one bitmask to each entity, the problem is that Panda only has 32 bitmasks for filtering.