Hi!

To boost last guard win chances (and mostly because I was bored and wanted to incorporate turrets into jailbreak)

You can purchase the upgrade in the upgrade store.



Once claiming last guard it will spawn turrets



kills made by turrets will be accredited to the last guard by assists.



NOTE: Kills on trapped prisoners by turrets are accepted

You can also buy the boost which doubles the HP and damage.

Default turret: 14.45 damage per shot and 880 HP
Boosted turret: 28.9 damage per shot and 1320 HP




Examples:

Turrets on Jungle.



Turrets on Spy.




Just to annoy everyone, every round there will be a random turret placed in the map targeting everyone.




Other fixes

• Pooping no longer pushes people off (only when close to other players)
  
• Cell escapers are now limited to 2 people per round
  

Enjoy

The Giveaway:

We have a small giveaway to get things started! Ill call this the "Rigged AF" giveaway, because why not! - I've managed to find a way of loading a lot of FIFA Points (66k to be precise), and I have a cool way to do a giveaway. I'm not really interested in FIFA itself, but opening packs etc is always fun. So, with rumors of TOTY players (best players at the highest rating) coming out, I'll be looking to open a lot of packs around that time. For this, I will spin 1 wheel with everyone's names on it (who has entered the giveaway), spin a 2nd wheel to see the potential prize they will win, and then spin a 3rd wheel to see the top rated player that comes out. (Due to gold packs being opened, the minimum it can be is 75 or higher rated. If it lands on that number, e.g. it lands on "84 or higher" and the top card is 84 rated, it will count as a win). There are a limited number of prizes available:

- 5 x $10 Steam Gift Cards (1/50 chance to get)
- 20 x CSGO Case Key (3/50 chance to get)
- 40 x Random Steam Game Key (15/50 chance to get)
- 100 x P250 Sand Dunes (30/50 chance to get)

There will be a 1/50 chance of getting a 2x Prize, which the wheel will re-spin, and the prize will be doubled (as long as you win the pack pull).

This giveaway will be streamed live on Twitch. I'm unsure on a date & time, but it will be around the time that TOTY is released (if it is, which is expected between 7th - 31st January 2019). A further post will be made about this.

The Main 5v5 Event:

This event will be ran by signing up your team before the event has started. Your captain will be asked to choose a name, and will remain the captain during the whole of the event.

The teams will be made & named, and will be randomized in a pool to be placed into groups. You will play each team twice, with each team picking 1 map they want to play. They can be played back-to-back or separated, but it is ideal to complete all games ASAP to not fall behind in the deadline. The games will be scored from Wins/Loss against the other teams in the group, and then by Round Difference if 2 teams have the same W/L. If by some miracle, by the end of all the games, there are 2 teams with the same score, they will play a BO1 veto'd game to decide the winner / KO brackets.

Top 2 teams will qualify through to the KO round and the structure will vary dependent on the amount of teams. It will be placed out of a team that has a better win against a team lower in score. This will be sorted by the Tournament Director(s).

Once in the KO stages, it will be a BO3 veto'd game, and if you lose, you will be knocked out of the tournament. The games will continue until there is an overall winning team.

The Double-KO 1v1 Event:

This event will have every round played as a BO3. One AK/M4 based map, one AWP based map & 1 USP / Pistol based map in that order. You can see the maps below that are being played. Registrants will be placed in a list & then fully randomized to build the brackets. There may be a few "Bye" rounds and some players may need to play an additional game. If you lose a round in the winners bracket, you will drop down into a Losers bracket, where you will have a lifeline to make it to the final round, but will need to win all remaining games to get there. If you lose a round in the Losers bracket, you will be knocked out of the tournament.

The games will be played until an overall winner is picked.

The Final Event:

There will be a final event which will run on the Sunday 27th January 2018 @ 6PM UK time. The event will be a 1v1 server, which will have multiple maps on. The amount of rounds per map will depend on the total amount of arenas +5 (So, if there is 30 players, there is 15 arenas, plus 5 to this will make 20 rounds). Top 4 arenas will get points (1 Point for arena 4, 2 Points for arena 3, 3 points for arena 2, 5 Points for arena 1). However, the 2 players in the bottom arena will be removed from the event. The main objective is to get as many points as you can!

Maps:

