is presently its sole maintainer,
You can support him:
Continuing yesterday's work on collision detection
Writing the wall intersection detection
Fixing backward movement
Fixing divide by zero
Actually move the player
Description of partial wall penetration
Adding the remaining wall tests
New problem: walking through the top wall due to floating point precision loss
Implementing a temporary fix
Looking for another bug causing the character to stop early
Debugging an assertion failure
More collision bugs; time to write a better collision detection system!
Observing the problems with the current collision detection system
What we want from the new system
Can you change the whiteboard colors?
Do you plan on getting into calculus to get better collision detection?
Do you think any need to prototype some features in some other language?
If we changed the resolution of the game, would it change the size of the objects?
Can you do collision detection based on if a bitmap and a pixel has alpha?
Is it interesting to have a tutorial on floating-point computations?
Why not use the old collision system and use the new one only if it finds a collision?
What about the tiles? Will they stay the same if you change resolution?
What is dynamic loading? I thought C code has to be compiled.