AdjeLast time someone "revealed" something like this in order to create awareness on this forum, we got a step by step guide on how to modify Spy decloak sounds. We are 6 years later and Valve has not done anything to mitigate that; all it did is put it on the radar of bad actors who didn't previously know. I don't understand how people can look at that and think giving Valve x amount of time to address an even worse issue, and then going public with this will lead to anything. But I would love to be wrong about this.
Having had 6 years to think about it I think you're right. The decision was mostly fueled by hearing that at least one player had been using it in invite, and it was relatively unknown (from my pov). My HOPE was that it would show people how easy it is for a player to convince themselves that it was just another tf2 customization like the explosion script, and provide a reference for players to identify if someone responding suspiciously to a spy cloak/uncloak could be exploiting.
I will say 4 years ago I felt extremely vindicated: https://www.teamfortress.tv/post/1008124/cheating-to-hear-spies-is-painfully-easy
But I believe there has been incorporation of mastercom's fixes into tf2's code and as far as I'm aware this still works.
I'm removing the instruction part of my post, but I know this is a Pandora's box situation where I have no way to take back the shared knowledge at this point.
I won't suggest mur remove this information but I do think we have definitively shown that Valve does not care about the competitive integrity of the game, if you don't find something that breaks the money making machine you probably won't find a Valve employee who cares.