In this PlayBASIC devlog, I'm continuing work on the World command set, including recreating the existing sliding collision system and looking at how its internals can be improved.

The red ball in the demo shows the replacement collision code running alongside the original implementation. It's a useful way to compare the two, expose their limitations, and work through the awkward cases where multiple walls influence an object's movement. Most of the World functionality has now been replicated, with sticky collision still on the to-do list.

But this work is about more than replacing an old command set. It leads into a bigger discussion about the future of PlayBASIC, the current 1.65 development branch, and the road towards PlayBASIC 2.

Rather than attempting another huge rewrite where the compiler, runtime and command sets all change at once, the plan is to migrate PlayBASIC one subsystem at a time. This gives us the opportunity to keep a working foundation, test each replacement properly, and gradually remove the old DirectDraw dependencies without needlessly breaking the existing language.

I also talk about the new platform-independent display system, the Scene Buffer, legacy font commands, and why some of PlayBASIC's older graphics architecture needs a rethink. There's a look at asynchronous rendering too, including how background work can help keep classic 2D graphics running efficiently.

The goal is simple: small steps of migration rather than massive steps of innovation.