Entity movement and controllers
The Core sample distinguishes the movement controller, its locomotion and its default mode.
| Controller | Example uses |
|---|---|
GROUND | Walking, hopping, crawling and slithering |
AIR | Hovering, flapping, orbiting, diving and landing |
WATER | Swimming, floating, surfacing and diving |
For example, movement.controller: GROUND and movement.locomotion: WALK describe physical motion; animation names are separately referenced under movement.animation.
When movement fails
- Inspect
movement.enabled. - Confirm the controller matches the creature's environment.
- Verify navigation clearance, collision and target distance.
- Check that referenced animation names actually exist.
- Change one setting at a time in a controlled test area.
For detailed parameters, use resources/entities/example.yml from your installed Core. Advanced rigs and importer outputs may need different configuration.
Safe creation, editing and validation
Start with a working spawned entity. Set the movement controller to match the terrain, test navigation clearance, then add mode changes and animations. Distinguish movement modes from animation clip names.
Keep a copy of the original file. Make small changes, verify the YAML and test in the appropriate runtime. Studio preview does not replace the real server validation.
Related reference: Methods and features.