Rules

1. General Rules

Disclaimer : LAN staffs/admins refer to the list posted on the website under “LAN administrator”. Shmaltz reserves the right to give out/take away the role as needed for the tournament to run as smoothly as possible. Any LAN staffs decision that would result in a grave consequence (a match forfeited or overturned, a player needing to be suspended, etc.) should be taken with the most amount of admins possible and ideally admins not benefiting directly from the decision.

1.1 LAN admins reserve the right to modify any rules as needed at any time as deemed necessary to the good continuation of the tournament. Changes to the rules will be posted on the website and relayed to the team captains on discord.

1.2 For any given game: The correct map must be played, the correct config must be used, and the match must be played on the LAN server.

1.3 If the server crashes within the first five minutes of a half, the half will be fully restarted. If the server crashes after the first five minutes of a half, the half will be restarted with the same score and the same amount of time remaining, rounded up to the nearest full minute. The score must be manually restored, and time remaining can be adjusted via server command. No player substitutions are allowed during this process. LAN staff need to be made aware as soon as possible if this happens.

1.4 The use of restricted areas on a map may result in player suspension and/or game/match forfeiture. Accessing an area via pixel walking, pixel walking and hanging in an area (such as harrington ladder), or an area that is only accessible via pixel walking is generally illegal. Please see Illegal Spots for examples of map areas that are considered illegal as well as a short video demonstrating illegal pixel walking. Basically everything that was illegal in KTP seasons will also be illegal on LAN and players coming back need to be made aware of new possible spots as ignorance will not be an excuse.

1.5 In the event of a tie, two five-minute halves of overtime should be played. These overtime rounds are to be played immediately after the match. Overtime rounds should continue until a winner can be established.The overtime configs have the normal config name with _ot added to the end. For example: ktp_harrington_ot.cfg. Failure to complete overtime rounds will result in a loss for both teams. LAN staff need to be made aware as soon as possible if this happens.

1.7 A seating schedule has been made to try to minimize change of computer, fairness, etc. LAN staff may need to modify the chart to accommodate for various delays. Their decision is final. Disappointment over change in the seating arrangement is normal but real complaints will be met with 69 other grown adults quietly laughing at you.

2. Cheating, penalties and disputes

2.1 LAN admins reserve the right to assign suspensions and forfeits, as necessary for failure to follow the rules or code of conduct. This decision should be taken with the most amount of admins possible and ideally admins not benefiting directly from the decision.

2.2 LAN admins reserve the right to investigate suspicious players in order to maintain competitive integrity. Demos files can be pulled at random. Computers and peripherals can be tested for integrity by LAN admins. Failure to provide requested evidence may result in a team forfeit loss or player suspension.

2.3 Cheating is not allowed in any form. Players found to be cheating will be suspended from the LAN and any match won that featured the cheating player will be overturned.

2.4 Cheating includes but is not limited to: the use of any program that aids in the visual location of players on a map, recoil control, target acquisition, illegally modifying game files, enabling snaptap and other software alike, null binds, monitor/software xhairs, mouseaccel program, etc.

2.5 Only default game files may be used unless explicitly approved or provided by LAN staff. The list is the same as the one used in KTP. The use of approved scoreboard modifiers, HLTV models and modifications to ClientScheme.res and TrackerScheme.res is allowed. The use of a custom crosshair is allowed for all weapons except the sniper rifle.

2.6 Once a game has gone live the use of spectator is cheating. Spec hopping is cheating with a caveat. The sole exception to the spec hop rule is if a player has been killed at the moment of a full map capture or a player is stuck in terrain then Spec hopping IS allowed to join your team during the spawn wave.

3. Player Rules

3.1 All players must abide by the file integrity checker and cvar checker.

3.2 All players must record one in-game POV demo for each half of every game, take an in-game screenshot of the scoreboard at the end of each half and not leave games early.

3.3 Player boosting IS ALLOWED so as long as the area being boosted into is an area that is accessible by a single player without boosting.

3.4 The use of voice commands or hand signals in game for anything other than communication between team mates is not allowed. Excessive voice negging opponents or abusing voice commands is not allowed. Violation of this rule must be submitted to LAN admins in the same manner as a dispute with a POV demo and timestamps.

3.5 Players are prohibited from binding any action in conjunction with +attack. Players may not bind +attack or +duck to mwheelup or mwheeldown (or any other macroed key) to accelerate shooting weapons faster than they are intended to be or to bypass stamina restrictions.

3.6 Players may not script to automate player attacking, player movement, or to gain an unfair advantage.

3.7 Players may not use hand signals, voice commands, or bind any cvar toggles in conjunction with +sprint, +crouch, +move, +fire, +jump or any other key or command in an attempt to make their player model harder to hit. Including binding crouch to scrollwheel/binding multiple buttons to +duck in order to achieve the same effect as binding crouch to scrollwheel.

3.8 Players may not spawn weapons to bypass class limitation, grenade glitch, map exploit, pixel walk, or wall glitch. All of the above are considered cheating.

4. Captain Rules

4.1 All captains must modify their in-game client scheme to produce more legible screenshots for end match score submission.

4.2 All captains must take one in-game rcon status screenshot per game.

4.3 Upon conclusion of a match, the winning captain is to report the final score and screenshots to a dedicated shared drive.

5. Pauses

5.1 Each team is allowed one pause of 2 minutes per half. Unused pauses do not carry over between halves.

5.2 A pause may only be initiated immediately after a cap out.

5.3 Only the team captain is permitted to initiate the pause.

Exception – Technical Issues

5.4 If a player crashes or experiences a critical issue, a pause may be called immediately, even if the team has already used its allotted pause for the half. In the event the team captain is the affected player, any remaining team member is authorized to call the pause. LAN staff need to be made aware as soon as possible if this happens.

5.5 Unauthorized Pause Penalties

Failure to follow the above conditions will result in the following penalties:

First Offense : the other team gets the equivalent points of a cap out
Second Offense: Immediate match forfeiture