Joining a server from the Steam server browser doesn't work

[DylwinTFTW]

It just takes you to the title screen. Disabling QuickPrecache doesn't fix this. Using Windows.

[cueki]

I am not sure what you mean, joining a server comes after everything related to the preloader.

[Niterux]

This is because of w/config.cfg, this might be able to be worked around by having the preloader edit valve.rc to run stuffcmds later as the steam server browser uses launch arguments to do the connection. But this would likely require significant work in valve-parsers as it does not support .cfg. Many huds edit valve.rc so a static bundle is not possible here.

(stuffcmds is the command in valve.rc that runs all of the launch arguments with + before them when the game starts, putting it in w/config.cfg would cause an infinite loop.)

[Niterux]

I am not sure what you mean, joining a server comes after everything related to the preloader.

Actually starting TF2 by joining from the server browser appends the argument to the beginning of the arguments list.

[cueki]

I am not sure what you mean, joining a server comes after everything related to the preloader.

Actually starting TF2 by joining from the server browser appends the argument to the beginning of the arguments list.

Ah, I wasn't sure what they meant, yes you can do it via valve.rc, as I originally did, but it conflicted with too many custom HUDs.

[DylwinTFTW]

I am not sure what you mean, joining a server comes after everything related to the preloader.

Actually starting TF2 by joining from the server browser appends the argument to the beginning of the arguments list.

Ah, I wasn't sure what they meant, yes you can do it via valve.rc, as I originally did, but it conflicted with too many custom HUDs.

Perhaps it could be added as an option that warns of its pros and cons?

[Niterux]

It would be fine if valve.rc could be patched in a fashion similar to mainmenuoverride.res

[cueki]

It would be fine if valve.rc could be patched in a fashion similar to mainmenuoverride.res

We actually could, we can also technically set launch options for the user by modifying share/Steam/userdata/<steamid>/config/localconfig.vdf (to verify that they do not double exec w/config.cfg)

Food for thought, I am not super familiar with huds myself, so someone more experienced would be helpful.

[djsigmann]

We actually could, we can also technically set launch options for the user by modifying share/Steam/userdata/<steamid>/config/localconfig.vdf (to verify that they do not double exec w/config.cfg)

This could be useful, but I wonder if perhaps only checking if the launch options correctly contain +exec w/config.cfg, and not setting anything might be less error prone.

[cueki]

We actually could, we can also technically set launch options for the user by modifying share/Steam/userdata/<steamid>/config/localconfig.vdf (to verify that they do not double exec w/config.cfg)

This could be useful, but I wonder if perhaps only checking if the launch options correctly contain +exec w/config.cfg, and not setting anything might be less error prone.

I more-so do not wish to modify something that the user may come across manually, which might then confuse them why it is there. I agree it is probably most useful as a check.