Waypoint Flags

Waypoint Flag List

To add or remove a flag you need to type this command 1st then the flag name as listed below.

/bot waypoint_addflag flagname

allies

• An ET alias for the team2 flag. Often used with team doors, or at spawn points.

axis

• An ET alias for the team1 flag. Often used with team doors, or at spawn points.

blockbridge

• Flags a path between two waypoints that leads over a destructible bridge or ramp.

blockwall

• Flags a path between two waypoints that is blocked by a wall or similar obstacle.

blockwater

• Flags the path between two waypoints as blockable by water. Example: the caves in Oasis.

climb

• Flag this waypoint as climb, for ladders or other climbable objects. The FollowPath low level goal calculates distance in 3D if the climb flag is set. Otherwise Z coordinate is ignored for navigation if the climb flag is not set.

closed

• Flag this waypoint as closed, and therefore unusable in path searches.

This flag is best added and removed from a script by function Wp.SetWaypointFlag

crouch

• Flag this waypoint as crouch, causing bots to crouch from previous waypoint towards this waypoint. Crouch ends when bot gets into waypoint radius.

disguise

• Flag this waypoint as disguise to be used only by disguised covertops. It's not recommended to use this flag at team doors because it requires two waypoints (one with disguise flag and another with axis/allies flag) . It's better to use the infiltrator flag at team doors.

door

• Flag this waypoint as door, causing the bot to repeatedly press USE button while going to this waypoint.

dynamic

• Flag this waypoint as dynamic, causing the bots to update their path if DynamicPathsUpdated() is called. Usually it's used in combination with the blockable flag to update constructible barrier paths.

elevator

• It does not work in current Omni-bot version.

infiltrator

• This flag is used together with axis or allies flag. Team is ignored if bot has INFILTRATOR role. Disguised covertops in ET or RTCW automatically get the role.

inwater

• Flag this waypoint as being in water. This should eventually be auto-detected on placement. Will eventually be used for smarter swimming logic. In the current Omni-bot version, bot repeatedly presses JUMP button.

jump

• Flag this waypoint as jump, causing the bot to jump once at the moment when the bot gets into the waypoint radius.

jumpgap

• Flag this waypoint as jumpgap, causing the bot to check the ground ahead and jump near before gaps in the ground.

jumplow

• Flag this waypoint as jumplow, causing the bot to check a short distance in front of the bot and jump over low obstacles such as small walls, crates, boxes...

prone

• Flag this waypoint as prone, causing the bot to go prone and crawl along the path from previous waypoint towards this waypoint. Prone ends when bot gets into waypoint radius. In 0.7 prone was also used in some circumstances as a stance to be in, such as with sniper points and such.

sneak

• Flag this waypoint as sneak, causing the bot to walk or sneak while moving from previous waypoint towards this waypoint. Walk ends when bot gets into waypoint radius.

sprint

• Flag this waypoint as sprint, causing the bot sprinting along the path towards this waypoint. The bot stops sprinting when he gets into waypoint radius.

strafe_l

• Flag this waypoint as strafe_l to hold STRAFE_L button while moving towards this waypoint. This flag is unreliable. You should use paththrough navigation instead.

strafe_r

• Flag this waypoint as strafe_r to hold STRAFE_R button while moving towards this waypoint. This flag is unreliable. You should use paththrough navigation instead.

team1

• Flag this waypoint as usable for team1 only.

team2

• Flag this waypoint as usable for team2 only.

teamonly

• Internal flag. Don't use this directly. Automatically set and un-set based on using other team flags.

teleport

• Flag this waypoint as a teleport. The paths between 2 teleport waypoints is considered 0 length since navigation is considered instant. Destination waypoint radius must be large enough so that bot is teleported to position within the radius.

underwater

• Flag this waypoint as being under water. This should eventually be auto-detected on placement. Will eventually be used for smarter swimming logic. Not used in the current Omni-bot version.

usepath

• Limit usage of a waypoint to specific high level goals. The waypoint must also have a property which name is lowercase ScriptGoal name and its value is true. Goal name depends on the Omni-bot version, see GetHighLevelGoalName.

/bot waypoint_addflag usepath
/bot waypoint_setproperty checkpoint true