get ur soft core cheater starter pack

• box/emo shadows
  
• loud (de)cloak sounds
  
• scope-less sniper zoom
  

This type of thread where you show people how to exactly replicate a cheat to denounce its usage is exactly why people gave delfy shit for his "exploits" videos. The only thing that this is about to accomplish is that people who want to use this cheat now have a helpful tutorial online to help them. You really didn't have to put the instructions there, the vid was enough and I struggle to see your reasons behind it.

Emailed valve about this like 5 times 3 years ago, its not only spy decloak sound you can also make a different sound for medigun and kritz being fully charged, uber popped, pyro phlog fully charged etc. Better question is why would you think making a public post on the most viewed tf2 comp forum is gonna be a good idea.
This game is like 80 years old shits gonna break people will find a way, let league admins know and spam valve, dont make shit public with an actual tutorial how to recreate it.

For the love of god at least edit the main post so it doesnt show the tutorial part

EDIT: honestly this goes to everyone, way worse shit has been found and people that should know about it already know about it and are trying to get them fixed (valve time). You can have a literal wallhack just by editing local files that works on pure 2. Please dont spoil comp by making shit like this public.

It's nuts to me that people are getting mad at Pete instead of holding the game's developer accountable.

There are community figures who have visited Valve DMing Pete to delete this thread instead of blaming Valve for this when there is nobody else to blame. Telling Pete to "hold off on the thread until the next major update"; the game has had so many stupid bugs, exploits, and glitches in it for years and Valve has done nothing to fix them.

Could you imagine if every time a CS team paused the game their money kept climbing until both teams were at 16k? Or if every time a team dropped/transferred the bomb you could hear it across the map. Or if Dota had ANY unintended game altering change. Those would be hotfixed within the day

Exploits like this, demo det, paused uber building, and countless others have been in the game for YEARS. Start holding the only party not only responsible for these problems, but the only party with access to fixing these problems accountable

it's too late to delete the thread or to edit it, someone already prob did it because they saw this thread and if they want to share it around they can just upload the file/folder to dropbox

i really don't think it was a good idea to make a thread for this (not just the tutorial but the thread in general), this has more consequences on the game than the box shadows do because this basically makes spy useless and basically ur padding ur death stat in logs if u try to go spy, meanwhile with box shadows yeah it's still a pretty big deal but at least it affects all classes equally (?)

You have to understand the risk you are taking as a small game community by making posts like these. This glitch has been known for at least 3-4 years now and valve have received countless emails about it already, do you think making a post on a forum they read twice a year is going to make them aware? On the other hand you are handing out a free way to completely banish an entire class and spoiling game thats had its peak half a decade ago. There are people dumb enough in this community that will use this even in league matches without a 2nd thought. In your post you are actually saying that there already are way better known glitches that arent even exploit worthy, just game mechanic bugs (sticky det, uber pause) and yet it takes valve months to years to fix them, how fast do you think its going to take them to fix this one?

Honestly just typing in google "cheat to hear spies tf2" brings this thread up on top result, delete the tutorial part asap

Just to add to what skeez is saying kinda..

I've just spent the last ~3 hours trying to get sv_pure to work properly. It's actually just fucking broken.

The game_sounds files are in the blacklist for sv_pure 2. They're there properly to be blocked by pure, and re-extracted from the Valve signed vpk to be default. But there are a few issues.

1. After the sv_pure 2 checking finds one file that isn't correct, it stops checking the other files. If you join a server with sv_pure 2 these files are checked:

	sound\...                            trusted_source
	models\...                           trusted_source
	materials\...                        trusted_source
	particles\...                        trusted_source
	scripts\game_sounds.txt              trusted_source
	scripts\game_sounds_manifest.txt	 trusted_source
	scripts\game_sounds_player.txt       trusted_source
	scripts\game_sounds_vo.txt           trusted_source
	scripts\game_sounds_vo_handmade.txt  trusted_source
	scripts\game_sounds_weapons.txt      trusted_source
	scripts\soundmixers.txt              trusted_source

But if you join with multiple game_sounds files you will get this error:

Reloading sound file 'scripts\game_sounds.txt' due to pure settings.

... and that's it. It stops there. In order to get the game_sounds_weapons.txt file to be properly checked by sv_pure, I had to remove all the individual file checks besides that one.

2. The fuckin check doesn't even work man lmfao. My suspicion is that the custom folder was added and sv_pure was never adjusted accordingly. So when sv_pure tries to give tf2 a new file to use, it never messes with the one stored in custom. So it makes some weird zombie shit happen where sometimes it uses the overpowered shit, but it also 100% of the time plays the spy cloak sound. Video example:

https://youtu.be/GM-qV-XMjKs

