Author's Note — What These Tools Are, and What They Aren’t
There’s a moment most game developers know well: you’ve built something that genuinely solves a real problem — something you wish had existed six months ago — and you think, someone else is going to hit this exact wall. That’s where these tools come from. Not from a product roadmap or a QA cycle, but from the actual workbench of someone making games.
What you’re getting is a working, thoughtful tool built by a developer for developers — tested in real projects, documented in good faith, and backed by genuine support. It handles its stated use cases reliably, and often well beyond that. What you are not getting is a hardened commercial product with a team behind it. That’s also true of the majority of what’s on the Asset Store — but most authors won’t say it out loud. I will.
Each tool is documented for its intended use cases, and within those it performs well. Edge cases or applications that fall well outside the described scope may not behave as expected — that’s the honest reality of any independently developed tool, and each tool’s own documentation will be upfront about where the edges are. What I can tell you is that when something doesn’t work the way you need it to, I am reachable on Discord (https://discord.gg/HadwVTP3r5) and will do my genuine best to help.
The price I charge isn’t about profit. It’s the signal that says this is worth my continued effort. Every purchase is a vote that says: keep building. I’m not asking anyone to keep something that truly doesn’t serve them — but before you decide, I’d ask you to consider not just “is this perfect?” but “is this useful? Do I want developers like this to keep contributing to the ecosystem I work in?”
If your expectation is Unity-corporate-grade polish and team QA, this isn’t the right fit — and I’d rather you know that now than be disappointed later. But if you value a real developer sharing real tools and standing behind them personally, I think you’ll find genuine value here.
—BBB