Admin Training Guide

[RedDevil6193]

HeLLsGamers

Admin training guide

Other Guides/Rules:

Jailbreak Admin Guide

Jailbreak Bible

How to catch a hacker

Guide on what NOT to do

HLDJ/Mic Rules

Macrodox Guide

Rules for Racism

Guide on getting proof for bans

Guide To Make A Ban/T-List Report

 

 

 

General Rules

---

• Remember that as a paid admin, you are NOT obligated to take action or use any of these commands listed.
• Use the following procedure:
  • Warn (through either mic or chat)
  • Kick (with a reason)
  • Ban (and post proof)
• Do not take someone's word as proof.
• You can use admin commands on yourself as long as it's not considered affecting gameplay (I.E: spamming commands on yourself, slapping yourself, etc).
• Do not use your admin commands on any admins at your level.

 

Chain of Command
Staff
v
Trusted Admins
v
Moderators
v
Gold Admins
v
Everyone else

 

• Do not override (undo) any other admin at your level. Even if you think it is wrong
• To keep our servers populated you need to understand that people won't always agree with you. Unless you are personally targeted by name more than once or twice, please refrain from kicking a target. Try and wait until you are personally harassed. In most cases, a warning through chat should be given.
• When warning a target there are many ways it can be perceived. Take into consideration that you are an admin, if you are in HG or not, you are representing our servers. When warning be respectful to the targets, make them feel like they are welcome to play, otherwise they won't.
• Not really a rule, but more of a recommendation. Always have proof, this means you should be recording demos, and taking screenshots whenever you are admining.
• If you ever have any questions ask a member of leadership.
  • Admin levels go as follows:
  • Gold < Moderator < dA < dL+ (with access: root)

Main Sourcemod Commands (CSS, TF2, CSGO)

---

 

How to use a command on a target with special characters in their name or when there are multiple clients with the similar names.

 

Open console, type status use the corresponding # to the left of their name.

For example !slay #179. Would slay ?¢s?.

or

!admin > target commands > slay > find their name.

 

 

Quote

Command in chat

