A Master-Slave Behavior (beMasterSlave) binds a slave entity position and/or orientation to a master entity bone, with optional offsets. It must be placed on Slave EntityType, and reference its master. The master-slave binding is done on a one-to-one basis, for each entity of those types.
A beMasterSlave Behavior in the Behavior Editor
Note that this behavior depends on EntityType / Advanced Attributes / Master-Slave Level. In order to bind a slave entity to a master, one must ensure that the master is updated first. See EntityType
Note that Master-Slave relations can only be achieved into the same CrowdField and same Particle System. Binding EntityTypes of different CrowdFields or different Particle Systems will end up in a failure.
When using more slaves than masters, several slave entities will be bound to the same master (using a modulo rule).


  • Behavior Editor / Behavior Library: 
  • Golaem Menu: Crowd Behaviors / Behaviors / CrowdBeMasterSlave Node
  • MEL command: glmCrowdBeMasterSlaveCmd;


A MasterSlave Behavior defines the following specific attributes. For common attributes see Behavior Common Attributes.

Master / Slave Attributes

Master / Slave Attributes
In Master EntityType

Specify which EntityType will be used as master EntityType

Master Bone Name

The given name must be a valid bone name of the selected EntiyType (click helper to pick one)

Constraint Position

Specify if the slave entity position must be constrained to the master bone position.

Position Offset

When non null, this offset will be applied in master bone referential, in addition to the master bone position, before applying it to the slave.

Scale Position Offset

When using position offset, it may be suitable, or not, to scale it according to master scale.

Constraint Orientation

Specify if the slave entity orientation must be constrained to the master bone orientation.

Orientation Offset

Adds an offset to the master bone orientation, in master bone referential, before applying it to the slave.