[BUG] Program is unable to find important command-line parameters

[UAVXP]

Describe the bug After the latest TF2 update, which has been released on 22'nd of June, 2021, TF2 Bot Detector cannot properly connect with the game

To Reproduce

1. Update TF2 after 22'nd of June, 2021
2. Run Bot Detector
3. Press "Launch TF2"
4. See error

Expected behavior Runned TF2

Logs No significant log errors found

Screenshots

Desktop

• OS: Windows 7
• TF2 Bot Detector v1.2.0.798

Additional context Before the latest TF2 update everything was working fine

[jmke79]

able to replicate on Windows 10 also; exact same issue

[Spygineer2]

I am having the same issue

[Susorodni]

With the recent update, also having the same issue

[Koi-TF2]

This BD issue is caused by the RCE exploit fix previously implemented in CS:GO being brought over to TF2. In doing so, the steam://run argument functionality has changed due to API changes.

Temporary fix:

• Shut down steam entirely
• Locate the steam file "localconfig.vdf" found in C:\Program Files (x86)\Steam\userdata\[your steam ID3]\config
• Find the section of the file with: "Software" { "valve" { "Steam" { "apps" { "440" { "LaunchOptions" "launch options go here"
• Inside the "LaunchOptions" section for app 440 (TF2), set your normal adv launch options and then also add on the following WITH A UNIQUE PASSWORD AND PORT. The rcon password is typically 16 characters long and the port is typically between the number 40000 and 60000. Anything in these ranges will do: -usercon -high +developer 1 +alias developer +contimes 0 +alias contimes +ip 0.0.0.0 +alias ip +sv_rcon_whitelist_address 127.0.0.1 +alias sv_rcon_whitelist_address +sv_quota_stringcmdspersecond 1000000 +alias sv_quota_stringcmdspersecond +rcon_password SETYOURPASSWORD +alias rcon_password +hostport PORTHERE +alias hostport +alias cl_reload_localization_files +net_start +con_timestamp 1 +alias con_timestamp -condebug -conclearlog
• Save the file, then load steam up again
• Note: To remove/reset your launch options back to what they used to be, just do the previous steps but remove all the extra TF2BD arguments (Make sure steam is shut down entirely before making changes)

Now you can launch TF2BD normally using its Launch TF2 button since it will be able to find the arguments it needs to run.

[PazerOP]

I've been very busy lately, which is why there hasn't been any activity lately. I'll try to implement a fix this evening.

Regarding the workaround above, you shouldn't need to close steam and edit the config. I think you can just modify command line options via the steam GUI by right clicking on tf2 and hitting settings or properties or whatever.

[Koi-TF2]

Regarding the workaround above, you shouldn't need to close steam and edit the config. I think you can just modify command line options via the steam GUI by right clicking on tf2 and hitting settings or properties or whatever.

Pazer, I do not recommend doing this because the launch options are too long. There is a visual bug within the steam interface which cuts the launch options short. Technically they are still present and will still work, but they are not visible or modifiable beyond a certain point, so do this at your own risk. It likely won't cause any serious issue but just know that it's a problem

[KaineWooten]

Wouldn't a work around be to create a batch file with the said command line paramaters to open the application. You'd just need to similarly set the launch options to be similar to what was presented already but with the batch file.

[Jesseman1]

crap, I just realized I probably should have just commented here instead of posting a whole new issue about it. But yeah, I don't know if I can follow Koi's guide cuz those fields are not in my file...

[Koi-TF2]

those fields are not in my file...

Assuming you are in the right file (localconfig.vdf), then the reason your 440 doesn't have a "LaunchOptions" field is because you have never set advanced launch options ever before. Either you can manually add the field yourself, or the easier method would just be to add one adv launch option via the built in menu in steam. Doing so should cause the field to be generated. I hope this helps

[Jesseman1]

Assuming you are in the right file (localconfig.vdf), then the reason your 440 doesn't have a "LaunchOptions" field is because you have never set advanced launch options ever before. Either you can manually add the field yourself, or the easier method would just be to add one adv launch option via the built in menu in steam. Doing so should cause the field to be generated. I hope this helps

I have advanced launch options already in place from using mastercoms' comfig. So I don't know why the field is not already there, unless there is some other launch options box that I don't know about.

[Koi-TF2]

I have advanced launch options already in place from using mastercoms' comfig. So I don't know why the field is not already there, unless there is some other launch options box that I don't know about.

Advanced launch options are normally placed in the following location: In steam, right click on TF2 in your library, then click on properties. In the General tab, there will be a section labeled "Launch Options". The reason I do not advise just copy+pasting the full string of TF2BD's launch options into that location is what I described above:

Pazer, I do not recommend doing this because the launch options are too long. There is a visual bug within the steam interface which cuts the launch options short. Technically they are still present and will still work, but they are not visible or modifiable beyond a certain point, so do this at your own risk. It likely won't cause any serious issue but just know that it's a problem

[Jesseman1]

yes, I already have some inputs there for the comfig

[Koi-TF2]

yes, I already have some inputs there for the comfig

If this is the case, and you are sure you still don't have any LaunchOptions field inside the localconfig.vdf file for TF2, then I am not sure. Perhaps this is caused by steam cloud sync not syncing it correctly? You can either manually add the field to the file as mentioned before, or alternatively you can try the other method by copy+pasting the full args directly into the launch options area inside the steam interface. Just be aware that they will NOT all show up in the steam interface - some will be invisible because the arguments are too long. Still worth a try though