Rules
These are the rules for the Jedi Knight:Jedi Academy Team Deathmatch Ladder. We make every effort to ensure the rules are complete and up to date but this may not always be the case. You should also check the Rules & Information and News for additions, exceptions and modifications that may apply. All players must meet the requirements listed in the Rules & Information at the time the match is scheduled to begin. The rules are a guideline and the decisions by admins may differ from them depending on the circumstances. If you have any questions about the rules, please write a support ticket.
- 1. Ladder Rules
- 1.1. Challenging
- 1.2. No show
- 1.3. Several squads (sub-teams) per team in one ladder
- 1.4. Agreements
- 2. Match Media
- 2.1. Screenshots
- 2.1.1. Scoretables
- 2.1.2. RCON status
- 2.2. Replays
- 3. Settings
- 3.1. Server settings
- 3.1.1. Configs
- 3.1.1.1. Other settings
- 3.1.2. Modifications
- 3.2. Maps
- 3.2.1. TDM
- 3.3. Client settings
- 3.3.1. Saber settings
- 3.3.2. Graphic tools
- 4. Match Rules
- 4.1. Game preparations
- 4.1.1. Game version
- 4.1.2. Nickname
- 4.1.3. Choice of server
- 4.1.4. Checking the server settings
- 4.1.5. Warm Up
- 4.1.6. Agreements
- 4.1.6.1. Spectators
- 4.2. Ingame
- 4.2.1. Choice of team
- 4.2.2. Exchanging players during a match
- 4.2.3. Player drops
- 4.2.4. Game Intermissions
- 4.3. Illegal Actions
- 4.3.1. Exploits / Bugusing
- 4.3.2. Modded Content
- 4.3.2.1. Usage of modified/new sabers
- 4.3.2.2. Usage of modified/new player models and skins
- 4.3.3. 3rd Party Software/Patches
- 4.3.4. Excessive avoidance of enemy contact
- 5. Penalty point catalogue
1. Ladder Rules
1.1. Challenging
In a ladder any participant may challenge any other. The challenge may be refused by the challenged if they choose. In ladders with more than 20 participants compulsory challenges are activated. If a participant is within 20 places above the challenging participants the refusal will be punished with one penalty point. If both participants are in the top 10 then the refusal will be punished with 2 penalty points.
A challenging participant from the newcomer pool (unranked) is considered as being at the bottom of the ladder, therefore the 20 participants ranked last in the ladder would be punished for rejecting a challenge.
Participants that have more than 5 outstanding challenges in a ladder, no matter if the matches are confirmed or not, may not take on any further challenges. This is scripted into the ESL system and cannot be changed.
1.2. No show
If your opponent does not show after 20 minutes, you must enter the result as your opponent did not appear in time. Do not enter a default win for yourself.
In Instant Challenger matches the no show time is 10 minutes.
1.3. Several squads (sub-teams) per team in one ladder
Any team may enter as many squads into any one ladder. However, only one squad can qualify for a premiership. A team is not allowed any more than one squad in a premiership.
During ladder play, no two squads from the same team are allowed to play each other.
1.4. Agreements
Certain agreements between participants are allowed to slightly differ from the ESL rules. Agreements that differ greatly from ESL rules are however not allowed. Please note that the ESL rules were made to ensure a fair match for all participants. You are not allowed to file a protest after the match if you think that the agreements made before the match in the end resulted in a disadvantage for your or your team.
Rules that can be changed with agreements are explicitly stated. Rules that do not explicitly state they can be changed by agreement, cannot have agreements made.
All arrangements between participants, made in addition to the ESL rules have to be written down in the match comments. The other participant has to confirm the arrangements also in the comments. To avoid abuse of the edit function, a third comment must be written.
Please also keep screenshots and/or logfiles of your arrangements. If you do not fulfil these requirements, any protests or supports concerning arrangements will be rejected.
The following rules may never be changed by arrangement: - Entering results for matches that have not been played - Allowing players to play that are barred because of penalty points, or are barred in the league due to a ban - Allowing players to play that in leagues with premium requirement that are barred for not having Premium
2. Match Media
All match media (screenshots, replays) must be kept for at least 14 days. Screenshots have to be uploaded within 24 hours after a match while replays have to be uploaded upon request of an admin. Failing to do so will result in a penalty. Manipulating match media is, of course, forbidden and will lead to severe penalties.
2.1. Screenshots
2.1.1. Scoretables
A screenshot of the score table, showing both players' scores and the round time, must be taken after every round.
2.1.2. RCON status
A status screenshot must show every single player that is connected to the server. The server hosting party is responsible for the availability of the screenshot. In case the match is played on a neutral server, both parties have to take care of getting in touch with the host to get the screenshot.
To create a status screenshot, proceed like this:
- Open your console using SHIFT-^
- Log in as server administrator with the appropriate RconPassword
- Type in the following commands:
- /rcon status
- /screenshot
Such a status screenshot has to be taken and uploaded for each of the following occasions:
- At the beginning of the match
- In case of a server/player change
- If a player reconnects
2.2. Replays
Replays of every round have to be recorded by at least one player per team.
3. Settings
3.1. Server settings
3.1.1. Configs
To provide you have as less work as possible, we have prepared some server configuration files that you have to edit (according to the commented lines in the configuration files) and put on your server.
Download the ESL server configuration package here.
3.1.1.1. Other settings
All settings that are not mentioned in the config files have to be set to their default value.
Exceptions are:
- map (has to be changed to the maps you play on)
- seta sv_privateClients
- seta g_allowVote
- seta logfile
- seta g_log
- seta g_logClientInfo
- seta g_statLog
- seta g_statLogFile
- seta g_logSync
and settings having to sole purpose of providing information such as:
- sets Clan
- sets URL
- sets E-Mail
- etc.
3.1.2. Modifications
There is no modification allowed. The server needs to be running on basejka.
3.2. Maps
3.2.1. TDM
In addition to all default ffa maps of the game, the following maps are allowed to be played on and need to be installed on the server:
3.3. Client settings
The following settings have to be set on the game client.
- cg_drawTimer 1
3.3.1. Saber settings
The following settings have to be set on the game client depending on the saber you play with.
If you play with a single lightsaber:
- saber1 kyle
If you play with two lightsabers:
- saber1 kyle
- saber2 kyle
If you play with a double-bladed lightsaber:
- saber1 dual_1
3.3.2. Graphic tools
Using graphic tools to gain an unfair advantage, for example making game textures translucent with a graphic card driver, are strictly forbidden. This is considered cheating.
4. Match Rules
4.1. Game preparations
Please resolve any problems that might occur before the match starts. Agreements between the teams/players have to be posted as match comments before the match starts.
4.1.1. Game version
Every match has to be played with the recent game version, which is 1.01.
4.1.2. Nickname
You have to play with a nickname that relates to your ESL nickname. Usage of colors and symbols for decoration, as well as the clan tag are allowed, however, one must be easily able to tell who you are.
4.1.3. Choice of server
Players should aim to find a server that gives both parties the same chances. Try to find a server with low and even pings. If you cannot decide on a server, the team on the left side of the match details may decide on the server for the first round, while the other may decide on the server for the second round.
4.1.4. Checking the server settings
With the beginning of the match you accept the settings the server has. If there is something wrong with the server settings, they have to be changed beforehand. If the server owner declines to change the server settings that can be found in the ESL server configuration files and the leagueinfo pages, you have to create a protest ticket.
4.1.5. Warm Up
The players are able to request a short warm up time of up to 5 minutes. Before each round starts, both parties have to state clearly that they are ready.
4.1.6. Agreements
The following settings can be altered if both parties agree:
- 2on2 Ladder
- Fraglimit: The fraglimit may be increased but never decreased.
- Timelimit: The timelimit may be increased but never decreased.
- TDM Ladder
- Timelimit: The timelimit may be increased but never decreased.
- Player count: The player count for both teams may be increased but needs to be even. For example you are allowed to play 4on4 but not 3on4.
4.1.6.1. Spectators
In case one party disagrees with having people spectating the match, every player who will not participate in the match has to leave the server before the match starts. The host has to guarantee that no one will join the server throughout the match.
4.2. Ingame
4.2.1. Choice of team
If you cannot agree on who plays as red/blue team, the team on the left side of the match details has to join the red team.
4.2.2. Exchanging players during a match
Each team may exchange one player for another one once during a round. The opponent has to be informed of this beforehand via ingame chat. The exchange itself may only be processed right after the player to be exchanged dies. If no spectators are allowed in the match, the opponent has to be informed of the exchange before the new player connects. The player to be exchanged has to disconnect from the server immediatly after the switch in this case.
4.2.3. Player drops
In case a player lags out or is unable to continue to play because of another understandable reason, the match has to be paused at once and a screenshot of the current score and time has to be made. After 5 minutes of waiting for that player, the match must continue. The team can let another player take the empty spot but only if they have not exchanged a player in that round yet. If this is not possible, the team may continue with 1 member less. If a team loses more than 1 player, it will count as leaving the match early (after the 5 minutes waiting time).
4.2.4. Game Intermissions
If the match gets interrupted, the points that have been scored so far will be rated. Take a screenshot if possible. The match will continue with the remaining time, only regarding the minutes. So if the interruption occured at a time of 9:12 with the max time of 15 minutes, you still have to play 6 minutes. For 9:00 also 6 minutes. For 8:59 7 minutes, etc.
4.3. Illegal Actions
4.3.1. Exploits / Bugusing
It is not allowed to exploit map bugs at any given time. This includes for example:
- Glitching through objects that should be unpassable [1]
- Exploiting a texture bug to gain a view through objects [2]
Killing a player by jumping on him while he's using an elevator is not considered a map bug.
4.3.2. Modded Content
It is generally forbidden to use any content that may alter gameplay or give you an advantage over your opponent. When in doubt whether this is the case for a specific file, a protest ticket has to be opened before the match starts.
4.3.2.1. Usage of modified/new sabers
It is not allowed to use sabers that do not comply with the ESL rules. Violation of this rule leads to severe penalties.
4.3.2.2. Usage of modified/new player models and skins
The only allowed models and skins are those you can choose by default when you select "Profile" in the main menu. Custom models created with the game's character creator are considered legit. All other models and skins, be it custom files or models/skins only accessible via cvar command, are not allowed to be used.
4.3.3. 3rd Party Software/Patches
The usage of any software which may alter gameplay or give you an advantage over your opponent is strictly forbidden. This includes for example ESPs, Wallhacks, using gamefiles altered with an unofficial patch and CVAR unlockers. Violations to this rule are considered cheating.
4.3.4. Excessive avoidance of enemy contact
It is not allowed to continuously bar the opponent from fragging by any form of action (e.g. running or jumping away, extreme passive play). Normal passive play remains unpunished, because this kind of gameplay generally allows the opponent to frag. An admin will, however, decide case specific after the available replays.
5. Penalty point catalogue
In general, a player can receive up to 6 penalty points, and a team up to 4 penalty points per match, unless a single violation has a higher punishment. A team is only punished once per violation, regardless of how many players. Where a player or team receives penalty points for multiple violations, the penalty points are added together.
| Rule violation | Number of penalty points |
|---|---|
| General | |
| No show | Team: 3; Player: 2 |
| Reject compulsory challenge | Normal: 1 Intense (top 10): 2 |
| Abort match | Player / Team: 4 |
| Use of ineligible player | |
| Inactive barrage | Player / Team: 3 |
| Barraged | Player / Team: 6 |
| Unregistered player | Player / Team: 3 |
| Missing Premium (where required) | Player / Team: 3 |
| Missing Trusted (where required) | Player / Team: 3 |
| Ringer/Faker | Player / Team: 6 |
| Playing with wrong gameaccount | Player / Team: 3 |
| Playing without a registered gameaccount | Player / Team: 3 |
| Unsportsmanlike behaviour | |
| Multiple/Fake accounts | Warning / 1-3 penalty points |
| Creating new teams | Warning / 4 penalty points / Ladder ban |
| Faking country/nationality | Warning / 1 / 2 / 3 penalty points |
| Kick player(s) from server | Player / Team: 4 |
| Deception | Player / Team: 1 - 4 |
| Fake result | Player / Team: 4 |
| Fake match media | Player / Team: 6 |
| Fake match | Player / Team: 6 |
| Cheating | Player: 12 / Team: 6 |
| Settings | |
|---|---|
| Usage of a non-allowed saber | Player: 3 / Team: 3 (if used by more than one player) |
| Match media | |
| Missing, incomplete scoreboard screenshot | Player / Team: 1 |
| Missing, incomplete rcon status screenshot | Player / Team: 1 (Server-hosting party. If neutral server both) |
| Missing requested demo | Player: 2 / Team: 2 |
| Unsportsmanlike behaviour | |
| Excessive avoidance of enemy contact | Player / Team: 4 |
| Excessive usage of special moves | Player / Team: 1 - 4 |
| Cheating/Exploiting | |
| Usage of map bugs | Player: 4 / Team: 4 |
| Usage of 3rd party software | Player: 12 / Team: 6 |
Copyright
All content appearing in this document is the property of Turtle Entertainment GmbH
or is being used with the owner's permission. Unauthorized distribution, duplication,
alteration or other use of the material contained in this document, including without
limitation any trademark image, drawing, text, likeness or photograph, may constitute a
violation of the laws of copyright and trademark and may be prosecuted under criminal
and/or civil law.
No part of the content of this document may be reproduced in any form or by any means
or stored in a database or retrieval system, except for personal use, without the
written permissions of Turtle Entertainment GmbH.
All content in this document is accurate to the best of our knowledge. Turtle
Entertainment GmbH assumes no liability for any error or omission. We reserve the right
to change content and files on our website at any time without prior notice or
notification.
Europe
Jedi Knight:Jedi Academy
Jedi Knight:Jedi Academy Team Deathmatch Ladder



