• Section 1 - What is a 'Warden'?

• Section 2 - Eligibility.

• Section 3 - At the start of round.

• Section 4 - CT Control.

• Section 5 - Moving a group of T's.

• Section 6 - Initiating games.

• Section 7 - Dealing with rebeller's/attempted tricks.

• Section 8 - Last request and deathwish.

• Section 9 - Closing statement.

---

---

At the start of the round is where, as a warden, you should instantly be looking to assert yourself. Once you have claimed warden, initiate a command. The command which generally should be played here is a command which you can use to instantly see how many T's you are going to be dealing with and their positions within main cell area. 
A good command to use here would be something similar to "Touch the front of your cell and face the back and freeze at all times." As soon as you emerge into main cell area, you and your CT's should instantly scan the cells. After 3 seconds have passed you will usually find people are either slow to react or they are touching and facing the front, or maybe even moving side to side for some reason who knows. At this point you and the CT's and instantly pick off a few T's and lighten your workload.


After the initial command and kill phase, which should take no longer than a few seconds, you want to move onto positioning yourself and your CT's in a way which secures the main cell area and gives you good 'arcs of fire' into the main cell area. The image below shows this concept perfectly.

As you can see there is a field with trees in to the front of the 4 men with weapons. Their 'arcs of fire' are the dashed lines starting from their rifle muzzles. If an enemy comes into the first mans arc, it is his responsibility to eliminate the threat. 

As you can also see, the mens arcs interlink, crossing over each-other to ensure there is no space left unwatched. This is a basic tactic and is extremely effective in ensuring mutual support.

Please re-read this section if you have to and make sure you understand it, as I will simply be referring to this principle as ARCS from now on.

Imagine the field is the main cell area, and when the cells open, no matter where the T's try and escape to, it should be covered by at least 2 CT's, leaving the T's little chance of survival. 



ONE OF THE MAIN REASONS CT'S LOSE ROUNDS IS BECAUSE THE GUARDS ARE NOT COVERING EACHOTHERS ARCS, OFTEN LEAVING 1 CT TO TRY AND DEAL WITH 5 REBELLERS. 

As the warden, make sure you identify easy escape routes for the T's and get CT's to have eyes on those areas. If you see a CT b-hopping with his knife out and not paying attention to the cells, educate him quickly.

Second of all, you are extremely vulnerable as warden to attacks. T's will attempt to kill you first as to cause chaos and disruption in the early phases of the round.
You must position yourself into a spot where you are far enough away from the T's to avoid a rush, but close enough to observe and react accordingly. Please see the diagram below.




I have used the cell area from Clouds as an example here. The red zones are what a warden should consider HIGH RISK areas. These are places where you are either un-necessarily close to T's or where you are channeled into going one direction only, such as the bridge to portal. As a warden you should only go into these areas when they are KNOWN to be clear and your CT's arcs are covering these areas. 

The orange lined zone is classed as MEDIUM RISK. These zones are fairly risky to be in as warden but sometimes you will need to enter this area to give yourself better situtional awareness or travel through to get to an area. Make your time spent in these areas down to a minimum and only use them for essential travel.

The green zone is classed as LOWEST RISK. This means that in this zone you get a good view of the entire area, there is some solid cover and you are able to move about in this zone with relative safety. All possible enemy contact will come from your direct FRONT in this position, it is extremely unlikely at this early stage of the round anyone will have been able to get behind you.

As a golden rule, you need to make your stay in the main cell area as short as possible. One or two commands, a few T's down and start thinking about moving on. Please see below an example of BAD WARDEN POSITIONING.



As you can see from the image, the warden has gone into a cell, possibly to kill a rebeller up close and personal, and has now put himself in a position where he has only one entrance and exit, making it easy for the T's in the surrounding cells to rush him, kill the warden and also get a free weapon for their troubles. 

On a side note, try not to let more than 2 people hunt at the start of a round. You need complete control of the main cell area at first, and more weapons pointed at T's guarantees that. Also, if you know you have 2 LEM's and 4 silvers on CT, it would be wise to send at least one of the higher ranks off to hunt, as their personal skills SHOULD be a higher level.

---

In this section we will go further into a subject which we have already touched on which is CT control. This basically means setting up your fellow CT's in a position which will benefit you all if a rebeller(s) decide to take you on.
Sometime there is nothing which can be done, if a T has spawned in a vent cell, got and awp and camped out on the other side of the map and lines up a shot on you, that's just unlucky, but there is no reason for CT's to be defeated by a one-man ambush.

We will now review the image below;


The green circle and arc on the left is the warden. He is midway through a command and is most likely looking around thinking what game to play. Ideally, he should have pre-planned in his mind by the time he got here which game he is going to play. The CT's on the tower near the portal have positioned themselves well. The one in the green circle is in an ideal position, covered from the rear by the tower and has good arcs to his right incase one of the T's attempts to run. The T in red is in an awesome position in terms of getting a good arc on the area and overlapping with his fellow CT and warden, but being ontop of the tower exposes him to fire from a 360 degree angle. 

The CT circled in green near jumprope is possibly hunting, heading toward a well-known rebeller area. Wether or not he has permission from the warden to be there is an issue, but if the warden has told him to hunt there, that is good wardening, as he is detatched from the main group to avoid to get caught up in a direct ambush, but is close enough to react if a rebeller was to appear.

