AlliedModders - making waypoints for podbot mm ( tutorial )

this thread is dedicated to podbot_mm waypoints (for .pwf and not for .nav files). it's useful to regroup the maximum of them in only one thread.

go to the top of thread
Content:

Important.
Requirements.
Installation.
Tutorials.
Making - Testing - Finalising.
Bugged waypoints.
FAQs Frequently Asked Questions.
credits.

Useful links.

go to the top of thread
Important:

there is already a thread about the podbot_mm installation. please check it before to make any irrelevant post.
this thread is made to show people how to make their own waypoints, or to check for some unresolved errors.
post your request only at last resort.
if you have some packs of waypoints, then you're welcome.
only new waypoints are accepted to be added to the global list.
if you edited an existing waypoint file, please specify why did you edit it (what was the flaw).

go to the top of thread
Requirements:

steam listen server (local game).
podbot_mm must be already installed (go to their official forum of look above).

go to the top of thread
Installation:

go here.

go to the top of thread
Tutorials:

before anything, you must read and to understand these three topics:

Waypoints - Basic.

to understand what's a waypoint file, how it works and how many type of way-points you need to use.

Waypoints - Common Errors

some common errors that you need to avoid, to make your waypoint file working finelly.

Waypoints - Useful keys binding

it's not important to make all and/or the exact same binds. just understand and choose your own easy binds.
in my case I use those binds which are sufficient for me:

Code:

bind "p" "amxmodmenu"

bind "[" "pb menu"

bind "]" "pb wpmenu"



bind "F1" "pb wpmenu;menuselect 1"

bind "F2" "pb wpmenu;menuselect 2;menuselect 1"

bind "F3" "pb wpmenu;menuselect 5"

bind "F4" "pb wpmenu;menuselect 6;menuselect 1"

bind "F5" "pb wpmenu;menuselect 4"

important: when you make binds, look at your keyboard as an US one even if not (mine is AZERTY but the binds are made as QWERTY)

go to the top of thread
Making - Testing - Finalising:

of course, to make waypoints will not be manually, one by one:

All You need is to start the listenserver on Your local PC, have administration rights to podbot mm menu, then invoke the command from the console: pb wpmenu

open your waypoint menu. go to options and enable the WP on/off and the autoWP on/off.
browse your map and look at your strewn waypoints.
after that you need to add manually other kind of waypoints, like goals, camp, etc.
the most important are the errors, if not solved the file will not work correctly.
try to make all the waypoints of the map sticked to each other by making a web. otherwise your wp file will not be saved correctly.
if the file is saved dosen't mean that's a good work, it only means that there are no errors. you should make good waypoint files, not only working ones !

little video added, sorry for the bad quality (the made file is in the attachement).
read the tutorials above to understand the video, I only made it to show the basic ways and the different waypoint colors, and their locations !

Code:

video detailed analysis for cs_assault_mini.



00:24 waypoints set to on.

00:40 auto-waypointing is enabled.

00:42 browsing the map to scatter waypoints.

00:56 making a waypoint manually.

01:12 deleting a waypoint.

01:19 first specific waypoint (goal).

01:46 first error displayed (will be fixed at the end).

01:46 church tower's sound at 5:00 PM.

03:35 making two waypoints at the end of area, to avoid it being isolated.

04:00 first ladder waypoint (first part).

04:08 first ladder waypoint (second part).

04:10 checking and making connection between the two parts.

04:28 first camping wayoint (start).

04:32 first camping wayoint (end).

04:36 (remark) the camping waypoint was made while ducking, that's why it has a small size.

06:27 the connection between the two ladders points was made automatically.

06:31 looking at it.

06:44 making a jump waypoint.

06:48 checking it.

07:00 making an outgoing connection, to avoid that aread being isolated.

07:31 first rescue waypoint.

08:11 "terrorist important" point.

08:28 "counter-terrorist important" point.

08:39 checking for errors.

08:41 a totally isolated waypoint.

08:54 one side isolated waypoint.

09:00 checking for errors, none.

09:05 saving waypoint file.

09:10 Go go go !

go to the top of thread
Bugged waypoints:

remark:

this section isn't for beginners, you need to have a little skill to understand it.
all the bugged waypoints used in those examples, can be found in the main archive folder, the edited ones in the edited folder. see the dropbox archive.

