[GUIDE] Warning Shots 2.0

[MusicManiac]

Welcome to the guide, the whole purpose of which is to explain warning shots, and how they work.

Last update: 16/09/2021
Last check on validity : 16/09/2021


Content table (click them to go to the section)

1. Why was warning shot added?
   
2. Warning shot rule
   • Warning shots with deagle
     
3. General warning shots scheme
   
4. List of examples with "freeze" command in place
   
5. List of examples with "face X" command in place
   
6. List of examples with "jumping is restricted" command in place
   
7. List of examples with trap commands in place
   
8. List of examples that don't fall into higher mentioned categories
   
9. Afterword and contributors
   

1. Why was warning shot added?

Lemme start with a small history course that will make you understand why warning shot was implemented. Before warning shot rule, CT's were allowed to instakill anyone who was not following command even in the slightest manner. Let me describe for what you could get instakilled:

• Told to face north, and you unfaced towards east for a quick look.
  
• Told to freeze, and you moved half a step, not even towards CT/vent.
  
• Restricted jumping, and you jump, while being in a stack.
  
• Have gun on your back for more than 3-4 sec. You can even not realize it's there, doesn't matter.
  
• Told to crouch-walk to some place, and you accidentally hit your "jump" button.
  
• Going IN the marker when told to go TO the maker and freeze.
  

So obviously, there were a lot of kills for minor things. So in an attempt to make the server less harsh towards new players as well as just to prevent kills on some T's who accidentally hit a wrong button, looked the other way, or something else, the warning shot rule was implemented.


2. Warning shot rule

Give warning shots to non-threatening actions of prisoners. (A warning shot should not deal more than ~34 damage)

• non-threatening examples
  • Slight movement when told to freeze
    
  • Slight head movement when told to face x
    
  • 1 step too much forward when told to freeze on the line.
    
  • Accidental stand up in crouch walking
    
  • Strafing a bit out of line when following warden (bhop)
    
• threatening examples
  • Bhopping around in a stack when told to freeze
    
  • Strafing too much out of line when following the warden
    

First things first: dealt damage. Should not exceed roughly 34 hp. It means, if you warning shot someone for 37, it's bearable, but if you go for 40 hp - that's already 20% more dmg than you should have done, and 20% is a lot. Best way to avoid that - shooting in legs, and not using anything that deals huge amounts of damage (deagle, shotguns, sniper rifles).

Second: you only need to give ONE warning shot. If a T keeps doing the same thing for which he received first warning shot, you are not FORCED to give another warning shot. You are free to head-shot the guy. However, if the same T gets their first warning shot for one thing, and then killed for another, because "he got warning shot already", it's not how the rule works. Example: T's told to freeze 10 sec ago, T named XYZ runs a little bit out of their cell, gets warning shot, so he freezes. Warden restricts jumping, XYZ jumps after 5 seconds. You are not allowed to instakill him, because you already gave him a warning shot, it's 2 different orders that he received warning shots for.


2.1. Warning shots with deagle

You can hear a lot of players on server ranting about "don't warning shot with deagle". You CAN warning shot with deagle if you're confident with your aim, shot with deagle in foot deals like 25 dmg. However, if you miss, and land your shot in body and deal 56 or so instead - get ready to pay for that, most probably in form of slaying yourself :D Also, staff will need to !damagelog player who complained on a warning shot for this big amount of damage, this is additional work for staff, and keeping server floating is not easy task even without some random guy giving warning shots with deagle, so they will not appreciate this phenomenon.


3. General warning shots scheme
Please, remember, this is general scheme, apply some common sense on top, and you'll be fine ;P

Powered by https://www.draw.io/


4. List of examples with "freeze" command in place

1. Warning shot for
   
   1. Slight movement out of stack not towards CT/vent/gun, that is closeby.
      
   2. Taking 1 step out of cells and freezing or going back to YOUR cell when told to freeze in cells.
      
