6 tournament. These changes will go into effect immediately. Below you've got a few instructions related to the new updates:
Also, emails that you have access to are required for you cal account. Our dispute email system emails both the leader and the disputed player so if neither one of you check your emails and do not notice you have been suspended until you recieve the suspension email or check you CAL page it is not our fault. Remember it is not the disputing teams responsiblity to let you know that you have been disputed or that your team was disputed.
As another reminder, it is the leader's/manager's responsibility to make sure that their player uploads the demo in time and/ or they do not have problems uploading just as much as it is the player's, if we have to start sending out suspensions for leader's as well then we will to stop the amount of no demo suspensions that we give out. For a piece of advice, every player on a team should stick around and check their emails for no less than 30 hours after their match is reported to make sure that they or someone else on their team has not been disputed. Ignorance once again is not an excuse.
Scroll down to take a look over the changes:
Screenshots that do not have smoke and net_graph 3 at the same time will be punished with a 8 week ban and overturn of the match just like there were no demos provided. Even if you do provide demos, if there are not screenshots with smoke and net_graph 3 on the same ss then the match will be overturned and you will be suspended. You must also start taking screenshots of smoke in clear view of the screen. If only an edge is shown of the smoke or the smoke is too far in the distance this will result in haivng no screenshots. We also still require 3 different screenshots showing smoke with net_graph 3 on, scoreboard with net_graph 3 on, and a ct and t model with net_graph 3 on. If any of these are missing net_graph 3 it will be looked at as no screenshots provided.
Demos must now be started prior to the screenshot round, failure to do so is going to result in a 2 week suspension for that player. Teams that are running rcon on the current server where the match is being played on are required to allow the other team to get their demos started prior to screenshot rounds as well as themselves. We MUST see the smokes being thrown by 1 or more person on each team and everyone doing the screenshot round.
Fastsprites are not allowed and are considered configging and will result in a 6 month suspension and match being overturned.

Both teams are required to take "status" screenshots while in the match during pistol round. To do so, drop your console. type status and hit enter. Then type snapshot and hit enter again, this saves a console screenshot showing the steamids of everyone playing. In order to prove that a player did not play this is what proof we need, we will no longer take Scoreboard screenshots as proof since players do not like to use their own aliases. Even if you use the correct alias and you are disputed but did not play a screenshot from your team must be provided. Teams that run the server are also required to take an additional screenshot of "rcon status" in console showing steamids and ip addresses. In order to do this screenshot you follow the same procedure as the "status" screenshot. This will help protect teams that play against others that like to use ringers. If we feel a team is disputing players to try and get the free win hoping we do not notice it was a player that did not play, they will be removed from the league for the remainder of the season.
16 bit smoke results in a 6 month suspension and overturn of the match that it happened in. A team is allowed 3 strikes in this case. This means that if 3 or more players on their team are caught using 16 bit smoke then their team will be removed for the remainder of the season. This means that the ingame leaders better make sure that their players are playing with 32 bit smoke.
Not recording two halves to your match seperately will result in a 1 week suspension. This means that you must start your demo for one half, stop it and then start another for the next half. Another infraction of this rule will double the suspension resulting in a 2 week suspension, then another infraction will result in a 4 week suspension, and so on, I think everyone understands the point. The only time you can record two halves in one demo is in overtime. All of overtime can be on its own demo.
Source: CAL