miner28_3

Data Debugger

Data Debugger is a free Miner28 utility script for logging VRChat DataDictionary, DataList, and DataToken values in a readable JSON-like format.

GitHub World Utilities Udon Tool
Browse VRChat Assets
Pricing Free
Published 25 May 2026
Author miner28_3

Data Debugger

Original source: GitHub Gist by miner28_3. Data Debugger is a small utility script for logging DataDictionary, DataList, and DataToken values in a readable JSON-like format, including common reference values inside the data.

Use it when a world script builds nested data and the normal Console output is too hard to inspect. Use the original listing to review and import the current code from the publisher.

Original Listing: GitHub SDK Note: 3.5+ Submitted by: miner28_3

Category: Utility Tools

What It Does

  • Adds debug helpers for VRChat data containers.
  • Walks through nested dictionaries and lists.
  • Converts supported references into readable values before logging.
  • Uses VRChat JSON serialization so complex data is easier to inspect in the Unity Console.
  • Helps when testing parsers, remote data, save data, or runtime state.

Good Uses

Use Case Why It Fits
Debugging parsed JSON You can inspect nested keys and values after VRCJson parsing.
Checking generated dictionaries Runtime-built DataDictionary values are easier to review as structured output.
Inspecting lists of tokens Nested DataList content can be logged without manually walking every item.
Finding reference values Common object references can be converted into readable names or display values.

Setup Review

This is a source-script utility rather than a packaged prefab. Before using it in a live project:

  1. Open the original GitHub Gist and review the current script.
  2. Confirm the project is using a compatible VRChat SDK and UdonSharp setup.
  3. Add the script to a test project first.
  4. Call the debug helper only from controlled test code.
  5. Check the Unity Console output with small sample data before trying large nested payloads.
  6. Remove or disable noisy debug calls before publishing the world.

VRChat Debugging Notes

Debugging tools are useful during development, but they can become expensive or noisy if left active:

  • Avoid logging large data structures every frame.
  • Be careful with data that could include private, moderation-sensitive, or player-specific values.
  • Keep debug helpers out of production paths unless they are intentionally guarded.
  • Test late join, ownership, and synced data separately if the data depends on networking.

Related Content

Prefab Setup Notes

Import the prefab or script into a throwaway test scene before adding it to a live world. Confirm inspector references, ownership behavior, sync, triggers, UI hooks, and audio or object links before moving it into the production scene.

Testing Checklist

  • Test once as a local player and again with a second client or late joiner if the behavior can affect more than one player.
  • Confirm ownership, sync, trigger zones, UI references, and audio or object references are assigned intentionally.
  • Confirm debug logs are readable with a small sample before sending large nested data.
  • Remove temporary debug calls before uploading a public build.
  • Check desktop and VR interaction distance so players can actually use the feature in context.
  • Keep a backup of the scene before changing prefabs, UdonBehaviours, or serialized references.

Related Pages

Official References

Listing Details

Import Notes

  • Use the external listing for current package contents instead of relying on copied files or outdated notes.
  • Use the original listing for the latest download, release notes, pricing, and license details.