George
881f716115
forceUpdateRegion crashed with "no profiling cycle is active" because runModulesForRegion calls profiler.beginModule() which requires an active cycle. Wrapped the call in startCycle/endCycle in a try/finally. Regions showed tick=0 and no module data because SimulationScheduler's priority queue was never populated for normal rolling updates — only explicit queueRegion() calls worked. Fixed by auto-enqueueing all active regions in onMinecraftServerTick() just before each simulation cycle fires. Auto-enqueueing is placed there (not in runSimulationCycle()) so unit tests that drive cycles directly are unaffected. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>