Tests before listings.
Each package gets automated coverage before the Asset Store ever sees a .unitypackage. Behavior is pinned by tests, not hopeful copy.
Avanatro Tools · Workshop
Where Unity tools get boring on purpose.
A one-person studio building Asset Store packages with the kind of unglamorous engineering that saves production days: tests first, clean imports, explicit failure modes and support from the author who wrote the code.
vanilla Unity first
CI before listings
72h support window
01
Verify
tests pass
edge cases pinned
02
Package
clean import
no hard deps
03
Document
examples compile
support notes ready
asset-check --unity 2021.3
docs smoke-test --examples
package status: ready
SaveStack
shipping first
shipping first
10-tool suite
built in public
built in public
01
Dogfood
used in Avanatro projects before it becomes a product
02
Stabilize
unit tests, migrations, import checks and bad-path cases
03
Explain
API docs, examples, quickstarts and honest limits
04
Support
same desk as the code, no outsourced help maze
Position
Small tools, serious maintenance.
Most Unity Asset Store plugins ship like prototypes and get sold like infrastructure. Avanatro Tools takes the opposite bet: fewer packages, clearer contracts and boring operational behavior before the listing page gets polished.
No subscriptions. No telemetry. No funded roadmap theater. The output is intentionally narrow, because a Unity plugin only becomes useful when it can survive somebody else's project constraints.
ruleBuy once, own forever.
ruleNo phone-home code.
ruleExamples must compile.
ruleSupport is author-level.
Method
What gets checked before a tool ships.
Zero hard dependencies.
No required third-party framework just to make a tool run. Provider interfaces stay available when a project needs a different backend.
Failure modes first.
Crash safety, corrupt files, broken migrations, path traversal and awkward Editor states get treated as product work, not later chores.
Docs as part of QA.
Quickstarts, examples and API pages are checked as real usage surfaces. If the docs imply a workflow, the package has to support it.
Editor tools that behave.
Custom windows never autostart, never interrupt play mode and stay under predictable menus. Tools should disappear until needed.
Dogfood before polish.
The catalog grows from systems used in Avanatro games and tools first. Product pages come after the tool has met real project friction.
Catalog direction
The workshop is a pipeline, not a content farm.
shipping
SaveStack
Atomic saves, encryption, migration and editor helpers for Unity projects that cannot afford fragile persistence.
suite Avanatro ToolsUI, audio, dialogue, text, localization and workflow packages converging into one coherent Asset Store bundle.
dogfood Browser gamesSmall public games keep the tooling honest: real releases, real UX pressure, real save and flow needs.
What this is not
No hidden tax on your project.
- No subscriptions or renewal lock-ins.
- No telemetry, phone-home code or analytics SDK hidden in the package.
- No "register your asset to unlock features" ceremony.
- No private Discord support gate.
- No roadmap claims for features that are not in the shipping build.
Contact
Found a bug, planning a build, or checking commercial fit?
Email the plugin name and Unity version. You get a human answer from the same person maintaining the package.