firstly, we should make difference between bugged and wrongly/badly made waypoint file:

a file having errors somewhere: isolated areas, some specific waypoints missed, etc. will not save correctly, even if it's nicely made.
a file saved without any error dosen't mean that's a nice one. it may be crapy but working "without errors".

wrong waypoints:

download de_santorini and try its waypoint file. you will not have any kind of error, and the game is running correctly. so go to spectate and watch if the bots can plant the bomb (or not). obviously, they will not !!
these screenshots will show that the person who made it had simply exchanged the terrorist important and the goal waypoints.

wrong waypoint: screenshot #1, screenshot #2 , screenshot #3
correct waypoint: ____________ screenshot #1, screenshot #2

the result ? the bot (a mindless sofware) will go to the goal waypoint location but isn't able not plant, as the map is only allowing it in bomb areas (remark the red bomb icon).

empty areas:

empty areas will not be browsed by bots, but may make them totally blind if they unfortunately go inside them, by seeing an ennemy for example. (read bots-united tutorials above).

empty areas: screenshot #1, screenshot #2, screenshot #3
full areas: __ screenshot #1, screenshot #2, screenshot #3

other examples of bad waypoints:

cs_assault_crayola.

in this location, the bot can't go outside the vent, because he/she must stand up before to do it, wich is impossible.
the solution !

cs_assault_mini:

bots will stuck in some areas because of bad waypoints.

normal waypoints floating in the air. bots always act oddly in this location. notice the colors, there is no jump waypoint here.
same location with another waypoint file. notice the different colors.
other locations where bots are sticking strangely. #1 and #2, better ways #1 and #2
some camping points are just looking at: the sky, the door, the wall or at the ground. some correct ones: #1, #2.

cs_assault_december:

there is a door in the hostages room that can only be opened by its related button (both of czero bots or podbot will try to go through it unsuccessfully).
the original waypoint file was made for me by a user here, (can't find the original post).

the door as seen in the map.
the waypoint near to the button, isn't a specific one (bots will not activate it).
near the door. the yellow beam is a bidirectional link, the white is an outgoing one. bots may try to go through the door.
specific waypoint, notice the two (green) outcoming and (white) outgoing beams. another view.
notice the one-way direction ! no bot will go towards the door without pressing the button. if the bot press the button, he/she has no other way than to go out !

go to the top of thread
FAQs (Frequently Asked Qestions):

Q. will this tutorial be useful for bots of condition zero ?
A. no ! it's a totally different software using another kind of wayoints: .nav files.
_____
Q. where to put new waypoints ?
A. ***\cstrike\addons\podbot\wptdefault. or ***\czero\addons\podbot\wptdefault.
_____
Q. I got three kind of files which one is the real waypoint ?
A. The main waypoint file is the one having a *.pwf extention. The *.pvi file is the visibility table (what waypoint is visible from another one, will be generated everytime a waypoint is edited). The *.pxp file saves the experience data (when the bot got hurt/killed in some position near the closest waypoint) "KWo".
_____
Q. should I use all the flag waypoints in all maps ?
A. not really.

goal flags must be assigned in their correct location or just somewhere in maps without goals (fy_, zm_, zp, ka_, he_, etc.).
team specific flags must be assigned somewhere, at least one for each team.
some of them are really specific, like the ladder one. others should be added in some kind of maps (camp, no hostage, etc.) for a better gameplay.

_____
Q. where to find waypoint files for a specific map
A. search in the web, in correct websites like 17buddies or Gamebanana. or read this.
_____
Q. I have the right waypoint file, but the bots are acting oddly.
A. it depends:

map and waypoint file have the same name, but aren't compatible.
waypoint file isn't nicely made.

_____
Q. bots work fine but are sticking in some parts of a map and don't want to move.
A.

make sure that you are using the latest podbot (beta) version.
waypoint file has some flaws (open the waypoints editor to see). bots can't understand or improvise, they just read and follow the web of waypoints.

_____
Q. I want to learn how to make waypoints.
A. up

go to the top of thread
Credits:

KWo: the podbot_mm master !

http://www.anglaisfacile.com/cgi2/my...ages/21276.jpg

go to the top of thread