Issue, possible bug with TF2 matchmaking.

[kamanabc123]

I have had no issues with ArchiSteamFarm when I login to a game it recognizes my account is in use and waits till I'm inactive again. I love this feature, but I have an issue with TF2.

For some reason when I sign into TF2 for the first time it takes forever to connect to the game coordinator.

After it connects it is IMPOSSIBLE to queue. When you attempt to queue it acts normal and starts the queue but a few seconds to almost a minute later it will always cancel the queue. I have no idea why it does this but it's very frustrating.

This is what the console output looks like.

The only way to queue is to quickly restart TF2 before ArchiSteamFarm deems the account inactive again.
It just sucks that I have to either A open the game twice or B close ArchiSteamFarm before signing in.

I have looked at the config section but I didn't notice anything that I thought would help. Is there any way I can solve this by configuring it differently or is this just a bug? Thank you.

[JustArchi]

When you take over the session from ASF forcibly, steam client in ASF gets disconnected immediately, which ASF quickly answers with reconnection. It's possible that due to some bug, as TF2 is quite old game, Steam thinks due to some reason that the new client session is the one which should receive the packets, and therefore you get disconnected. Perhaps this is why re-launching TF2 helps, since then ASF is waiting for you and not getting disconnected, so when TF2 gets initialized, it's initialized in the right session right away, and there is no new session popping up in the meantime.

I don't have any solution for you, this isn't a problem with ASF. You can !stop or !pause the bot prior to launching a game, which will avoid the disconnection-reconnection loop, but this isn't much different from just closing the app prior to playing.