Crash when player connects to TF2 Dedicated Server Options

[SleepyAl]

Hi, I've used RCBot2 in the past with TF2 on my local machine, and I've just set up a dedicated server on a Windows 7 x64 machine so my friends and I can game together on it.

I've got it all installed correctly (to my knowledge) and running, and it's finding the waypoints correctly, but whenever a player joins the game while a bot is connected (or vice-versa), the server instantly crashes once the "[player name] has connected" line pops up in console.

I'm not sure how to run RCBot2 in a debug mode or if it makes any logs or not, but if there's a way I can post them if told how to do so.

I've tried running RCBot2 with and without Sourcemod/Metamod, and it crashes regardless. The server works fine without any RCBot2 bots.

My directory to the tf installation is as follows: C:\Program Files (x86)\Valve\HLServer\steamcmd_win32\orangebox\tf

RCBot2's folder is installed in C:\Users\Sleepy\rcbot2 and the waypoints are in waypoints\orangebox\tf

Any help would be appreciated.

[madmax2]

This may not be the whole problem, but the value for rcbot_runplayer_cmd_tf2 in the config.ini somehow got changed and is wrong now! It's showing 416 instead of 417. Change that & see if it helps. Also, toggle rcbot_runplayer_hookonce back to 0 to start with. If it still crashes, then try 1, others have said 0 is working best atm...

The bot_mods.ini looks right for what the console is reporting, so I think that is ok...

max

[SleepyAl]

This may not be the whole problem, but the value for rcbot_runplayer_cmd_tf2 in the config.ini somehow got changed and is wrong now! It's showing 416 instead of 417. Change that & see if it helps. Also, toggle rcbot_runplayer_hookonce back to 0 to start with. If it still crashes, then try 1, others have said 0 is working best atm...

The bot_mods.ini looks right for what the console is reporting, so I think that is ok...

max

I'm not sure how the runplayer_cmd_tf2 got changed, but putting it back to 417 didn't fix the problems. I also tried hookonce on both 0 and 1, no dice.

[Cheeseh]

I'm not sure how the runplayer_cmd_tf2 got changed, but putting it back to 417 didn't fix the problems. I also tried hookonce on both 0 and 1, no dice.

well I've downloaded steamCMD and tried it myself this morning and it's definitely crashing at the hooking stage. So there's got to be something wrong with the offset. Perhaps it's different for dedicated server. Could try 415 or even go lower. When I get home I'll have another look and see how sourcemod gets the offsets.

[Cheeseh]

well I've downloaded steamCMD and tried it myself this morning and it's definitely crashing at the hooking stage. So there's got to be something wrong with the offset. Perhaps it's different for dedicated server. Could try 415 or even go lower. When I get home I'll have another look and see how sourcemod gets the offsets.

okay I've found the problem. The RCBot2 config.ini doesn't load until you add a bot in dedicated server, unfortunately your rcbot_runplayer_cmd_tf2 value is in the config and it's too late to update.

So what you'll need to do for the time being is type, or automatically set "rcbot_runplayer_cmd_tf2" to "417" after you load the rcbot2 plugin but before you add any bots, in the console or by some automatic means

[madmax2]

okay I've found the problem. The RCBot2 config.ini doesn't load until you add a bot in dedicated server, unfortunately your rcbot_runplayer_cmd_tf2 value is in the config and it's too late to update.

So what you'll need to do for the time being is type, or automatically set "rcbot_runplayer_cmd_tf2" to "417" after you load the rcbot2 plugin but before you add any bots, in the console or by some automatic means

Yeah, I'm glad you found a solution... So was this problem only with TF2 dedicated servers? Because I thought some of the users on DODs (darkranger), currently had a working dedicated server... maybe he had placed the rcbot_runplayer_cmd_dod statement in one of the server config files?