Syntax (When not shown it is either !<command> <target> or just !command

Why and when you should use it - Important Notes

• Most these commands can be used in console. Substitute the ! with sm_ (example: sm_admin instead of !admin)
  • If the console command is different it will be shown in a blueish color
• All commands can be used in chat with a '/'. This will make the command invisible to players.
• When dealing with someone whose name is @t/@ct/@all/@me you can easily use your admin command on them specifically by typing # before their name: !ban #@t
• Command parameters that have spaces in should be surrounded by double-quotes, e.g. /ban "player name" 60 "player was whatever reason ..."
• for <target> you can use the following (depending on the command):
  • Player's Name
  • Player's Status ID
  • Player's Steam ID
  • @me (targets yourself)
  • @aim (targets a player in your crosshair, this is very dangerous so be careful doing it)*
  • @t(s), @ct(s), @spec, @all, @dead.*
  • @blue, @red TF2 only*

*These should not be used often if at all, it is better to just do the command on individual players. Doing commands on a large group of people may get you an abuse report.

 

!admin

This command opens up the admin menu, which lists all sourcemod commands available to you:

 

 

!who

This command is used to determine whether or not a target is an admin in the server. You should ALWAYS use this first before taking any action. To use this command you can type !who namehere or you can type !who then check console for every member that is in the game.

 

@ In all chat

This command is used for verbal warnings for breaking server rules or explaining server rules.

 

@ in team chat

This will be useful for discussing punishments and asking questions on what to do in certain cases of punishment.

 

!slap

*sm_slap <target> <damage> (Damage should always be left blank or 0)

This command should RARELY ever be used. It should only be used if a target is stuck somewhere on the map where he cannot move himself. Although 99% of the time the slap will not help him out of being stuck.

 

!slay

This command should only be used in Mini-games or Jailbreak. In minigames it should only be used when someone is delaying the map.

 

!kick

*sm_kick <target> <reason> (reason required)

This command kicks the target from the server. Should be used after a warning has been given for breaking a server rule.

 

!ban

*sm_ban <target> <time (no required)> <reason (not required)> (default time is 2 hours, 1 hours on all CSS server except Jailbreak)

This command bans the target from the server. Adds the ban to HGBans. You should be posting proof.

 

!mute (!unmute to undo)

*sm_mute <target> (# of rounds if in Jailbreak)

This command is used when a target is being disruptive through his mic, either spamming HLDJ, or spamming with his voice. Removed on map change.

 

!gag (!ungag to undo)

*sm_gag <target> (# of rounds if in Jailbreak)

This command is used when a target is spamming chat and or being disrespectful to a target so much that it is becoming harassment. Removed on map change

 

!silence (!unsilence to undo

This command is used similar to mute and gag a target. This does not work correctly on Jailbreak.

 

@@ in all chat or !psay

*sm_psay <target> <message> (When using !psay or sm_psay "" <quotes> are required for the message. Be careful when using @@ because you could accidently use all chat)

Sends a private message to a target.

 

Other Sourcemod Commands (CSS, TF2, CSGO)

---

!observe

Auto-spectates a target. Useful when recording a demo for a ban report.

 

!endobserve

Stops observing the client

 

!mdx_stats mdx_stats

Prints out the Macrodox statistics of the target in console. Read the guide on mdx_stats.

 

!teamswitch_spec teamswitch_spec

Moves target to spectator immediately. CSS and CSGO only, except Jailbreak.

 

!teamswitch_roundend teamswitch_roundend

Moves target to spectator at round end CSS and CSGO only, except Jailbreak.

 

!teamswitch_death teamswitch_death

Moves target to spectator on death CSS and CSGO only, except Jailbreak.

 

!adminspray

*sm_adminspray <target> (leaving target blank is similar to using @me)

Sprays the spray of target where you are facing. CSS and TF2 Only.

 

!removespray

*sm_removespray (while looking at the spray)

Removes the spray of target, you have to look at the spray to remove it. Only warn>Kick>Ban if they spray their spray. You cannot make people change their spray. Will not work if the target has left the server. CSS and TF2 Only.

Details about adminspray and removespray:

When a spray is removed with !removespray, a menu will display on your screen with warn/slap/kick/ban options. Use these accordingly. It's wise to snap a screenshot immediately after you choose an option, for you now have the proof of a warning/kick and the time this occured.

Even though the warning option in !removespray displayed to the target is "Please change your spray, it is innapropriate", don't force players to change sprays, only to not spray the bad spray.

Some things about sm_adminspray you should know.

When adminspraying a players spray, try to only do it in alarm room under the map when you are dead so you and other admins know only an admin sprayed it there. Then let other admins know via admin chat to not !adminspray or !removespray the spray. If the spray isn't that bad you could respray it in a high place normal players wouldn't be able to reach. Also when you do !removespray, the spray isn't really removed but resprayed to the VIP water and air bubble. So don't punish a player if you see a spray there as it might have been removed by an admin elsewhere in the map. Check with other admins in admin chat to see if another admin did !removespray, then !adminspray the spray in alarm room and tell other admins

 

!nospam

*sm_nospam <target> 1 (0 to undo)

Prevents target from using HLDJ. CSS and CSGO only

 

 

 

Thanks to burnt

[Suicide]

Whats the difference between silence and gag?

 

I don't think we have silence on the servers, but normally:

 

!silence - would mute + gag a player. Making it so they can't talk, or type.

 

!gag - Just makes them not able to type.

 

!mute - Just makes them not able to talk.

[Suicide]

This rule:

• Do not use admin commands on yourself. Only one that is okay is slaying yourself. If you broke a rule the best thing to do it to apologize and don't do it again.
  

Changed to:

• You can use admin commands on yourself as long as it's not considered affecting gameplay (I.E: spamming commands on yourself, slapping yourself, etc).
  

[Purplex]

This rule:

• Do not use admin commands on yourself. Only one that is okay is slaying yourself. If you broke a rule the best thing to do it to apologize and don't do it again.
  

Changed to:

• You can use admin commands on yourself as long as it's not considered affecting gameplay (I.E: spamming commands on yourself, slapping yourself, etc).
  

what if you are stuck or tying to get some one elce unstuck is that alowed?

[Jglake]

what if you are stuck or tying to get some one elce unstuck is that alowed?

 

 

!slap

*sm_slap <target> <damage> (Damage should always be left blank or 0)

This command should RARELY ever be used. It should only be used if a target is stuck somewhere on the map where he cannot move himself. Although 99% of the time the slap will not help him out of being stuck.

 

 

[Hydranix_]

I'll add that a sm_slap can be useful in situations where a player is not responding to messages in chat, but a sm_kick is too severe to be warranted. Slapping for 0 damage very clearly signals to a player that an admin requires your attention.

 

Every time I've used it like this, it successfully started dialog with the player and myself.

 

 

- - - - - - - - - - - - - - - - - - -

The following is confirmed for CSS, unknown for other games.

----------------------------------

 

Another shortcut for targeted commands is @bots which targets obviously, all bots.

 

----------------------------------

 

Directed/Private chat also supports:

 

(in team_say)

 

@@ text : sends chat message only to [Mod]s and above. (Specifically to exclude (gold) [Admin]s)

@@@ text : sends chat messages only to [staff]s and above. (Specifically to exclude [Mod]s)

 

----------------------------------

 

!teamswitch <player> (console: teamswitch <player>)

 

Is also valid, however it switches the target immediately, without respawn, and without changing their player model.

 

It's never appropriate to use this command in CSS.

 

-----------------------------------

Spray removal warning

 

When removing a spray, the punishment menu is opened immediately after removal. On the deathmatch servers, yours guns menu can become overlapped by the punishment menu. The guns menu will no longer be visible, only the punishment menu, however selecting an option will instead interact with both menus. The punishment menu will close upon choosing an option, the punishment will be issued, and your guns menu option will have been selected, the punishment menu will then show again shortly after, if the guns menu has not completed and closed, it may overlap the punishment menu and you may accidentally punish a player.

 

The timing of the punishment menu showing again can be unexpected as well, and you may accidentally punish a player especially if you use 1-4 to select weapons.

 

This is a limitation of the plugin system and sourcemod.

[nielsfalko]

 

 

!teamswitch <player> (console: teamswitch <player>)

 

Is also valid, however it switches the target immediately, without respawn, and without changing their player model.

 

It's never appropriate to use this command in CSS.

 

fun fact u can use this in css just IF jb returns

[Yiddman]

Cant bind a key for !admin? It shows admin unknown command.