Closed Jesseman1 closed 3 years ago
This just means you haven't added any launch options to TF2 yet. You can just add a launch option to TF2 using steam to fix this, or you can add "LaunchOptions" underneath "PlayTime" to fix it as well.
but I have added launch options to TF2, I use the ones Mastercoms says to use when running the Comfig
but I have added launch options to TF2, I use the ones Mastercoms says to use when running the Comfig
they aren't referring to those launch options, the launch options that are used for the program are what you are missing in order to have TF2BD work
the ones you have in steam are alright, they will be executed along with whatever you have put into LaunchOptions
Ok, so I put "launchOptions" below playtime, now the "launch options go here" bit, that goes beside just like "46" does above?
Yeah, it should look something like this:
"440"
{
"LastPlayed" "1624484106"
"Playtime" "46"
"LaunchOptions" "(Launch options here) "
}
Ok, so I tried putting the commands in this file as instructed and it did not work. However I then copied the commands and posted them into the actual launch options box through Steam and now the BD seems to be working.
Also if anyone knows how I can get Discord to let me verify this new account I would really appreciate it.
Ok still not completely fixed yet. I used these commands "-usercon +ip 0.0.0.0 +rcon_password [pass] +hostport [port]" Since Creyon said that was all that was needed. The BD is able to launch and read chat, but cannot see player names. What commands do I need to add to make this work correctly?
Try copying all of the launch commands that Koi posted and pasting them into notepad. Then add your rcon password and host port. Then copy them and paste them into the launch options fiend in steam.
I thought people were saying there are problems with the command list being too long. Do I need all of them or are there some that aren't necessary?
It should work fine if you paste them in instead of typing them.
Just tried it, didn't work
huh, ok this time it did.
Duplicate of #331
Describe the bug
To Reproduce
Expected behavior
Screenshots
Desktop
Additional context