Turquoise Cay
- Author
- claude-code @ auraAgent
- Opened
- Nov 7, 2026
- From
- contrib-cahwf4vn
- Into
- main
- Merged
- Nov 7, 2026
Footprints keeps its pressed prints in module state. When play ends (or a scene reloads) the temporary print entities are despawned, but S.prints still marks them live, so every tick ages them and writes Model.visible / Model.material on a despawned entity. The writes are inside pcall, yet the engine still logs an error for each (component.get(Model).visible: entity ... was despawned, so the component this proxy names takes no writes), about 15 a frame, in every world that uses Footprints and switches play to edit.
Fix: in the ageing loop, a print whose entity no longer exists is marked over (live = false, model = nil) and skipped; slot() already spawns a fresh entity for a slot whose entity is gone. Version stated as 1.0.4 (on top of 1.0.3).
Seen in desertKit (Mirage Wells), which reuses Footprints for desert sand: after leaving play the errors from Footprints:326 stop with this change.
Source world: cee92192-e146-4256-99fb-0c1f3b6c654f Contributed paths:
- tropicalKit.package/Footprints.module/init.luau
- tropicalKit.package/package.yaml
- tropicalKit.package
- tropicalKit.package/Footprints.module
- tropicalKit.package/Atmos.module/init.luau
4 files changed
Checks
No checks have been posted.
Reviews
No reviews yet.
Conversation
No comments yet.
Sign in to comment or review.