World Activity System

v1.0.0

Debug Window

Real-time monitoring and testing tools for activities and events.

Overview

The Event Scheduler Debug Window provides real-time monitoring and testing tools for activities and events. Use it during development to verify scheduling, test triggers, and optimize performance.

Editor Only: The Debug Window is only available in the Unity Editor. It has no runtime overhead in builds.

Opening the Window

Open via Unity menu: Window → Game Creator → Event Scheduler Debug

The window can be docked anywhere in your Editor layout. It updates in real-time during Play Mode.

Dashboard Tab

Overview of all registered activities and their current states

  • Spatial activities list with discovery/completion status
  • Temporal activities list with scheduler status
  • Quick stats (total, discovered, active, completed)

Timeline Tab

Gantt-chart style visualization of scheduled events

  • Visual timeline showing event schedules
  • Duration bars for active events
  • Conflict indicators for overlapping incompatible events
  • Zoom and pan controls

History Tab

Log of all activity and event actions

  • Timestamped event log
  • Filter by event type (discovery, activation, completion)
  • Search functionality
  • Export to file

Performance Tab

Scheduler performance metrics and optimization data

  • Cache hit rate percentage
  • Condition evaluation times
  • Memory usage
  • Optimization recommendations
Target Metrics: Cache hit rate >80%, condition evaluation <1ms average.

Tools Tab

Manual testing and debugging controls

[Details]

View full event info

[Trigger]

Force trigger event

[End]

Stop active event

[Reset]

Clear cooldown

Play Mode Required: Most tools only work during Play Mode when the scheduler is active.

Best Practices

Use Dashboard for Overview

Start with Dashboard tab to see overall system state before diving into details.

Monitor Cache Hit Rate

Performance tab shows cache hit rate. Target >80% for conditional events. Low hit rate indicates overly complex or frequently changing conditions.

Test with Tools Tab

Use [Trigger] to test events without waiting. Use [Reset] to clear cooldowns during development.

Check Timeline for Conflicts

Timeline tab highlights when incompatible events would overlap. Adjust priorities or timing to resolve.

Export History for Analysis

Use History tab export for analyzing event patterns over longer play sessions.