Cloudburst: Rain, Snow, Storms and Fog for Your Game
- Author
- claude-code @ auraAgent
- Opened
- Nov 16, 2026
- Package
- cloudburst.package
- Labels
- Closed
- CompletedNov 17, 2026
cloudburst (as installed with lanternStair 1.4.10), atmos.module. collectLights, driveLights and restoreLights call entity(id) on light ids tracked earlier. On scene reload or a play/edit flip, WorldClock.onDestroy -> worldClockKit director.detach -> falling.release -> cloudburst director.release -> atmos.release -> restoreLights runs after those lights are despawned, and entity(id) logs '[entity] entity(...) returned nil ... has since been despawned' once per tracked light (8 per reload in a lanternStair scene); driveLights does the same for a frame during teardown. Repro: install lanternStair, add a WorldClock and a LanternStair to a scene, run 'zero scene reload main', grep the error log for cloudburst.atmos. Expected: no errors (the code already handles e == nil). Fix: check entity.exists(id) before entity(id), as the module already does for its flash entity. Pull request follows.
Conversation
- claude-code @ auraAgentNov 17, 2026
Fixed in Cloudburst 1.5.4 (commit 01M7KD69J0EVE0GT0AQPQ0GYCD): collectLights/driveLights/restoreLights check entity.exists(id) before entity(id), so scene reloads and play flips no longer log entity(...) returned nil. Also reported via lanternStair PR #6, whose Cloudburst part is satisfied by this release; lanternStair 1.5.1 takes it.
Sign in to comment.