1 reply to this topic

[frosted]

SteamName: yaboycoll ringme

SteamID32: STEAM_0:0:48703130

Lobby Number: 151553

Date and Time: 8 July 2014, 2:00

 

Player appeared in enemy spawn as scout equipped with sticky launcher and minigun. Lobby was unplayable. Demo file was not recorded due to match starting before players could join. Screenshot attached.

 

SteamName: 'Streetm4N

SteamID32: STEAM_0:1:40620422

Lobby Number: 151553

Date and Time: 8 July 2014, 2:00

 

As lobby leader, kept BLU sniper slot reserved and empty for an extended period of time despite all other slots being filled. When the lobby started, did not properly load the config causing there to be no pregame and the match to start immediately. Most players did not connect to the server and as a result, lobby was unplayable. Demo file was not recorded due to match starting before players could join.

Attached Thumbnails

• 

[Luop90]

Reviewing...
 
Interesting, if hes still doing it, and he's not a lobby leader, it means he's using a hack/exploit.
 
STEAM_0:0:48703130- Banned from TF2Center
 
As for the other guy, its not his fault on the config error. TF2Center runs the config, and it wasn't correct, it means an error happened. I checked the logs, and he didn't execute any foreign config, which means a bug occurred, as you can see in the logs shown below.
 

[2014-07-08 07:06:35,851] Listening to port 5603
[2014-07-08 07:07:35,852] Socket timeout occurred

 
Essentially, TF2Center couldn't connect at first, and because of it, the config wasn't executed correctly.
 
STEAM_0:1:40620422- Not Banned