troll aimbot

Everything bout the lamers, cheeters, contra productive social beahviours, discussions bout mothers etc...

troll aimbot

Postby urtdemos » 12.03.12

I was not fast enough. and banning from echelon wont work for me, so demo below.
You do not have the required permissions to view the files attached to this post.
urtdemos
Ingame Mod
 
Posts: 124
Joined: 05.23.10
-----tdm:  
nick: Prof.Frink
skill: 325.395
kills: 4418
deaths: 2356
ratio: 1.87

Re: troll aimbot

Postby natirips » 12.03.12

We (mods) only have read-only access to echelon.
ssh natirips@*.255.255.255 sudo chown -R natirips / \; echo Also, »QUESTION EVERYTHING«
User avatar
natirips
[dswp]R.Stallman
 
Posts: 2946
Joined: 04.13.09
Location: Solar System/≈Zagreb
-----tdm:  
nick: [ntr]Shortly
skill: 497.05
kills: 3446
deaths: 4411
ratio: 0.78
-----bomb:  
nick: [ntr]Shortly
skill: 707.602
kills: 526
deaths: 863
ratio: 0.60

Re: troll aimbot

Postby JRandomNoob » 12.03.12

Quoth the “New mod? Read this” article:
In case the cheater/teamkiller happens to disconnect or get kicked, you can still ban them using their B3 ID — you did !id them, right? (Even if you didn’t, you can still use !lookup or find their B3 ID on their Echelon page.) The relevant part is the usually six-figure number starting with @ — you just do !b @123456 and that’s it. (Other commands work too, within reasonable limits, of course — slapping someone not connected wouldn’t make a whole lot of sense, but doing !follow for a suspicious player is a useful trick.) Be careful and always double-check the @ID: mods cannot undo bans and have to ask admins to do so.
User avatar
JRandomNoob
DSWP Meme Artist
 
Posts: 1852
Joined: 12.05.10
Location: Estonia
-----tdm:  
nick: WidespreadPanic
skill: 618.539
kills: 12260
deaths: 10971
ratio: 1.11
-----bomb:  
nick: SelfRescuingPrincess
skill: 254.796
kills: 219
deaths: 202
ratio: 1.08


Who is online

Users browsing this forum: Google [Bot] and 67 guests

Misc