I fully agree on Brassie being an admin. He's online very often and keeps a keen eye on the cheaters/spammers.
 
Test question:
If you were admin and a player (XXX) started saying that another player (AAA) was hacking, everyone else on the server said "hes not hacking, AAA is just good", XXX disagrees and then initiates a voteban against AAA, which fails to pass, XXX is unhappy that the vote fails, and still maintains that AAA is cheating, he then proceeds to make a report against AAA which is passed, what would be your course of action through all of this?
 
player XXX
300_2270082.png
 
+1 on this app

EDIT: Please approve this, so i don't have to go to the scummy 2Fort
No offence here

But defo a great candidate
 
Test question:
If you were admin and a player (XXX) started saying that another player (AAA) was hacking, everyone else on the server said "hes not hacking, AAA is just good", XXX disagrees and then initiates a voteban against AAA, which fails to pass, XXX is unhappy that the vote fails, and still maintains that AAA is cheating, he then proceeds to make a report against AAA which is passed, what would be your course of action through all of this?

If I was on the server:

When XXX first states AAA is hacking/cheating, ask XXX why he thinks AAA is cheating/hacking. If the reason given seems legitimate, I would check HLstats and AAA's steam account for any suspicious signs (low play time, High k:d etc...) , then switch to spectator and observe for any signs of hacking- Locking on to players, even cloaked spies (aimbot); Shooting/being able to see through walls (wallhack); perfect backstabbing- not seeing the knife come up before a backstab every time (autobackstab/automelee); Always/ mainly having crits (crithack); Increased speed (speedhack). Hacks such as esp are harde to detect, but if player AAA is able to kill EVERY spy that is about to backstab him then it will raise suspicion- and will consult other admins before action is taken on AAA.

If action is taken, I would record a demo before banning with the command: /sm_ban "#STEAM_0:0:0A0A0A0" 0 "*Hackname*"

If I was responding to a report:

Whilst connecting to the server, Check AAA's steam profile and HLstats as above. Then switch to spectate and determine whether there are any hacks being used- as above.

If AAA is hacking/cheating, then I would record a demo and ban with the command: /sm_ban "#STEAM_0:0:0A0A0A0" 0 "*Hackname*"

If AAA isn't hacking:

After determining that AAA is not hacking, I would send a private message to XXX using: /sm_psay "XXX" "AAA is not hacking, so please do not start another vote or report- as it will be classed as abuse"

I would then stay on the server for 10 minutes to make sure another vote or report is not started, then go back to 2fort :3
(If XXX starts another vote after this warning, I would ban them for the appropriate legnth of time.)
 
If I was on the server:

When XXX first states AAA is hacking/cheating, ask XXX why he thinks AAA is cheating/hacking. If the reason given seems legitimate, I would check HLstats and AAA's steam account for any suspicious signs (low play time, High k:d etc...) , then switch to spectator and observe for any signs of hacking- Locking on to players, even cloaked spies (aimbot); Shooting/being able to see through walls (wallhack); perfect backstabbing- not seeing the knife come up before a backstab every time (autobackstab/automelee); Always/ mainly having crits (crithack); Increased speed (speedhack). Hacks such as esp are harde to detect, but if player AAA is able to kill EVERY spy that is about to backstab him then it will raise suspicion- and will consult other admins before action is taken on AAA.

If action is taken, I would record a demo before banning with the command: /sm_ban "#STEAM_0:0:0A0A0A0" 0 "*Hackname*"

If I was responding to a report:

Whilst connecting to the server, Check AAA's steam profile and HLstats as above. Then switch to spectate and determine whether there are any hacks being used- as above.

If AAA is hacking/cheating, then I would record a demo and ban with the command: /sm_ban "#STEAM_0:0:0A0A0A0" 0 "*Hackname*"

If AAA isn't hacking:

After determining that AAA is not hacking, I would send a private message to XXX using: /sm_psay "XXX" "AAA is not hacking, so please do not start another vote or report- as it will be classed as abuse"

I would then stay on the server for 10 minutes to make sure another vote or report is not started, then go back to 2fort :3
(If XXX starts another vote after this warning, I would ban them for the appropriate legnth of time.)
Pretty much spot on, the only thing extra I would do is check XXX's steam id on source bans and his chatlog to see if he has a history of excessive voting
 
Had a good chat with Joeman last night, he has a good head on him, down to earth, and an all round nice guy. I think he understands responsibility and the implications that it brings.
He would make a good and fair admin.
 
Had a good chat with Joeman last night, he has a good head on him, down to earth, and an all round nice guy. I think he understands responsibility and the implications that it brings.
He would make a good and fair admin.

I thought it was mainly about cider? :D
 
There is a hacker on a server using a name changer causing his name to change to that of a random player on the server once every second. What do you do?
 
There is a hacker on a server using a name changer causing his name to change to that of a random player on the server once every second. What do you do?

Switch to spec (Obviously)- And spectate the person who's name keeps changing. If it changes once a second- it should be fairly obvious. Type status in the console then wait until the name changes. Type status again so you have 2 different sets of steam IDs.

Type CONDUMP to dump the console to a text file- making it easier to read and compare. On each of the sets of Steam ID's look for the duplicated names. Spot the same steam ID within each name pair. Double check that that is the right person by entering it on HLStats- and seeing how many name changes there are- and what they were.

Once I am sure that I have got the right person- Ban with the command: "sm_ban "#STEAM_0:0:1234765" 0 "*Namehack/Hacking*"" (Hacking if he wasn't just using a name hack but a crithack, or an aimbot too)
 
  • Like
Reactions: Firekip and CiNiC