I get why you guys are frustrated but it's so STUPID that so many people are saying "I already tried to tell Valve about this" while also saying "You shouldn't give this more publicity". If you told them, and they didn't fix it, then they decided it was irrelevant. It's fucking not when people are already using it in comp.

I already talked to league admins. Everyone that says they've got buddies @Valve link them this. I spent the last 4 hours doing more troubleshooting on this issue than anyone at Valve has I'm sure.

Now someone help me w/ my networking project that I should've been working on instead

btw this shit used to be an issue with items.txt (https://www.teamfortress.tv/post/341960/more-dumb-stuff-you-can-do-with-the-item-schema) Valve fixed it in 2015.

As of the October 15, 2014 Patch, items_game.txt is protected by a digital signature and neither the client nor the server will start up if it has been modified.

They can (and have been able to) do the exact same thing with these files. Absolutely no reason for people to be able to edit these files.

who the fuck is telling op to delete the steps lmao
literally the only way the people who maintain this game are gonna fix this is if pubbers start complaining
spread it wide and far
http://archive.is/JIbdN for prosperity

i mean yeah but where are you gonna draw the line?
what about explosion removal? or removing the soundscape? or changing surfaceproperties? or medic radar?

yeah that totally worked for box shadows too right guys?

One is an exploit involving tweaking your GPU settings (NOT DEVELOPED BY VALVE)
One is a file edit that is literally supposed to be blocked by sv_pure 2 and isn't (DEVELOPED BY VALVE)

They're very different.

E: Also you listed off stuff like the explosion script like they're equal. You know they aren't. Imo none of this shit should even work, but TF2 isn't locked down at all properly. It's just ridiculous to ban for things as minor as that so we let them slide in leagues.

:thinking: is this when we go make a promod?

it isnt a gpu tweak its a hudfile
also removing soundscapes accomplishes the same task of making it easier to hear things without having to turn your volume up higher which is the essence of any "sound hack" its not as though it makes it so you can hear things that wouldnt make noise otherwise

	sound\...                            trusted_source
	models\...                           trusted_source
	materials\...                        trusted_source
	particles\...                        trusted_source
	scripts\game_sounds.txt              trusted_source
	scripts\game_sounds_manifest.txt	 trusted_source
	scripts\game_sounds_player.txt       trusted_source
	scripts\game_sounds_vo.txt           trusted_source
	scripts\game_sounds_vo_handmade.txt  trusted_source
	scripts\game_sounds_weapons.txt      trusted_source
	scripts\soundmixers.txt              trusted_source

Reloading sound file 'scripts\game_sounds.txt' due to pure settings.

one thing to bring discussion and awareness to a specific cheat, and a whole other thing to give a step by step guide on how to use aforementioned cheat. You are telling people there is an undetectable full proof way to cheat and the threads tone is valve will never fix that, how do you think that's a good idea.

lol hl

twiiku please make a promod i will give you 2,000,000 million zimbabwe dollars

Skeez you can be mad at Valve for that AND be annoyed at this thread, the two are not mutually exclusive. I just don't think Valve even answer to their email, so me ranting about them in a videogame forum will do nothing.
While I understand that the solution is likely to come from the community, there's got to be a better way to keep track of the technical side of things than a thread (with a nice clear title for search engines) that is able to help any wannabe cheater.

Stop calling for the thread to be deleted, morons. This is how you're supposed to proceed when you find an exploit but the company refuses to fix it: you make it public. If the company still won't take action then your anger should be redirected at the company, not the whisteblower.

Drama like this is good, believe it or not. It gets everyone butthurt and that might just get something done... Or not because this is Valve we're talking about. Hey, didn't Jill browse the tftv forums? Wonder where that guy went!

What? so youre saying valve wont do anything, so the community has to do something, but we shouldnt tell the community?
If they havent fixed it from emails 3 years ago, making everyone publicly frustrated about it is a great kick in the ass for valve to do something

This scorched earth tactic seems dubious considering the sheer amount of time that Valve takes to update the game.

There is never going to be a hotfix for TF2 in 2019. Valve has already been noticed. We know for a fact due to their silence on other, more damaging bugs (sticky det bug, uber building during pauses) that they may very well not bother/be able to fix it. The only thing that this tutorial accomplishes is that more people now know how to abuse the game.

Well surely there's got to be a better way to reveal this information than a cheating tutorial on a forum, like a more private doc or something. I'm not a really a computer dude so I don't have a tangible example, but I'm sure there's got to be something.

Situation 1: Only a few people know about, use it. They have massive advantage over people who don't. Valve doesn't fix it and a few cheaters keep being able to play the game better than everyone else

Situation 2: knuck publicises it, more people use it and it is no longer a secret advantage for a certain few people. The more use it, the more spy becomes useless. If the majority use it and spy becomes completely unviable, Valve has to do something.

I think the line is pretty obvious:

• box shadows makes it trivial to spot people around corners or in hiding spots - obvious exploit
  
• making decloaks loud makes it extremely obvious when a spy is around - obvious exploit
  
• removing the sniper scope gives you a lot of extra vision - obvious exploit

And notably, valve did try to stop both changing decloak volume (it's just that sv_pure doesn't enforce the files properly) and sniper scope removal (they fixed a trivial version but not one that uses anim locks). And as for box shadows, where you change how shadows work by misnaming a hud font declaration, that's about as blatant of a glitch as you can get -- it's just a glitch that also gives you a very big unfair advantage. I think it's fair to say those are exploits.

Compared to:

• Explosion removal makes the screen a bit clearer sometimes - not an exploit
  
• Soundscape removal removes a very small amount of useless noise on some maps - not an exploit
  
• Surfaceproperties also makes the screen a bit clearer sometimes - not an exploit
  
• Medic radar is intended behavior of the command in the first place - not an exploit

Of those medic radar's the only one I could see anyone actually considering an exploit since it's the only one that gives you any actual advantage, but that's also something that would be really easy for valve to stop if they wanted to. All of which are files that could be blocked in sv_pure or commands that could be limited / removed / locked. They just aren't problematic, unlike the actual exploits above.

What are you on about? You can hear multiple sounds at once, and spy decloaks are very distinct. A few ambient noises aren't going to block your hearing from picking up on a spy decloak.

The point of increasing the decloak sounds' volume is to, you know, make them actually louder. Either by upping their volume, or making everything else quieter and then upping the game's total volume to compensate. It wouldn't do anything if it was just "a few sounds are removed."

everyone use this script until valve fixes it

But how do you ban it? Maybe the dude that just turned around actually heared the regular spy noise. What can you look for in a demo without comms (maybe someone told you to turn around) to prove this exploit was used?

Also I agree in making this public and it should be crossposted to r/tf2 and r/gaming too showing the casuals what this game has become thanks to valve. As adysky said noticing valve and keeping the exploits relatively secret has not worked for several years, time to take a more radical action.

This but unironically

This is all faith from me, but Valve does not always wait for massive community backlash to fix stuff. People like sigsegv have seen many bugs they submitted eventually fixed, and all they did was post video evidence and send emails.
While I have faith in Valve eventually fixing the thing, I really don't believe that they will change their update "schedule" for this. With no hints of any update in sight, we'd be looking at 4 months of unplayable spy assuming the update drops in early July, or 7 months if it eventually happens during Scream Fortress.
Also, the comp community is too small that even if we all started abusing this, we wouldn't make enough noise for Valve to consider us. You'd have to get pubbers on board, and they won't care since pubs are on sv_pure 1 anyway.

To me the options look like this
Situation 1 : We try to limit the spread as much as possible so that most players don't have to play against this, while hoping that Valve does something next update.
Situation 2 : We somehow rally a large enough portion of the community under our banner, make spy unplayable everywhere for at least half a year and we're still left hoping that Valve fixes it since it does not affect pub play so it's not really a priority.

I understand that it is frustrating to have to wait for Valve to fix their game for absurd amounts of times even 10 years after the launch, but seeing as the TF2 staff is made up of 2 and a half dev and a potted plant, I really don't think we can do anything to rush them by making spy utter garbage.

To me our most realistic options have to be built by us, either a plugin blocking that or a way to detect it for AC review, but I don't know a lot about the technical side of the game so I don't know how feasible that would be.

now we just need a script to change the spycicle melt sound to the mvm tank explosion

Aelkyr
Pubs are on pure 2, pure 1 is literally "pure 2 but you can choose to add your own stuff"

Stop acting like valve have just been too gosh darn busy to fix a class-breaking bug. It took me less than 1/5 of a single work week to diagnose and provide a possible solution to the problem, having no CS background or ever working with this type of problem in the past. Also not being a valve employee.

A lot of people that are giving counter points to what I did have very valid reasons until #38 and #39. I questioned if exposing this was the right thing to do, until it was actually so easy to come up with a solution to. If they've been emailed about this for years and done nothing about it clearly the priority needed to be raised.

Pete
You're right, there has been some misunderstanding on my end due to my lack of technical knowledge, like no tknowing the difference between sv_pure 1 and 2 and in message #37, I did not catch that you found a simple fix.
It's just that I've never seen Valve release any sort of hotfix, so to me the loss of spy as a decent class for multiple months outweighs the eventual benefit that Valve will eventually fix this. I guess it's just personal preference at this point. Regardless, sorry about my poor reading of your second and third posts.