Stachekip

Gore-Spattered Heavy
Contributor
Edit: Whitelist needs testing. If anyone can quickly test this on a server and let me know if it works, please do so.

I don't disapprove of sv_pure 1 because it stops people from using undetected wallhacks and replacing the Spy decloak sound. The problem with it is that no one makes a proper whitelist for their servers, meaning people can't even use skins that don't give an advantage over others(such as viewmodels, certain player models, and the health meter).

I think the servers should have a whitelist that allows all skins EXCEPT ones that can produce wallhacks and replace the Spy decloak sound.

This is the whitelist:

Code:
Whitelist
{
Whitelist
{
    //
    // 3 modifiers are allowed on file specifications:
    //
    //    from_steam        - only check the Steam cache for the
 
file (ignore anything on disk)
    //    allow_from_disk        - allow the file to come from disk
    //    check_crc        - used with allow_from_disk - server does
 
CRC checks on the client's file to make sure it matches
    //
    //    The default modifier on all files is allow_from_disk.
 
Thus, all files can come from disk and don't need CRC checks unless
    //    allow_from_disk can be set at the same time as check_crc.
 
Use the + character in between them to signify this:
 
allow_from_disk+check_crc.
 
 
    //
    // Three types of file specifications:
    //
    //    1. directory\*.*    - refers to all files under the
 
directory
    //    2. directory\...    - refers to all files under the
 
directory and all directories under that (recursively)
    //    3. directory\filename    - refers to a single file
 
 
    //
    // By default, when in pure server mode, most content file types
 
are only allowed to come from Steam.
    //
    materials\...            from_steam
    models\...            allow_from_disk
    sound\...            allow_from_disk
 
 
    //
    // Allow custom player models. Don't do CRC checks on them
 
because the clients may all
    // have different custom models and the server won't have them
 
all.
    //
    models\player\...        allow_from_disk
    materials\models\player\...    allow_from_disk
 
 
    //
    // Allow custom spray decals.
    //
    materials\temp\...        allow_from_disk
    materials\vgui\logos\...    allow_from_disk
    materials\vgui\logos\ui\...    allow_from_disk
 
 
    //
    //Unblocked content:
    //
    materials\models\buildables\... allow_from disk
    materials\models\player\...    allow_from_disk
    materials\models\weapons\...    allow_from_disk
    materials\models\items\...      allow_from_disk
    materials\models\flag\...      allow_from_disk
    materials\console\...          allow_from_disk
    materials\particle\...          allow_from_disk
    materials\Particles\...        allow_from_disk
    materials\sprites\...          allow_from_disk
    materials\props\...          allow_from_disk
    materials\Effects\...          allow_from_disk
    materials\signs\...            allow_from_disk
    materials\HUD\...              allow_from_disk
    materials\Tile\...              allow_from_disk
 
    //
    //Blocked Content:
    //
    sound\player\footsteps\...                    from_steam
    sound\player\spy_uncloak.wav              from_steam
    sound\player\spy_cloak.wav                from_steam
    sound\player\spy_disguise.wav            from_steam
    sound\player\spy_uncloak_feigndeath.wav    from_steam
    materials\Effects\sniperdot.vtf            from_steam
    materials\Effects\sniperdot_blue.vtf      from_steam
    materials\Effects\sniperdot_red.vtf      from_steam
    materials\HUD\scope_sniper_ul.vtf          from_steam
    materials\HUD\scope_sniper_ul_dx80.vtf      from_steam
    materials\water\...                      from steam
    materials\wood\...                        from_steam
    materials\concrete\...                    from_steam
    materials\metal\...                      from_steam
    materials\nature\...                    from_steam
 
}
 

Bottiger

Administrator
You can suggest a whitelist and have people verify that it won't allow cheating.

This is what we are using right now.

Code:
whitelist
{
        //
        // 3 modifiers are allowed on file specifications:
        //
        //      from_steam                      - only check the Steam cache for the file (ignore anything on disk)
        //      allow_from_disk         - allow the file to come from disk
        //      check_crc                       - used with allow_from_disk - server does CRC checks on the client's file to make sure it matches
        //
        //      The default modifier on all files is allow_from_disk. Thus, all files can come from disk and don't need CRC checks unless
        //      allow_from_disk can be set at the same time as check_crc. Use the + character in between them to signify this: allow_from_disk+check_crc.


        //
        // Three types of file specifications:
        //
        //      1. directory\*.*                        - refers to all files under the directory
        //      2. directory\...                        - refers to all files under the directory and all directories under that (recursively)
        //      3. directory\filename           - refers to a single file


        //
        // By default, when in pure server mode, most content file types are only allowed to come from Steam.
        //
        materials\...           from_steam
        models\...                      from_steam
        sound\...                       from_steam


        //
        // Allow custom player models. Don't do CRC checks on them because the clients may all
        // have different custom models and the server won't have them all.
        //
        models\player\...                       allow_from_disk
        materials\models\player\...     allow_from_disk

        //
        // Allow custom spray decals.
        //
        materials\temp\...                      allow_from_disk
        materials\vgui\logos\...        allow_from_disk
        materials\vgui\logos\ui\...     allow_from_disk

        //
        // Allow replay browser thumbnails.
        //
        materials\vgui\replay\thumbnails\...   allow_from_disk
        //
        // (Uncomment and edit these for mods).
        // Allow mod resources to come from disk.
        //
        // materials\mymod\...          allow_from_disk+check_crc
        // models\mymod\...                     allow_from_disk+check_crc
        // sound\mymod\...                      allow_from_disk+check_crc

        // custom whitelist
        materials\models\weapons\...            allow_from_disk
        models\weapons\...                      allow_from_disk
        materials\chaofanaticeffects\*.*        allow_from_disk
        materials\console\*.*                   allow_from_disk
}
 

Stachekip

Gore-Spattered Heavy
Contributor
I'd generally say allow content from these folders:

materials\effects\...
materials\vgui\...
materials\backpack\...
materials\HUD\...
models\weapons\v_models\... (v_model replacements don't seem to work properly last I tested)
materials\overlays\...
materials\overviews\...
materials\Tile\...
materials\props\...
materials\models\props_gameplay\...
models\props_gameplay\...
materials\models\props_vehicles\...
models\props_vehicles\...
materials\models\flag\...
models\flag\...
materials\models\class_menu\...
materials\models\buildables\...
models\buildables\...

And for sounds, you could basically whitelist the folders for all sounds except the "player" folder

sound\ambient\...
sound\coach\...
sound\doors\...
sound\items\...
sound\misc\...
sound\physics\...
sounds\pl_hoodoo\...
sound\plats\...
sound\vo\...
sound\weapons\...

Pretty much every sound folder except for "player," where you could easily replace a sound to find the location of a player(and, of course, replace the decloak sounds).
 

Steak

Server-Clearing Cynic
Contributor
sounds ok but then you always want to keep it as locked as possible going full tilt on all files aside from one or 2 is asking for more trouble then its worth
 

Stachekip

Gore-Spattered Heavy
Contributor
sounds ok but then you always want to keep it as locked as possible going full tilt on all files aside from one or 2 is asking for more trouble then its worth
I pretty much only listed folders that people generally use visual skin replacements in, and tried to exclude anything that could give someone an unfair advantage over another(For example, I left out the folders that include wall textures).

As for sounds, I believe the folders I listed aren't ones that could include sounds that would give a player an unfair advantage over others.
 

RisenDemon

Epic Skial Regular
Contributor
I'd give this a +1
I replaced half of my weapon sounds with ones from GoldenEye. It's a pain to have to manually remove the folders just so I could play a round of Dustbowl without it crashing.
 

butterfingersman

Positively Inhumane Poster
Contributor
Plus one!
Remember that post I had a looonngg time ago about my sounds making really shitty crackly noises?
I had some metal gear solid music and sounds set when people were capping the point and all it did was make horrible crackly noises because of the poor item whitelist.
I'd love you guys foorrreeevverrr if you fixed this. <3
 

Stachekip

Gore-Spattered Heavy
Contributor
Apparently, we need someone to verify that my additions to the whitelist will not allow cheating.
 

Steak

Server-Clearing Cynic
Contributor
well it depends on what kind of cheats there are and what kind of resources they would require.... like with the addition of allowing skins would also possibly allow the skins for invis players being skinned..... if you could find a way to allow speciifc things to the list as opposed to open full and wide
 

Stachekip

Gore-Spattered Heavy
Contributor
Actually, we could just enable sv_pure 0 instead of using sv_pure 1. I just talked to a user known as Shugo, who is a respected contributor to TF2 and has worked with Valve multiple times. Here's his stance:

3:07 PM - Shugo: sv_pure is only really meant for competitions now
3:08 PM - Stachekip: One claim people have is that sv_pure 0 can allow undetected wallhacks.
3:09 PM - Shugo: yeah, that used to be the case
3:09 PM - Shugo: before valve fixed ignorez
3:09 PM - Shugo: now any working wallhacks are -actual- hacks that only VAC can deal with
3:09 PM - Shugo: sv_pure won't do shit against those
3:13 PM - Shugo: I just searched around
3:14 PM - Shugo: and it doesn't even seem to matter if sv_pure is on or not

3:15 PM - Shugo: and besides, very few people use wallhacks in tf2 anyway
3:15 PM - Shugo: tf2 is largely full of f2ps now
3:15 PM - Shugo: in all the time I ran sv_pure 0 servers
3:15 PM - Shugo: I never ran into anybody who seemed like they were mathacking
3:16 PM - Shugo: more people use legitimate skins than mathacks
 

Drum

Australian Skial God
Contributor
Mapper
We need this. I'm tired of not being able to play on dustbowl because of my legitimate skins / etc.
 

Perseus Dash Jackson

Epic Skial Regular
Sorry, wallhacking's not the only thing you can do with sv_pure 0. Frankly, it's better to be safe than sorry; you can have a pretty ridiculous number of skins with sv_pure 1.

We should look into that edited whitelist, though.
 

Drum

Australian Skial God
Contributor
Mapper
Sorry, wallhacking's not the only thing you can do with sv_pure 0. Frankly, it's better to be safe than sorry; you can have a pretty ridiculous number of skins with sv_pure 1.

We should look into that edited whitelist, though.

I only have two skins; one for the butterfly knife, and one for the demoman's stickies, yet my FPS drops like crazy on dustbowl, and after a few minutes TF2 crashes.
 

Perseus Dash Jackson

Epic Skial Regular
I only have two skins; one for the butterfly knife, and one for the demoman's stickies, yet my FPS drops like crazy on dustbowl, and after a few minutes TF2 crashes.

And it works without the skins?


Edit: Also, I think door sounds should be off the whitelist. You could theoretically turn them up super loud and know whenever someone's entering or leaving spawn etc. Same with weapons and some other stuff I likely missed.
 

Stachekip

Gore-Spattered Heavy
Contributor
Sorry, wallhacking's not the only thing you can do with sv_pure 0. Frankly, it's better to be safe than sorry; you can have a pretty ridiculous number of skins with sv_pure 1.

We should look into that edited whitelist, though.

What else can people do with sv_pure 0 exactly?

Edit: Also, I think door sounds should be off the whitelist. You could theoretically turn them up super loud and know whenever someone's entering or leaving spawn etc. Same with weapons and some other stuff I likely missed.

Either way, with sv_pure 1 on, if people use replacements for non-whitelisted sounds, they tend to be made screamingly loud and obnoxious, thus killing the reason for sv_pure 1 on sounds already.
 

Stachekip

Gore-Spattered Heavy
Contributor
Know if a door opens or spy uncloaks anywhere, for two. Personally, I think it should be sv_pure 2 on everything except idle, but yeah.
Sv_pure 2 is even worse. And if you didn't read what I just said before, sv_pure 1 and 2 already make sound replacements ear piercingly loud.

And honestly, I have no idea why anyone would need to make the door opening sound louder. It's pointless and the sound is already pretty audible. In all of my years of making skins and sound replacements, I've never known of anyone who replaces the door opening sound.