Everything here follows the same three rules. They are what decides whether an asset is still useful six months after you drop it in.
Documentation
Every tool ships with documentation that covers the parts people actually get stuck on: what it does not do, which Unity versions it targets, and the error you will hit if you wire it up wrong. The docs are public and readable before you buy, because deciding a tool is wrong for your project should cost nothing.
Source
Open the files and you will find plain C# with names that say what things are, comments where the reasoning is not obvious, and a folder layout you can navigate without a map. Changing behaviour should mean editing one clear place, not tracing a call through six abstractions first.
Support
Questions get a direct answer, not a forum thread that dies unanswered. Every asset has an update schedule and a changelog that says what changed and why, not that this release contains improvements and bug fixes.
What shipped lately, across every tool.
Nothing shipped yet
Release notes appear here as tools ship. Every update gets a changelog that says what changed and why.
About
Everything here started as a problem in an actual project. Solved properly once, then cleaned up and documented because it was worth sharing.
Each asset stays inside its own boundaries. It handles what the title says and leaves the rest of your project alone, so adding it does not turn into a week of rewiring. You should be able to drop it into work that is already underway and carry on.
Questions get an answer within two business days, from someone who knows the code. If something here does not fit your project, the honest answer is faster than a sale.
