List of additions for DOD:S Options

[Cheeseh]

red = released. blue = unreleased (in SVN), green = to do

dod:s : sprint/prone waypoints
dod:s snipers/defenders/gunners crouch/prone depending on waypoint type at defend/sniper/machine gun point

Revision 269
Modified Thu Jan 31 12:31:43 2013 UTC (2 days, 12 hours ago)

dods: bot choose to plant bombs in less dangerous capture points
dods: bots can plant bombs that block paths
dods: new waypoint 'bombtoopen'

all: added waypoint add <type> <area> e.g. rcbot waypoint add sniper 3 (adds sniper waypoint at area 3)
all: fixed bug - bots not listening to other players (improves combat)
all: mods: fixed divide by zero error with bot's movement

Revision 267
Modified Sun Jan 27 12:40:11 2013 UTC (6 days, 12 hours ago) by rcbotcheeseh

all: fixed random crash to do with weapons
all: fixed 'you do not have access to command' after map change
dod:s bot's step back from bombs before they explode better
dod:s fixed a class bug where bots just stood still and did nothing


Revision 264
Modified Thu Jan 24 11:09:37 2013 UTC (9 days, 14 hours ago) by rcbotcheeseh

dod:s ladder fix
tf2: fix bots not going to point to defend so much when under attack

Revision 263
Modified Thu Jan 24 08:48:40 2013 UTC (9 days, 16 hours ago) by rcbotcheeseh

messaround crash bug with voice commands

Revision 262
Modified Thu Jan 24 07:47:57 2013 UTC (9 days, 17 hours ago) by rcbotcheeseh

tf2: bots don't taunt when on fire or holding flag
tf2: demoman pipe bombing / pipe jumping
tf2: bots can say 'sentry ahead' and 'incoming'
tf2: some crash bugs
all: movement jerk bugs

[genmac]

awesome stuff as always Cheeseh keep up the good work.
The DODS community is forever thankful and all those high quality custom dods maps will get some more well deserve playing time and exposure.
Can't believe there's so much of those maps still being made inspite of the decreasing numbers of dods servers as years go by.

Can you also add some sort of GO TO THIS waypoint id where bots are forced to go to this waypoint just to check if all those intricate wpts will be use properly by the bots. Podbot-mm has that feature. I had to delete certain wpts and paths just to check if the wpts I made for the dod_kalt's ladders to tunnel and out wpts will be use smoothly by the bots since they seldomly use that path when all wpts are inplaced I had to spectate like forverver just to catch if a bot decided to use that path.

Also some sort of connecting paths using ids without the need of touching wpts like...create path from wpt id no.1 to wpt id no.2. This is very useful on connecting
very specific paths when wpts are too close to each other like those ladder/descending wpts I made on kalt's tunnel.

[Cheeseh]

Can you also add some sort of GO TO THIS waypoint id where bots are forced to go to this waypoint just to check if all those intricate wpts will be use properly by the bots. Podbot-mm has that feature. I had to delete certain wpts and paths just to check if the wpts I made for the dod_kalt's ladders to tunnel and out wpts will be use smoothly by the bots since they seldomly use that path when all wpts are inplaced I had to spectate like forverver just to catch if a bot decided to use that path.

Also some sort of connecting paths using ids without the need of touching wpts like...create path from wpt id no.1 to wpt id no.2. This is very useful on connecting very specific paths when wpts are too close to each other like those ladder/descending wpts I made on kalt's tunnel.

already done, use

rcbot debug bot <botname>

then goto a waypoint and type

rcbot debug bot_goto

the bot with <bot name> should try to go to the waypoint, if he doesn't you can use 'rcbot debug nav 1' and see what it's really doing

--------

as for the other suggestion, not sure what you mean exactly, I'd just switch "rcbot pathwaypoint disable" then add the waypoint, then use "create1" and "create2" without the fear of connecting unwanted waypoints, you can put rcbot pathwaypoint enable again