Skip to content

Editor Entry Points

This page simply shows where to find things in the Unity Editor

RevFramework includes a set of optional editor utilities for inspection, debugging, and advanced workflows.

These tools are not required to use the framework. If you prefer to work directly in code and inspectors, you can safely ignore them.

Tools Menu

Most one-shot actions, wizards, and utilities live under:

Tools ▸ RevGaming ▸ RevFramework ▸ …

Examples include:

  • Export helpers
  • Setup and creation wizards
  • Generators and maintenance utilities
  • Validation and cleanup tools

These tools perform a single task and then exit.

Window Menu (Dockable Debuggers)

Each system with a debugger exposes it at the same place:

Window ▸ RevFramework ▸ <System> ▸ Debugger

Available for Inventory, Crafting, Currency, Health, Status and Loot. A system whose package you do not have simply has no entry — the editor assembly only compiles when that system's REV_*_PRESENT define is set.

These windows allow you to:

  • Inspect live runtime state
  • Debug rule execution and ordering
  • Observe decisions, gates, and failure reasons
  • Interact with systems during Play Mode

The Loot debugger answers a different question

The others show you what a system is doing right now. The Loot one samples a table — it rolls it many times and reports the distribution that actually came out, so authored weights can be checked against what they produce rather than what they look like.

It needs no Play Mode, because rolling is a pure function.

They can be docked alongside the Inspector, Hierarchy, or Game view.

Project Window (Create Menu)

Some systems expose shortcuts in the Project window:

Assets ▸ Create ▸ RevFramework ▸ <System> ▸ …

These create common assets such as:

  • Definitions
  • Presets
  • Data containers

All generated assets are fully editable and optional.

Important

Editor-only, and never required

  • All editor tools are Editor-only and are not included in builds
  • Nothing here is required to use the runtime systems
  • These tools exist to support debugging and deeper workflows

If you are unsure whether you need a tool, you probably don’t.

Summary

They are there to help — not to get in your way

  • Editor tools are optional
  • Runtime systems do not depend on them
  • Use them when you need visibility or convenience
  • Ignore them if you don’t