PersistKit Inspector - VRChat persistence QA

A Unity Editor audit tool for VRChat persistence.

PersistKit Inspector helps you check what your world is saving before you upload it.

It is made for VRChat world creators using PlayerData, PlayerObjects, save slots, settings, inventories, leaderboards, player progress, unlocks, or any UdonSharp system where players expect their data to come back next time.

Persistence bugs are awkward because they often look fine while you are building. A key is a little too generic. A prefix is missing from one setting. A save slot uses a slightly different naming pattern. A PlayerObject prefab has synced fields, but the persistence setup is incomplete. ClientSim has local data that makes a test pass, but the uploaded world still needs its own check.

PersistKit gives you a proper review pass for that. Run a full audit and it scans your loaded scenes, C# source files, local ClientSim JSON, and any keys you add manually. The result is an audit asset you can reopen, edit, compare, export, and keep with your release notes.

The Dashboard gives you the quick read: release readiness, open issues, PlayerData storage estimates, validation status, PlayerObject counts, and the next things worth checking. The Audit tab shows the actual PlayerData findings, including source location, confidence, value type, prefix status, estimated raw size, and warnings for keys that look risky.

PlayerObject scanning checks loaded scenes for `VRCPlayerObject`, `VRCEnablePersistence`, UdonSharp behaviours, synced fields, and setup warnings. The ClientSim tab shows local PlayerData and PlayerObject JSON files, with tools to refresh, back up, import, export, or clear data when you need a cleaner local test.

Reports are built in. Export Markdown or JSON for a release record, compare two audit snapshots to see which keys were added or changed, and use the validation checklist to track the uploaded tests that still need a human pass.

There is also a save-slot key generator for creating consistent C# constants, useful when you are using prefixed keys like `rpg.A.level`, `rpg.B.level`, or `rpg.C.coins` instead of trying to manage slot names by hand.

No code changes are required to use the tool. Open `Tools > RubyNouille > PersistKit`, choose your namespace prefix, and run a full audit.

PersistKit is not a replacement for testing an uploaded VRChat build. It is the step before that: the part where you find the obvious naming mistakes, missing setup, suspicious storage growth, stale ClientSim data, and risky key changes while they are still easy to fix.

If your world uses persistence, PersistKit gives you a clearer answer to the question everyone eventually has to ask: what are we actually saving, and is it safe to ship?