[[steam admin] + isa](10/26/2013) [9:25pm EST] (STEAM_0:0:15602686).

[Pootie Too Good]

Title: Username(of banned user) Date(of ban) Time(of ban) STEAMID(of banned user)



Name in Game: [steam admin] + isak
Steam-ID: (STEAM_0:0:15602686).
(STEAM_0:0:15602686).
Where:gungame
Link to ban: i did ban him, however, it's not showing up in the ban list?
Reason for perma ban: obviously hacking.

forgot to add poll, sorry, but it really isn't even a question whether or not he was hacking. just trying to make sure he doesnt come back

I'll link demo once map is over, but it is undeniably obvious and will be proven. thanks.

- - - Updated - - -

Attachment 7937 demo. i cant open demos on my css for god knows what reason, so i'm sorry, i can't give ticks. it was early in the game that he joined.

[Carmichal]

what? this format is revolting.

[phil.™]

Aren't you an admin? Why didn't you make the ban?
Up top, there is a "thread tools" click that and add a poll.

I'll check the demo when I get home.

[Pootie Too Good]

Aren't you an admin? Why didn't you make the ban?

i did ban him for 360 minutes just because that was the first number that came to my head. however, he is not showing up on the ban list for whatever reason?

[phil.™]

Yikers. That means the ban didn't go through. Just ban him on sourcebans with his steam id you have.

[CYBER]

ticks 10k...


HOLY FUCKING SHIT...


this is probably the best aimbot i've EVER seen in game...absolutely zero crosshair shake and jitter

the idiot is obviously aiming and walling, but put that in a good hacker's hands and holy fuck... god help us all.


hacks... and I might as well submit my fucking 2 weeks' notice if this new rage aimbot gets popular with valve's family key sharing...

[CYBER]

INTERESTINGLY enough,
the second desert went to spec, the guy left the game.
pootie, did you try to do a ban him by admin menu at that time around 12k before he came back?

because WHILE you would have been administering the ban, the guy was able to detect an incoming ban and forcefully quit the game and rejoin to bypass the ban.
I am definitely sure this was a script because he was mid-jump when he left the game, clearly something mechanic happened.


then, when he came back at 14k, you administered ANOTHER ban on his way bcos you typed
!ban isak 360 in the spec chat


A ban WAS NOT made by you, pay attention to the console output man. it said "steam admin isak HAS LEFT THE GAME" when u made that ban, it didn't say "steam admin isak has been banned for XXX minutes"...
Clearly the same script he had that detects incoming bans/admin has allowed him to LEAVE the server WILLINGLY before a ban is made... so make sure you guys always READ properly, and see if he was truely banned, and didnt just willingly leave to bypass the ban.

Because he just duped you guys, into thinking you banned him bcos of his script... in ibis, it didnt work out too well for him BECAUSE we have THIS process of posting a ban for a perma etc, but had it been in another community, the admin would have thought that he banned the guy, and forgot about checking sourcebans, and the guy would have returned again one day, all willy nilly.



So CAREFUL guys, always read the console dump in chat when u make a ban, and better yet, keep sourcebans bookmarked or tabbed on an open browser and refresh it to see if your ban was made. using the web panel is also good for banning steam_family_Sharing accounts, and LUA hackers, and to unban wrongful bans and ban disconnected players like THIS guy... so start having this habit.


PS: i just slapped a month ban on him till this thread is dealt with. I recommend all admins, ulas and clan members watch the demo
and see how the new isakRage v1 works.

[Pootie Too Good]

INTERESTINGLY enough,
the second desert went to spec, the guy left the game.
pootie, did you try to do a ban him by admin menu at that time around 12k before he came back?

because WHILE you would have been administering the ban, the guy was able to detect an incoming ban and forcefully quit the game and rejoin to bypass the ban.
I am definitely sure this was a script because he was mid-jump when he left the game, clearly something mechanic happened.


then, when he came back at 14k, you administered ANOTHER ban on his way bcos you typed
!ban isak 360 in the spec chat


A ban WAS NOT made by you, pay attention to the console output man. it said "steam admin isak HAS LEFT THE GAME" when u made that ban, it didn't say "steam admin isak has been banned for XXX minutes"...
Clearly the same script he had that detects incoming bans/admin has allowed him to LEAVE the server WILLINGLY before a ban is made... so make sure you guys always READ properly, and see if he was truely banned, and didnt just willingly leave to bypass the ban.

Because he just duped you guys, into thinking you banned him bcos of his script... in ibis, it didnt work out too well for him BECAUSE we have THIS process of posting a ban for a perma etc, but had it been in another community, the admin would have thought that he banned the guy, and forgot about checking sourcebans, and the guy would have returned again one day, all willy nilly.



So CAREFUL guys, always read the console dump in chat when u make a ban, and better yet, keep sourcebans bookmarked or tabbed on an open browser and refresh it to see if your ban was made. using the web panel is also good for banning steam_family_Sharing accounts, and LUA hackers, and to unban wrongful bans and ban disconnected players like THIS guy... so start having this habit.


PS: i just slapped a month ban on him till this thread is dealt with. I recommend all admins, ulas and clan members watch the demo
and see how the new isakRage v1 works.

if i recall correctly, it said to me, personally, that he had been banned.

edit: i know it told me that he was banned. i accidently hit no recoil instead of auto aim and it told me that was his reason.

[phil.™]

ticks 10k...
HOLY FUCKING SHIT...

This.
Holy shit, wow. No shakes, no robotic move, nothing. Obvious hacks, shooting through walls and shit.


I do agree with Cyber though. Every admin should take a look at this demo and see this new hack we could be dealing with.
Perma ban, closed.