I started building AceLand packages back in 2020. Unity is powerful precisely because it is so open and unopinionated, but that same freedom turns long-term projects into a maintenance nightmare, where every team ends up reinventing the same plumbing in slightly incompatible ways. My answer was to stop rebuilding the foundation on every project and instead package it once, properly. That is why the core of AceLand is not flashy features but framework and background services, things like Event-Driven messaging and State management, together with agent services such as Task Utils and Web Request that quietly do the heavy lifting underneath the game.

​

These packages were never written in isolation. I built and hardened them on real production work, and as I used them day to day, more focused library and tooling packages grew out of genuine needs, including Curve, Command History, and Kalman Filter. Each one exists because I hit the problem myself and wanted to solve it once, cleanly, and never again. The result is a toolkit that lets me finish tasks with high efficiency and high quality, because the difficult, error-prone parts are already solved, tested, and reusable.

​

In 2026, as Unity moves toward CoreCLR, I decided to take this further. AceLand packages are being rebuilt around the modern runtime, with no reliance on domain reload, and released under a model I call "Open Core, Paid Editor Tools": the runtime that ships inside your game stays open source and free forever, while the development-time editor tooling that makes the packages easier to inspect, verify, and optimize is offered under a paid license. The sections below explain how this model works in practice and what it means for you.