ECS World Management

What problem does it solve?

This Skill solves the problem of managing an ECS world safely in a fixed-timestep game loop by preventing invalid structural changes during iteration and reducing thread-safety risks across simulation, background reads, and persistence.

Core Features & Use Cases

• Thread-safe world wrapper: Wraps Arch.Core.World with read/write locking so entity creation, destruction, and queries can be coordinated safely.
• Deferred structural changes: Uses a command buffer to record adds, removes, spawns, and destroys during system execution and apply them later in a deterministic cleanup phase.
• Background-readable snapshots: Captures immutable component snapshots so worker threads can inspect ECS state without blocking the main simulation tick.
• World lifecycle coordination: Organizes world creation, scheduler registration, tick execution, and disposal through a WorldManager pattern.
• Stable entity identity: Introduces stable IDs and lookup maps for save/load flows, entity persistence, and cross-system references.
• Use case: A Godot 4.x action game can keep physics, AI, and spawning deterministic while UI, serialization, and async jobs read safe snapshots without corrupting ECS iteration.

Quick Start

Use the ECS World Management skill to design a thread-safe world wrapper with deferred commands, stable IDs, and snapshot-based background access for my Godot ECS project.