Salvation - Season 3

Tournament system

Playoffs system will be announced after signups close
Play-offs will be single elimination
Third place deciders will be played to help seed players next season.
The system will run with a fixed schedule (sunday 18:30 / 20:00 / 21.30 CET)
If a team can not play at the scheduled time, they are at the mercy of their opponents. The game may be rescheduled to another time or day (before next sunday’s games). Opponents may also take the walkover if they can not agree on a new time. We do encourage flexibility and sportsmanship in this regard.
Playoff Sundays will have a fluid scheduled and game order will be announced some time after group games are over.
To seperate team with equal points following order will be applied:

Team Restrictions

Player limit of 5 players per team in division 1 and 6 players in division 2.
Player swaplimit: There will be no player swap limit this season. However if a player is kicked out from a team he will NOT return to the player pool. The player was kicked either because he was idle or missbehaved. If he is idle he won't get a second chance. If he missbehaved he is banned from this season. The swaplimit is basiclly the size of the free agent pool. But all swaps are to be approved by an admin
Teams can not add/change players once regular season is over
Players should use the nick they are registered with on the website
If any player goes inactive or is not able to play anymore, the captain can then request a swap with someone from the free agent list. With approval from a admin.
Div1 team can borrow a player from their own div2 team during the groupstage. The players will still remain on their original roster after the game. IF this occurs, admins will try to rearrange the schedule accordingly for div1 and div2 team.
Players picked for Division 1 is not allowed to play with their div2 teams

Picking Order for division 1

Seed Group 1: Captain 1 and 2
Seed Group 2: Captain 3 and 4
Seed Group 3: Captain 5 and 6
Seed Group 4: Captain 7 and 8

Round 1: Seed Group: 4, 3, 2, 1
Round 2: Seed Group: 3, 2, 1, 4
Round 3: Seed Group: 2, 1, 4, 3
Round 4: Seed Group: 1, 4, 3, 2

In Round 1 the lower seeded captain will pick before the higher seeded one in the Seed Group. Rounds 2 and 4 the picking order is reversed, so the higher seeded captain picks first within that Seed Group. In division 2 teams are picked according to the ktx captains mode system, where the captain who picks first in the first round picks first in the last round.

Maps and match procedure

Map pool

Claustrophobolis (dm2)
The Abandoned Base (dm3)
Castle of the Damned (e1m2)

Maps to win

Group Stage: 2 (BO3)
Quarter Final: 3 (BO5)
Semi Final: 3 (BO5)
Bronze game: 2 (BO3)
Grand Final: 3 (BO5)

Match procedure

In a BO3: First map pick is decided by coin toss (/cmd rnd Team1 Team2). The winner of the coin toss decides who picks first.
The team who didn't pick the first map picks the second map, which can't be the same map as the first.
If a decider map is needed the map that has not been played yet will be the decider. No map can be played more than once in a BO3.
It is suggested that you wait no longer than 5 minutes between each map.
In a BO5: First map pick is decided by coin toss (/cmd rnd Team1 Team2). The winner of the coin toss decides who picks first. Second map by the other team (can not be the same map as first). Third map will the remaining map of TB3 that has not been played yet. Fourth map will be picked by the team behind on mapwins. Fifth map by the other team (who was up 2-1 before the fourth map).

Match Reporting

In order for a match to be valid you'll need to have screenshots and match log from each played map.
match_auto_logconsole "2"
match_auto_sshot "1"
match_format_4on4 "4on4/%Y-%m-%d_%b_%M"
log_dir "qw/matchinfo"
sshot_dir "qw/matchinfo"

Scores and ranking

Points in Group Stage

2-0 win awards 3 points
2-1 win awards 2 points
1-2 loss awards 1 points
0-2 loss awards 0 points
Walkover is worth 3 points

Walkover and VOID

If the match isn't played within the scheduled 1h30min the team causing the delay will be giving a WO (2-0 victory) until played on Catch Up Day. If both teams are the cause of delay the match will be rendered VOID (0-0) until the match is played on Catch Up Day. If the game isn't played on Catch Up Day the WO/VOID rendering of the match will stay in place. This might sound harsh but WILL be enforced to show respect to the other teams and players waiting.
Example 1: If Team 1 has been delaying a game to a score of 1-1 when the scheduled time runs out, Team 2 will be given a WO victory (2-0). If both teams agree on continuing the game on Catch Up Day the game will resume with the score of 1-1. The Catch Up Day match can be started after 20.00 CET but has to be finished before 22.00 CET.
Example 2: If the game was delayed and both teams agreed on playing it on Catch Up Day but one team fails to field enough players, a WO victory (2-0) will be granted the other team. If the team NOT delaying the game are unsure if they can play on Catch Up Day, they can disagree to reschedule it and keep their WO (2-0) victory.

Clients and modifications

Allowed clients

