Component groups

❗Warning: This is a legacy page covering functionality with the old SDK version 6. See the latest version of this topic here .

Each component group keeps track of a list of entities that have all the required components .

The engine automatically updates this list every time that:

• A new entity is added to the engine
• An entity is removed from the engine
• An entity in the engine adds a new component
• An entity in the engine removes a component

📔 Note: Only entities that are added to the engine are eligible for component groups. Entities that have been created but not added to the engine, or that have been removed from the engine, aren’t listed in any group.

After the group is created, you don’t need to add or remove entities manually from it, the engine takes care of that.

const myGroup = engine.getComponentGroup(Transform)

Systems typically iterate over the entities in these groups in their update method, performing the same operations on each. Having a predefined group of valid entities is a great way to save resources, specially for functions that run on every frame like update(). If on every frame your system would have to iterate over every single entity in the scene looking for the ones it needs, that would be very time consuming.

You can access the entities in a component group in the following way: if the group name is myGroup, calling myGroup.entities returns an array containing all the entities in it.

const myGroup = engine.getComponentGroup(Transform)

for (let entity of myGroup.entities) {
	log(entity.uuid)
}

📔 Note: Keep in mind that component groups take up space in the local memory of the player’s machine. Usually, the benefit in speed you get from having a group is a tradeoff that is well worth it. However, for cases where you’d have a large group that you don’t access all that often, it might be better to not have one.

Required components #

When creating a component group, specify what components need to be present in every entity that’s added to the group. You can list as many components as you want, the component group will only accept entities that have all of the listed components.

const myGroup = engine.getComponentGroup(Transform, Physics, NextPosition)

💡 Tip: If your scene includes entities that have all the required components but that don’t need to be in your component group, create a custom component to act as a flag . This component doesn’t need to have any properties in it. Add this component to the entities that you want the component group to handle.

Use component groups in a system #

const myGroup = engine.getComponentGroup(Transform, Physics)

export class PhysicsSystem implements ISystem {
	update() {
		for (let entity of myGroup.entities) {
			const position = entity.getComponent(Transform).Position
			const vel = entity.getComponent(Physics).velocity
			position.x += vel.x
			position.y += vel.y
			position.z += vel.z
		}
	}
}

In the example above, PhysicsSystem iterates over the entities in myGroup as part of the update() function, that is executed on every frame of the game loop.

• If the scene has several ball entities, each with a Position and a Physics component, then they will be included in myGroup. PhysicsSystem will then update their position on every frame.

• If your scene also has other entities like a hoop and a scoreBoard that only have a Physics component, then they won’t be in myGroup and won’t be affected by PhysicsSystem.

📔 Note: The engine.getComponentGroup() is an expensive function to process, it should never be used inside the update of a system, as that would create a new group on every frame. When regularly checking the entities in a group, refer to an already created group, as in the example above. Once created, component groups are updated as entities and components are added and removed from the engine, so there’s no need to redeclare or update these groups.

Dealing with the entities #

The entities array of a component group contains elements of type IEntity, which is identical to Entity, but not recogized by Typescript as the same type. If a function expects an input of type Entity, you can simply force the argument’s type with as Entity.

const myGroup = engine.getComponentGroup(Billboard)

for (let entity of myGroup.entities) {
	addLabel(entity as Entity)
}

function addLabel(entity: Entity) {
	let label = new Entity()
	label.setParent(entity)
	label.addComponent(
		new Transform({
			position: new Vector3(0, 1, 0),
			scale: new Vector3(0.5, 0.5, 0.5),
		})
	)
	label.addComponent(new TextShape(entity.uuid))
}

All entities #

You can access the full list of entities that have been added to the engine, regardless of what components they have, through engine.entities.

engine.entities

Change a component group while iterating #

Component groups are mutable. You shouldn’t modify the component group while you’re iterating over it, because that could have unwanted consequences.

For example, if you iterate over a component group to remove each entity from the engine, the act of removing an entity displaces the other entities in the array, which can lead to some entities being skipped.

To overcome this problem, use the following code to remove all entities from the engine:

while (myGroup.entities.length) {
	engine.removeEntity(myGroup.entities[0])
}