groups-and-containers

Organize Phaser 4 game objects using Groups for non-visual collections and object pooling, Containers for nested transforms and UI composition, and Layers to control rendering order. This structure enables modular, scalable scene building without manually managing individual object positions.

Groups handle logical collections and object pooling without visual properties. Containers provide parent-child nested transforms for UI composition. Layers manage render order and apply shared visual effects. Each serves a distinct role in structuring enemies, UI elements, and dynamic scenes.

Set up object pooling in Phaser 4 by creating a Group, adding inactive objects, and retrieving them with getFirstDead. This pattern reuses pooled game objects instead of instantiating new ones, optimizing memory and performance for dynamic scenes.

Use a Container in Phaser 4 when you need visual parent-child relationships with inherited, nested transforms for positioning UI elements. Use a Group for non-visual logical collections and pooling where inherited transforms are not required.

Applying setExclusive when adding objects to a Container in Phaser 4 ensures correct lifecycles and rendering. It restricts objects to a single container, preventing overlapping display list registrations that cause visual glitches and unpredictable transform behavior.

Control render order in Phaser 4 by placing game objects into a Layer using the add.layer API. Layers group objects specifically for draw order management and applying shared effects, separating visual rendering from logical grouping and transforms.