TF2C Profile: Nobel H
Region: AU
Browser: Google Chrome
Critical plugins: --
OS: --
Connection type: --
Bug type: In-game
Lobby ID: #740171
Date & Time: Lobby launched at "22:16:37" by TF2C's clock. Started typing this up at 22:44 12 August 2016. Same evening. The lobby played at some point in between.
This is a follow up of this.
https://forums.tf2ce...rtress-servers/
When a HL lobby (and specifically HL, 6s whitelists work fine) is created with an ozfortress server (specifically ozfortress, au.serveme.tf servers do not exhibit this issue), there is no whitelist.
To reiterate, ozfortress servers DO have UGC HL S19 configs and whitelist.
https://github.com/o.../server-configs
They work completely fine when manually executed. I have used them for UGC matches. They work without any issues.
The server used was ozfortress 1.
According to this, booked under "boo".
http://livelogs.ozfo....com/view/72784
http://logs.tf/1492220
Looking at this, ace of BLU team used the Sandman. This weapon is not allowed under the UGC HL S19 whitelist.
If the STVs may be found, it will show I (BLU medic) was using the Vita-Saw the entire game. This weapon is not allowed in any gamemode in any league in any part of the world.
This issue has been around for a few months now and has gone unnoticed because of the lax HL whitelist.
This issue can easily be replicated by creating a UGC HL lobby with an ozfortress server and testing the whitelist against this.
http://whitelist.tf/ugc_9v9_s19
Might I suggest obla to be the assigned staff member to this. AFAIK he is the only person who is a staff member of ozfortress AND TF2C and is therefore in an ideal position to diagnose and resolve this issue once and for all.
The booked name, livelogs, logs.tf, lobby number, and rough time and date have all been provided.
Edited by Nobel H, 12 August 2016 - 01:09 PM.