Avoiding a new foundation for every game
Why I am bringing recurring battle systems into a Unity framework.
A retrospective on 2 October 2026. Written and published on 14 October 2026 using the project history.
A battle game brings familiar jobs: configuring units, assembling waves, distributing resources and changing the battlefield. I do not want to collect those pieces from scratch for every project.
Battle Framework brings them into a modular Unity template. Its central interface is the Game Manager, where related settings belong together.
The early October build contains that foundation and a demo. It is not a finished release. Controls and behaviour in actual play still need visual review.
The next useful view would follow one unit from the Game Manager into the demo. A suitable capture is still missing here.