HPB_bot2_i486.so, HPBot2 ver 0.5 release 106 Options

[bir3yk]

I compiled a linux RCBot2 0.5

1. Folder Structure :
.../hl2
.../orangebox <-- srcds_run is here (for TF2 and Orange-Box games)
.../orangebox/bin <-- HPB_bot2_i486.so files copied here
.../rcbot2/
.../rcbot2/config/
.../rcbot2/profiles/
.../rcbot2/waypoints/
.../rcbot2/waypoints/orangebox/tf/ <-- waypoint and scripts files copied here
.../steam
2. Edit .../rcbot2/config/bot_mods.ini
mod = TF2
steamdir = orangebox
gamedir = tf
bot = TF2
3. Add
./srcds_run ..............+plugin_load ../bin/HPB_bot2


146 SVN revisions 119 SVN revisions
RCbot2 0.52
121 SVN revisions 121 SVN revisions
RCbot2 0.53
122 SVN revisions 122 SVN revisions

124 SVN revisions 124 SVN revisions

126 SVN revisions 126 SVN revisions

146 SVN revisions 146 SVN revisions

[madmax2]

Welcome to the Rcbot2 forums...

I'm not a linux guy so can't be much help there, but your folders look correct to me. The bots appear to be loading correctly, but there may still be a bug in the linux build, with bot names & profiles. See the last few posts in this topic about that...

http://rcbot.bots-united.com/forums/index.php?showtopic=1862

I believe the linux build is either .76 or .79, so you still need sv_cheats 1. It sounds like bots are working on most maps, but won't move on just a few maps?

I assume you have already tried replacing the waypoints on the effected maps. You could try deleteing the temporary files in the waypoints folder and let them regenerate (rcv, rcd, rcb) on those maps. If that doesn't help, you could try loading the waypoint manually, then add the bots, such as:

rcbot waypoint load dod_avalanche (rcbotd on dedi)

I have noticed when loading a waypoint manually after bots join, they may not recognize the capture areas, but a map restart will fix that.

It looks like you renamed the waypoints folder properly, and bots are working on many maps, so it must be related to the specific wpts it would seem, wierd file corruption maybe, very odd??? With rcbot1, sometimes the temp files need to be refreshed to correct odd behavior, so maybe thats the case here too?