Editor Tools

Review draft. This source page has not completed website editorial and release-specific verification.

Both tools open from the shared Director Suite menu. They are registered by SignalBus and remain available when SignalBus is the only Director product installed.

SignalBus Runtime Inspector

Path: Tools → Director Suite → Runtime Inspectors → SignalBus Runtime Inspector

The Inspector is strictly read-only. It observes snapshots for active World and Game Instance contexts and shows active subscriptions, pending queued messages, diagnostic event history, warnings, warning severity/status, and selected-row details. The Broadcast Graph is also observational.

Use the context picker to select a PIE context. Search matches event type, message/topic ID, payload type, publisher, subscriber, scope, dispatch mode, queue ID, and captured payload text. Types is a multi-select filter for event kinds present in retained history. Columns controls history-table presentation and Reset Columns restores common debugging fields. Disable Auto Refresh to freeze the displayed snapshot; Refresh updates it manually.

The Inspector does not enable or disable diagnostics, change payload capture policy, change warning analysis, clear retained history, or clear warnings. Use Runtime Controls for those actions. Opening Runtime Controls from the Inspector does not alter the selected runtime context.

SignalBus Runtime Controls

Path: Tools → Director Suite → Runtime Controls → SignalBus Runtime Controls

Select a World or Game Instance context before changing its settings.

Control	Consequence
Diagnostics Enabled	Enables or disables diagnostic event capture for the selected context.
Warning Analysis Enabled	Enables or disables warning analysis for the selected context.
Payload Capture	Changes the payload detail retained in future diagnostic snapshots.
Clear History	Removes retained diagnostic events for the selected context. It does not change message delivery.
Clear Warnings	Removes retained warning records for the selected context. It does not change message delivery.

These settings and clearing actions use the existing subsystem APIs and do not change routing or subscription state.