Unity Asset Store Plugins & Custom Unity Tools

Every game team eventually hits a point where off-the-shelf tools don't fit their workflow. I build Unity Editor windows, custom inspectors, ScriptableObject-based data pipelines, build automation tools, and runtime debug overlays.

Common tool categories I've delivered: level editors, asset import processors, localisation management systems, screenshot and trailer capture tools, procedural content generators, and custom shader graph nodes.

I have a deep understanding of what makes an Asset Store package succeed: not just the technical quality of the runtime code, but the demo scenes, the documentation, the inspector UX, the API design, and the support experience.

If your studio has built an internal tool that would be valuable to the broader Unity community, I can help you prepare it for commercial release: refactoring for public API quality, writing comprehensive documentation, building demo scenes, and setting up a support channel.

Sometimes the challenge isn't building a new tool but integrating an existing one, or migrating away from a deprecated package. I offer plugin integration audits: a review of your project's third-party dependency tree, identifying risks and recommending a migration path.

I'm also familiar with the most common Asset Store plugins, Odin Inspector, DOTween, Addressables, TextMesh Pro, Cinemachine, Shader Graph, and can help your team get the most out of tools you've already purchased.

I publish and maintain 16+ commercial Unity plugins on the Asset Store, so the tools I build for clients follow the same standards I apply to my own products. A few examples from the catalogue:

• Touch Camera PRO: a mobile, desktop, and console camera controller with perspective switching.
• Level Designer: a real-time level editor that runs inside your game or app.
• Tutorial Engine: a system for creating step-by-step tutorials and displaying them whenever your game needs them.
• Home Designer Suite: tools to design, furnish, and light interior spaces directly inside the Unity Editor.

Some packages are complete projects rather than tools: RE-PAIR, a physics-based multiplayer party game built in Unity, is also available as a full Unity project.

Tool projects follow the same process as my other engagements, adapted for pipeline work.

• Discovery call (30 minutes, free): you walk me through the workflow that slows your team down today, who will use the tool (programmers, designers, or artists), and which Unity version and render pipeline you are on.
• Written proposal within 48 hours: the tool's scope, deliverables, milestones, and timeline. For a package headed to the Asset Store, this includes documentation and demo scenes.
• Milestones with weekly builds: each week you get a working version to try inside your real project, because a tool only proves itself in the hands of the people who use it every day.
• Handover: source code, documentation, and a walkthrough for your team. Fixed-price projects include a post-delivery support period for bug fixes and questions.

• Source code you own, organised with Assembly Definitions so editor-only code never ends up in your builds.
• Inspector and editor UX designed around the people who will use the tool, with sensible defaults and clear validation messages.
• Documentation: a quick-start guide, a reference for every public class and method, and a troubleshooting section.
• Demo scenes that show each feature on its own.
• Compatibility notes listing the Unity versions and render pipelines the tool has been tested with.

Tool work uses the same published rates as my other services, detailed on the hire page:

• Fixed-scope projects start from $5,000 and suit a clearly defined tool, or an internal tool being prepared for public release.
• Time and materials at $500 to $1,500 per day suits smaller utilities, plugin integration, and dependency audits, where the work takes days rather than weeks.
• Monthly retainers cover Unity version updates, bug fixes, and small feature additions after delivery.