ezQuake 1.9.3 stable and above + jquake fork
Fodquake 0.3
FTE 3343
Exceptions can be granted due to problems

Allowed modifications

Required ruleset: smackdown (ezQuake), nqr (FTE), eql (Fodquake). How? disconnect, ruleset smackdown, reconnect , allow_scripts 0 works without reconnecting
For routing, Qizmo 2.91 is allowed, prefered method is however the new QWfwd proxy
Rulesets and noscripting are strict. All games should be started by checking that all models are ok, scripts are turned off and that players use an allowed client. If a players disobeys the rules regarding the just stated it will result in a default loss (map)
The user's client needs to give a clean response to f_modified with ruleset smackdown
Using disallowed clients/proxies will lead to a direct loss of the map. Continious usage will result in more drastic consequenses
A clean respone looks like: smackdown-msfi

Scripting and cheats

Allowed

cl_fakeshaft (only mentioned here as it used to be forbidden)

Banned

movementscripts (cl_idrive must be turned off)
kfjump
custom rocketjump scripts
Any other kind of movement scripts
Teamoverlay
Automated teamsays
Different enemy skins
Skin changing depending on health/armour/weapon
Custom models not allowed by f_modified
Hacked clients (recompiled quake-executables)
Coaching, (timing quad and other items, relaying enemy positions and giving teamplay suggestions)
Nospecs must be on to prevent ghosting

Warnings and disqualification

Two warnings will result in a disqualification/removing from the tournament, there are no exceptions.
To retain order in the tournament and prevent teams from cheating or behaving badly we may issue warnings or bans to teams if they misbehave in some way.
If you are inactive during the tournament you will be kicked and replaced with a free agent

Other offences

Having one or several players intentionally drop from server during a game without replacing them
Playing in more than one team, or playing under someone else's name in another team (mercing)
Fakenicking

Most of these cases result in a ban of atleast 1 season.

Servers and settings

Server Settings

Timelimit: 20 minutes
Overtime: 5 minutes if match is a draw
Deathmatch mode: 1
Teamplay mode: 2
Spawn mode: Either KTX/KTX2 Respawns or KTPro Spawn is to be selected
Powerups: ON
Discharge: ON
FPS: A max of 77 fps is allowed.
KFjump: Toggled OFF (command = tkfjump)
Airstep: OFF
Jawnmode: OFF
Fallbunny: ON (if server allows)
Teamoverlay: OFF

These should be the basic 4on4 settings on all modern servers, but make sure to check.

Server and minping

Mutual agreement between captains is first priority. If captains are not able to agree on a server go by the following steps to find most suitable servers:
Add the ping from all your players together and divide with 4. If a player has more than 65ms to the server his ping will count as 65. If the average pings between the two teams are LESS than 15 ms apart it is acceptable. If it is higher try qizmos and QWfwd to lower your ping.
If packetloss is 2% or greater you should considering finding another server.
If teams can’t agree or find a suitable server contact an admin. Admin will try and help find a good server. If necessary admin will decide server for the game. Admins decision is final.

Spectators

Nospecs must be on to prevent ghosting

Server problems

The current map should be played to the end, no matter the servers condition
Admins will decide if a map should be replayed on another server

If a server gives 2 or more spikes that result in 100% packetloss for all players for more than 10 seconds, the map should be replayed on another server if the teams does not agree to the score/situation

The Salvation rules are based on the rules of EQL. Admins can change/fix rules if problems should occur

Scheduled date	Team 1		Team 2	Division/group	Score		C	D



Feb 17, 21:30	Carapace's Primary	vs	Milton's Primary	Division 1 - Playoffs	1 - 3	9
Feb 17, 20:00	Ganon's Secondary	vs	ParadokS' Secondary	Division 2 - Playoffs	3 - 1	5
Feb 10, 20:30	Rikoll's Primary	vs	Milton's Primary	Division 1 - Playoffs	1 - 3	8
Feb 10, 20:30	ParadokS' Secondary	vs	Milton's Secondary	Division 2 - Playoffs	3 - 2	5
Feb 10, 18:30	Carapace's Primary	vs	Zero's Primary	Division 1 - Playoffs	3 - 1	9
Feb 10, 18:30	Ganon's Secondary	vs	Rikoll's Secondary	Division 2 - Playoffs	3 - 0	4
Feb 03, 20:30	Milton's Primary	vs	ParadokS' Primary	Division 1 - Playoffs	3 - 0	2
Feb 03, 20:30	Rikoll's Primary	vs	kingpin's Primary	Division 1 - Playoffs	3 - 0	8
Feb 03, 20:30	Milton's Secondary	vs	Carapace's Secondary	Division 2 - Playoffs	3 - 0	4
Feb 03, 20:30	ParadokS' Secondary	vs	kingpin's Secondary	Division 2 - Playoffs	3 - 0	9