The cause of the bug that has existed in 'Counter-Strike' for more than 10 years is finally revealed

Numerous reports have been made by players of the FPS game 'Counter-Strike' developed by Valve, including the remake 'Counter-Strike: Global Offensive (CS: GO)' and its updated version 'Counter-Strike 2 (CS2)'. There is a special bug that was also seen in ``. A software engineer involved in the community management of the Counter-Strike series has explained the bug, saying that he has found a fundamental solution to this bug that has been bothering players for many years.

A decade long Steam issue, is everyone just too fast for Valve? | freudenjmp

According to software engineer Freudensprung, if you start up and play the Counter-Strike series under certain circumstances, you will encounter a ``No user logon'' error that will disconnect you from the game.

This bug has been reported by people all over the world since around 2008, and developer Valve never fixed it. There are a lot of articles on the internet with titles like '5 ways to fix No user logon disconnection error', and they mention things like reinstalling the game and verifying files, but these don't fix the bug at its root. Freudensprung points out that it is not a solution, but only a temporary improvement.

The solution to this is surprisingly simple: ``Wait 10 seconds at the main menu after starting the game.''

According to Mr. Freudensprung, many similar bugs have been reported in the community 'Esportal' that he is involved in, and even though he has investigated it more than 100 times, it was a problem that he could not identify the cause of. I've been plagued by bugs, including one that often occurs two to three minutes after a player connects to the game, and one that a coworker said one day: ``There's a delay of several minutes before your skin appears.'' Mr. Freudensprung formulated a hypothesis based on the words 'I will.'

The hypothesis was that ``Valve may be verifying user IDs to see if there is any unauthorized display of skins in the game.'' When we actually checked the game server logs, we found that the user ID was being verified approximately 1 minute and 20 seconds after connection.

Furthermore, when we examined the CS:GO source code that was previously leaked , it became clear that a server called 'Steam3' may be authenticating users. This server was separate from the matchmaking server, and was thought to exist solely for authentication purposes.

Digging deeper into the problem, we found that Steam3 does a process that ``if CS2.exe connects to Steam3 via Steam.exe running on the same machine, it will correctly authenticate the user.'' Turns out. Therefore, if you connect to a game from a browser outside of the game, connect to a friend's match outside of the game from your Steam friends list, or use the Steam browser protocol (steam://connect/127.0.0.1 :27015) to manually connect to the server, there is a high probability that a bug will occur.

Freudensprung said: 'While we are confident that the solution of waiting 10 seconds will work for 99% of users, there are a small number of users who are affected by this error for other reasons not covered in this blog post. We are fully aware of this, and we hope that you will never see a Slack message reporting this error again.'