2. No warning shot for
   
   1. Slight movement out of stack towards CT/vent/gun, that is closeby
      
   2. Cheating in a game (starting to play game before told, failing to freeze when told to, after someone finished)
      
   3. Slight movement out of stack, while having a gun, considered as trying to get better shot at CT's.
      
   4. Trying to run away (surprising, isn't it?)
      
   5. Bhoping around stack of Ts.
      
   6. Cell-swap
      

5. List of examples with "face X" command in place

1. Warning shot for
   
   1. Unfacing X while having no gun in arms
      
   2. Unfacing X while no CT's are near knife-range
      
2. No warning shot for
   
   1. Unfacing X while having gun in arms or pulling gun out
      
   2. Unfacing X when it can be classified as cheating, examples:
      
      1. Unfacing X to see on whom shot will get landed when playing shoot or don't shoot,
         
      2. Unfacing X to see how far your opponent got in time climb
         
      3. Unfacing your opponent in shot-4-shot, if told to face opponent at all times.
         
      4. After someone won in game and needs to crouch-walk under T's he wants to kill, unfacing X to see if winner chooses you to die.
         
   3. Unfacing X when CT is really close (for example, warden healing Ts)
      
   4. Unfacing X and knifing CT, while being frozen
      
   5. Unfacing X and looking towards CT, while having bomb in arms (power-toss threat, plus checking out if blowing up CT's in usual way is good)
      

6. List of examples with "jumping is restricted" command in place

1. Warning shot for
   
   1. Jumping in stack while being frozen, not trying to reach CT's or buttons
      
   2. Accidentally jumping while going to marker
      
   3. B-hopping towards marker, while not shortening distance between you and CT closer, that you should be.
      
2. No warning shot for
   
   1. Cheating in the game, examples:
      
      1. Jumping in colors game.
         
      2. Starting playing climb/bhop by taking jump (-s)
         
      3. Jumping on first reaction / last reaction
         
   2. B-hoping towards marker, and as a result being closer to CT/corners/exits that allow to run away, than you supposed to be
      
   3. Jumping while having scout in hands (doesn't matter if guns restricted or not)
      
   4. Jumping trying to press or pressing "threatening buttons" (what's threatening button is explained on .png higher)
      

7. List of examples with trap commands in place
Generally, CT's dont need to give warning shots for trap commands, with few exceptions, such as: (yes, some of there has been mentioned before)

1. Going IN the marker when told to go TO the marker and freeze.
   
2. Taking 1 step out of cells when leaving cells is restricted
   
3. Facing X when facing X is restricted or unfacing X when told to face X at all times
   

8. List of examples that don't fall into higher mentioned categories

1. Warning shot for
   
   1. Having a gun for more than 2-3 seconds when guns are restricted. You don't need to call out T by name.
      
   2. Having a gun for more than 2-3 seconds when guns are not restricted and CT told prisoner XYZ to drop it. You need to call out T by name and you can't enforce additional rules such as "w/o passing it on or picking it back up again".
      
2. No warning shot for
   
   1. Pointing gun at CT when guns are restricted
      

9. Afterword and contributors

Code:

bind F9 "say If you were killed and believe you were supposed to be warning shot, please read this thread: clwo.eu/thread-3423.html"
bind F8 "say You were warning shot for not following warden commands"

Thanks for reading, thread will be updated, so be sure to check it out regularly, changelog will be below.

Contributors:

• Author: MusicManiac 4Head
  
• People (actually it's 1 person) who helped me to fix rule-wise mistakes (actually it were 3 mistakes) in initial post: TheDilShawn. Not even sure he should be in contributors Kappa
  
• Other staff members who helped to confirm this post is rule-wise correct: SourceCode, C.C., Sharc, Square Play'n, Ya Grill Anne PogChamp
  
• People, who helped with adding examples: none yet BibleThump
  
• Separate thx to Jay (aka Nightmare) for his old thread. SMOrc
  
• Another thx to Square Play'n for fixing grammar mistakes. LUL
  

[MusicManiac]

Changelog:

16/09/2021
Added:
8. List of examples that don't fall into higher mentioned categories

• Having a gun for more than 2-3 seconds when guns are restricted. You don't need to call out T by name.
  
• Having a gun for more than 2-3 seconds when guns are not restricted and CT told prisoner XYZ to drop it. You need to call out T by name and you can't enforce additional rules such as "w/o passing it on or picking it back up again".
  

[TeamKiller]

I like the guide. Sorry I didnt helped, I am sick a lot, and its hard to focus. But it end up nicely, and helpful.
Thanks

[XeLa]

Can i ask, If a warning shot is given that results in a t dying within a game, eg, the t is shot midair and their strafe is ruined and forces them to either fall to their death or hit an obstacle that may kill them. This happened to me on minecraft party, and on lava climb hot lava was on. I did take 3 seconds to get ready for the jump, but as i left the ground, i got warningshot and slowed in midair and fell to my death. I contacted staff in saying that i was freekilled but no one was really sure.

[Anne]

Can i ask, If a warning shot is given that results in a t dying within a game, eg, the t is shot midair and their strafe is ruined and forces them to either fall to their death or hit an obstacle that may kill them. This happened to me on minecraft party, and on lava climb hot lava was on. I did take 3 seconds to get ready for the jump, but as i left the ground, i got warningshot and slowed in  midair and fell to my death. I contacted staff in saying that i was freekilled but no one was really sure.

It is situational. If you have been delaying for a long ass time, the warningshot was really necessary to keep the game going. If you only got 3 seconds to take your strafing jump (strafing meanwhile to prepare for the jump) then in all honesty I would respawn you if you were ws mid air and tell the CT not to slay. 

Why? Because we are not cruel. We hand out ws to make the game go faster, to show you do sth wrong. In the first you did: big delay. In the second you didn’t: strafing to make your jump, barely delay.

[MusicManiac]

Can someone explain to me how this is not threatening? If he would run half second more he could have zeussed me, for example?
Timemark is 2:25, since embedded vids dont properly do timemarks
https://youtu.be/8Tnh4UOfTYo?t=145

[Anne]

Can someone explain to me how this is not threatening? If he would run half second more he could have zeussed me, for example?
Timemark is 2:25, since embedded vids dont properly do timemarks  
https://youtu.be/8Tnh4UOfTYo?t=145

Hey Music

Thank you for providing a video, so that we can all see what happened in detail. Answering your question on the other hand is a topic to discuss. 
Command was to shift walk follow warden, which sugar did, but stopped doing so for a few steps. 
You could say he rushed you, but in my opinion he did not. He took about 1-2 steps not shift walking, which does not imply rushing unless you were closer, which you weren't.
Therefore, that action is not threatening. But as said, it's a topic to discuss ... In my opinion, if he took like 1-3 more steps non shift walking, you being at that position would make it a threatening action.

Hope you understand my view and please do answer if you have more questions or arguments to bring :) 

Guardian Anne

[MusicManiac]

Command was to shift walk follow warden, which sugar did, but stopped doing so for a few steps. 
You could say he rushed you, but in my opinion he did not. He took about 1-2 steps not shift walking, which does not imply rushing unless you were closer, which you weren't.
Therefore, that action is not threatening. But as said, it's a topic to discuss ... In my opinion, if he took like 1-3 more steps non shift walking, you being at that position would make it a threatening action.

There is no definition of rushing. Not shiftwalking = rushing/running. He was not shiftwalking - he was rushing/running. It was already threatening, if he would keep on rushing he would literally take 1 bhop and knife me or zeuss me without bhopping.

Why do I need to wait for him to kill me? This is bullshit, IMO. Also, it w as not accident, he did the same thing on the previous angle?

[Harmless Telly Tubby]

Don't know if it matters, but all of us in the front were warning shot a few seconds earlier for running. So if your point is he should have been warning shot, he was

[MusicManiac]

Don't know if it matters, but all of us in the front were warning shot a few seconds earlier for running. So if your point is he should have been warning shot, he was

You can also see that on a vid. But even without warning shot, my point is about the thing that it's a threatening action.

[Sugar]

Don't know if it matters, but all of us in the front were warning shot a few seconds earlier for running. So if your point is he should have been warning shot, he was

I actually wasn't warning shot by any CT and I wouldn't consider that threatening at all as the distance between me and you was a 2x zeus range or further.

[Shankey]

In my opinion it is a freekill, as stated by sugar he didn't get warningshot and the range between you and him were maybe 3/4 times Zeus range (insta kill range). So not speaking about tagging him for 40 HP warningshot. And it just seems like you shot 1 bullet in the stack and instantly realised what you did since you didn't kill the rest. When there were 2 others who did the same. And as Anne stated before it is something where multiple opinions can be. It's situational. I think if this exact moment happened on the football field on potato or clouds you wouldn't have killed him maybe a warningshot. It was because they were in a tight corridor and it looks more threatening by slight movement.

[MusicManiac]

In my opinion it is a freekill, as stated by sugar he didn't get warningshot and the range between you and him were maybe 3/4 times Zeus range (insta kill range).

I actually wasn't warning shot by any CT and I wouldn't consider that threatening at all as the distance between me and you was a 2x zeus range or further.

I don't think you're familiar with actual zeuss range. I recently killed someone on JB on insane Zeuss range, I did not even realize it has that far range.

And it just seems like you shot 1 bullet in the stack and instantly realised what you did since you didn't kill the rest. When there were 2 others who did the same.

You can see me changing aim from their body/feet to his head. What I did not realize that others were running aswell. I've seen him running, I killed him. But whatever, if you say it's not threatening, it's not threatening. But it's still bullshit. He intentionally broke the order to get closer to CT.