Now we switch our attention to the CT circled in blue, who was positioned in a terrible spot and has paid the price for it. Just before this screenshot, a rebelling T came out of the portal to extreme climb and awped the CT. This occured due to the CT being in a complete lack of cover and having no support. The warden should have identified this CT and told him to gain a better position.

As a warden, you must do your best to position your CT's in a way which ensures security and your safety. Do not be afraid to place a marker and tell a specific CT to stand in it and watch a certain area. They will listen to you. If they do not, inform staff and they will be teamlocked.

If you want to write a guide in order to get it in this section you need to go through a small process which involves quality control and an originality check. In order to get your thread posted here you will first have to post your guide inside our 'other' (link) forum section. If you are posting your guide in the other section in the hope for it to become an 'official' guide you will have to do the following things:

• Include the [Guide] prefix in the title of your post.
  
• Make sure the guide has little to no grammatical errors, same goes for spelling errors and punctuation errors.
  
• Format your guide, make use of the features of our forum such as bullet lists, quoting, font size and alignment to increase the readability of your guide.
  
• Make sure your guide is relatively easy to read and to understand as many of our forum users do not speak English as their native language.
  
• Make sure that your signature does not show at the end of your guide (untick the signature box when posting).
  
• When including images, make sure they are all being retreived via https instead of http.
  
• Make sure you describe every subject in-depth; if you include multiple terms make sure you explain them all in-depth as well unless another guide has already mentioned them.
  

As soon as your posted guide got reviewed by a valid member they will either supply you with constructive criticism, which you will then have to read through and work on, or they will move your guide to this section. If your guide got moved to this thread you are still able to edit your guide and possibly delete it. A guide can be created by multiple authors if the other authors involved are mentioned in the guide itself including their forum username (if applicable).
When you have posted enough guides you will be granted a special forum rank which allows you to move and review other people's guides. It also gives you a custom title on the forums and increases your chance of becoming part of our staff team. If you really show to have talent towards writing informative posts we can ask you to write other things on our forums, such as improving rules, update posts and more. We can also ask you to become a forum moderator which involves editing, closing ,removing and moving posts if needed too.

Happy writing everyone!

Aight, after some tinkering I decided it a better idea to write a separate microphone plugin that relies on 1 easy to understand command

!microphone <target>

Thats right! No more teambanning! Bob doesn't reply to the mic check? -> !microphone bob 0

Everyone on the staff team will know the feeling when after teambaning  bob, the next round bob realised he fucked up and and he starts using his microphone!

This fear is now over ! any staff (yes any, even informers) can now just simply do !microphone bob 1, this will instantly allow bob to rejoin CT ;).



I added support for this across the existing plugins



so when using !teambans/!teamlocks you will see the no mics aswell.

the new plugin comes with an interactive list too!

Anyone can type !mics and it will show you ;)
non staff view



staff view


When you select a player you can change his status



so tl:dr

added

sm_microphone <target> (get individual status)
sm_microphone <target> [0/1] (set individual status)
sm_mic as alias of sm_microphone (alias)

sm_microphones (optional:<target>) (interactive menu /get individual/filter/everyone status)
sm_mics (alias)

I'm converting all the teambans to the new system Converted 137 teambans into microphone bans
For developers, there is a new API endpoint

• /jailbreak/api/v1/microphones.php
  

Other changes

• Added killing CT's as warning
  
• Added spamming guns as CT as warning.
  
• Added names to kick messages.
  
• Added a way nicer kick message. [image 1]
  
• last guard gets excluded from stack shooting
  
• added !warnings [image 2]
  
• added zone support to detect armory
  
• added vent cells support
  
• Entering armory will turn you into a rebel
  
  
  
  

I've implemented an automatic (no staff involved) warning system that will punish you with teamlocks if you exceed the warning limit.

There are 3 warning levels you can fill up with warnings

1. minor or low warnings
   
2. average or normal warnings
   
3. major or high warnings
   

*these are only for guards

By doing any of these actions you will increase your warning level.

• Damaging fellow guards
  
• Gun planting guns
  
• Shooting suicide bombers and kill a friendly
  
• Shooting in stacks
  
• Baiting
  
• Not claiming warden before 9:00
  
• Not claiming warden and giving everyone global freeday
  
• Spraying CT's to troll them
  
• Killing a CT
  
• Opening cells without warden
  

The warnings will decay over time and will let you know at the end of the rounds every now and then.



If you have suggestions on what else to warn people for, let me know!


Other changelog
-Added bait detection. (still work in progress)
-When last guard window gets ignored, force last guard to be denied.
-Added slapping to warnings
-Removed STAMM and replaced it with my own playtime tracking stats
-Added sm_playtime
-last guard will ignore low playtime.
-freeze time (fz[x]) removes 1 second to get more accurate times
-added website removal in names



-added lcrh[] (last crouch)
-hns no longer removes suicide bomb.
-added new player notifications
-added 2 new settings in !settings to control the new player notifications
-Force new player info (!settings) forces you to see the new info messages.
-Disable new player info (!settings) allows you to disable the messages.
-updated automated lock messages for staff, "we suggest a lock on x"