party-ai

To synchronize a 2-member AI party state machine in Godot, implement a three-mood system using FOLLOW, ENGAGE, and RETURN states with hysteresis thresholds to manage companion movement and combat behavior naturally. It prevents follower desync and stuck AI.

Follower AI desync and stuck behavior during scene transitions occur when scene-persistent character data and spawn contracts are not properly managed by a Party autoload to enforce node group requirements and movement speed constraints across scene changes.

Manage persistent character data during leader swaps by utilizing a Party autoload contract that handles spawn logic, ensuring character data persists correctly across scene changes and maintains synchronized AI brain state for both party members.

The best way to handle companion combat engagement and movement speed constraints in GDScript is to use tuned hysteresis thresholds within an AI mood machine, ensuring leash teleport logic matches current movement speeds to prevent desync.

Yes, the Godot party system AI brain supports custom mood thresholds for action-RPG combat, allowing you to validate and tune hysteresis thresholds for FOLLOW, ENGAGE, and RETURN states to match specific game triggers and movement speeds.