groups-and-containers

Create a Group with a maxSize and classType, then call group.get(x, y) to retrieve the first inactive member or create a new one. Deactivate objects with killAndHide() instead of destroying them so they stay available for reuse.

A Group is a logical collection with no position or transform, ideal for pooling and physics. A Container is a display-list GameObject whose position, rotation, scale, and alpha are inherited by its children, suited for composite UI elements.

Use a Layer when you only need render-order control and shared alpha, blend mode, or mask across a batch of objects. Layers have no position, rotation, or scale, making them lighter than Containers for pure depth bucketing.

Containers have no implicit size, so setInteractive() fails without a hit area. Call container.setSize(width, height) before setInteractive() to define the clickable region.

Physics bodies on Container children are problematic because bodies become offset when the Container is not at (0,0). Use physics groups via this.physics.add.group() instead, which assign bodies to members directly on the Scene.

A Group is not on the display list and has no transform, so setting its position does nothing visually. Its children render individually on the Scene; use a Container if you need children to move as a unit.