About Waypoint Flags
Waypoint flags are not just labels — they actively alter path cost calculations, bot eligibility, and movement behavior. A flag on a waypoint can make bots avoid it, restrict which bots can use it, or change how they traverse it.
Flag Reference
| Flag | Effect on Pathfinding | Notes |
|---|---|---|
WAYPOINT_AVOID | Treated as near-forbidden — extremely high path cost | Bots will strongly prefer any other route |
WAYPOINT_SPECIFICGRAVITY | Blocks use if bot gravity is below the waypoint requirement | Set via rbot wp setgravity; auto-enabled by that command |
WAYPOINT_ZOMBIEONLY | Hard filter — only zombie bots can use this path | |
WAYPOINT_HUMANONLY | Hard filter — only human-role bots can use this path | |
WAYPOINT_ONLYONE | Blocks selection when a same-team bot already occupies the nearby radius | Prevents bot crowding at one spot |
WAYPOINT_DJUMP | Double-jump assistance; blocked for non-eligible movement contexts | |
WAYPOINT_ZOMBIEPUSH | Marks this as a zombie push behavior path node | |
WAYPOINT_FALLRISK | Signals a fall risk — affects movement style | |
WAYPOINT_WAITUNTIL | Bot will wait before proceeding through this node | |
WAYPOINT_CROUCH | Bot will crouch while using this waypoint | |
WAYPOINT_LADDER | Marks ladder traversal — special movement handling | |
WAYPOINT_HMCAMPMESH | Human mesh/camp grouping using mesh id from campStartX | Used with rbot wp setmesh |
WAYPOINT_ZMHMCAMP | Zombie-human camp grouping; uses visual link overlays | Used with rbot wp setmesh |
WAYPOINT_SPECIFICGRAVITY path validityWhen this flag is set, path validity depends on the individual bot's current gravity value. A bot with lower gravity than the waypoint requirement cannot use that path — effectively blocking that route for them.
Mesh flags use campStartX
WAYPOINT_HMCAMPMESH and WAYPOINT_ZMHMCAMP both rely on the mesh id stored in the waypoint's campStartX field. Set this with rbot wp setmesh <id>.