[bskll]

For the scout, I'll admit that you're correct, but only for bad wallhackers. A good wallhacker will wait until they pop out, knowing precisely where to aim once they do. It really looked like this could have been the case in this circumstance, but of course I can never be certain. Again, this all boils down to speculation and circumstance.

I didn't hear him because there was fighting going on below you, as I stated in my previous posts. I was suspicious as how you managed to pick out that the soldier was rocket jumping between the battle making the racket below you. The only other conclusion I could think of was that you also managed to 'see' him.

I actually agree with Womb somewhat. If I was 100% sure of my call, I wouldn't be going to all this effort to give Engineer a chance to explain so thoroughly. As humiliating as it is that I may have made a bad call, I refuse to rule it out, especially when the suspected player has been nothing but cooperative and respectful. I might be willing to lift the ban if I'm given a fair reason as to how you heard the soldier over the front door/grate camp battle. Especially since he was already tucked away in your center battlements by the time you came out.

if a wallhacker "simluates aiming" by adjusting crosshair after the enemy reveals, then its not really all that different than having a good reflex, which negates the advantage of wall hacking.

now as for the soldier, one thing should be pretty certain, rocket jump sounds pretty distinct to me. I hear a single, muffled rocket with a pause of about 2 secs, that's a suspect rocketjump sound to me. even among the firefight sounds downstairs, a rocket with pause of about 2 secs should be pretty disntinct, moreso if its followed by shots to your left side. Plus with source engine, the positional audio should enable you to determine where the sound is coming from. In this case, i head it coming from left of me, so i suspected a RJ into that part of battlement.