5v5:
The 5v5 event will feature the current active duty pool. If they change before the applications close, then this list will be updated to the active duty map(s). This includes:

- Inferno
- Train
- Mirage
- Nuke
- Overpass
- Cache
- Dust 2

1v1:
The 1v1 event will feature the following maps:

- aim_map
- awp_orange
- usps_arena_1vs1

They will be self-hosted by us and automatically downloaded (with different filenames) to skip any bugs / issues with the maps.

Prizes:

Prizes for this event is as follows (Please note that they can be updated / changed at any moment):

5v5:
1st Place: 20 USD Steam Wallet Voucher (Each), JB Crown Icon (Chat) (Each), 1 x PartyCrate & 5 x LootPackage & 10 x FreeDays (each)
2nd Place: 5 USD Steam Wallet Voucher (Each), 5 x LootPackage & 1 x Freeday (each)

1v1:
1st Place: 30 USD Steam Wallet Voucher
2nd Place: 10 USD Steam Wallet Voucher

Final Event:
1st Place: 20 USD Steam Wallet Voucher
2nd Place: 10 USD Steam Wallet Voucher
3rd Place: 5 USD Steam Wallet Voucher

EAC (Easy eSports) Anti-Cheat:

We've updated the Anti-Cheat system this time, as we do each time, to the best system possible. We are now using EAC's Client-Side system to be run for each game. You can download Easy Anti-Cheat from the steam store (for free) here - Run this program first, and then open CS:GO, and then join the server as soon as you get the details, for the anti-cheat to work. NOTE: If you don't have the anti-cheat running, you will be removed from the session until it runs.

Please ensure that you only have EAC (Easy eSports) running only. If you have FACEIT-AC / ESEA running at the same time, this may cause conflicts and possibly kick you from the server / crash your game.

Streaming:

The games will be available on the CLWO Twitch Channel (here). Be sure to follow in-case you miss any of the games!

GOTV will be available for players to spectate (and will hopefully be set-up so the casters will have full camera control too at relevant delays)

Applications / Registration:

***Registration is now closed!***

5v5 Event: Click Here
1v1 Event: Click Here
Final Event: Click Here
Giveaway: Click Here

Casters / Streamers: Click Here

Groups / Bracket:

5v5 Group 1: Click Here
5v5 Group 2: Click Here
5v5 Playoffs: Click Here

1v1 Bracket: Click Here

Questions / Comments:

If you have any questions or comments for this event, please don't hesitate to PM MrGibbyGibson

Good luck to all players & teams!

Do you want another TTT meeting? Of course you do. Anybody can come, you don't have to be a staff member. If you are a staff member who can't come, please do let me know.

I hope I have the time zones correct.

In the last patch you can enable positional VOIP.

Meaning you will hear the voicechat from the players location.


In jailbreak you can locate talkative rebellers with this (you can hear them inside vents)
In TTT you can locate talkative traitors.

Etc...

Enjoy.

iNilo

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

Last update: 23/9/18
Last check on validity : 09/08/19

<a name="index"></a>
Content table (click them to go to the section)

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

<a name="1"></a>
1. Why was warning shot added?<a href="#index"></a>

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.

<a name="2"></a>
2. Warning shot rule<a href="#index"></a>

Quote: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.

<a name="2.1"></a>
2.1. Warning shots with deagle<a href="#index"></a>

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.

<a name="3"></a>
3. General warning shots scheme<a href="#index"></a>
Please, remember, this is general scheme, apply some common sense on top, and you'll be fine ;P

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

<a name="4"></a>
4. List of examples with "freeze" command in place<a href="#index"></a>

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
      

<a name="5"></a>
5. List of examples with "face X" command in place<a href="#index"></a>

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's 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)
      

<a name="6"></a>
6. List of examples with "jumping is restricted" command in place<a href="#index"></a>

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)
      

<a name="7"></a>
7. List of examples with trap commands in place<a href="#index"></a>
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
   

<a name="8"></a>
8. List of examples that don't fall into higher mentioned categories<a href="#index"></a>

1. Warning shot for
   
   1. Nothing here yet
      
2. No warning shot for
   
   1. Pointing gun at CT when guns are restricted OR CT asked you to drop your gun without picking it up or passing it on again
      

<a name="9"></a>
9. Afterword and contributors<a href="#index"></a>


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