OBSIDREL / DOCS

Documentation

Guides, tutorials and technical references for the Obsidrel ecosystem.

DocumentationEntity movement and controllers

Entity movement and controllers

The Core sample distinguishes the movement controller, its locomotion and its default mode.

ControllerExample uses
GROUNDWalking, hopping, crawling and slithering
AIRHovering, flapping, orbiting, diving and landing
WATERSwimming, 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

  1. Inspect movement.enabled.
  2. Confirm the controller matches the creature's environment.
  3. Verify navigation clearance, collision and target distance.
  4. Check that referenced animation names actually exist.
  5. 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.

Was this article helpful?Loading ratings…

Help us improve Obsidrel documentation. One vote per account and article. Discord AI feedback can also contribute when the answer cites this article.