Loading group standings...
FACEIT Jedi Championship 2026 TDM - Group Stage
All Group Matches
Registered Participants
Rules
Faceit Standard Rules
Overview
Summary of default settings, required media, server selection and penalties.
Required client & server values
cg_fov— maximum value: 97cg_fovAspectAdjust— either0or1(affects TPR limits)- Third-person range (
cg_thirdPersonRange):- Max 100 when using JAMP client or Tayst/EternalJK with
cg_fovAspectAdjust 0 - Max 80 when using Tayst/EternalJK with
cg_fovAspectAdjust 1
- Max 100 when using JAMP client or Tayst/EternalJK with
- Faceit base servers:
sv_fps "30" - Client network:
cl_maxPackets "100",cl_timeNudge "0" - Rate: min
25000, max90000 - Screenshots and demos must be recorded for all matches.
1. General Rules
1.1 Agreements
By default, all matches are played on Faceit servers to provide balanced ping. If both teams agree to use a non-Faceit server, the agreement must be documented with screenshots. When documented properly, admins will not accept protests related to server issues.
1.2 Server selection
Server selection aims to provide equal and consistent ping. Default server assignments:
| Matchup | Default Server(s) |
|---|---|
| EU vs EU | Frankfurt, Germany |
| EU vs South America | All rounds on US East Coast servers |
| EU vs USA | At least one round on London and one on US East Coast (may vary) |
| USA vs South America | One round on US East Coast and one on a South American server |
Any deviation requires mutual agreement during match scheduling. Requests made after the match has started will not be considered.
1.3 Cross-region teams
Cross-region teams present challenges finding fair servers. The admin team will work with cross-region teams to find practical solutions and may impose conditions to prevent unfair advantages. If you plan to compete as a cross-region team, contact organisers before joining. If matched against a cross-region team and you believe the server is unfair, raise the issue before the match.
2. Match Media
2.1 Screenshots
A screenshot of the scoretable at the end of each round must be provided. (This requirement may not apply while using Challonge.)
2.2 Replays / Demos
A demo must be recorded for each round by at least one player from each team.
3. Settings
3.1 Server settings
Server settings should match Faceit servers. If playing on a non-Faceit server by agreement, both teams must be informed which settings are used.
3.2 Client settings
| Setting | Requirement |
|---|---|
cl_timeNudge | 0 |
cl_maxPackets | 100 |
| Rate | Min 25000, Max 90000 |
cg_fov | Max 97 |
cg_thirdPersonRange |
Max 100 (JAMP or Tayst/EternalJK with cg_fovAspectAdjust 0)Max 80 (Tayst/EternalJK with cg_fovAspectAdjust 1)
|
Any other cg_thirdPerson… or client settings that are cheat-protected on the original JAMP client must remain at default values when using clients that unlock them—unless event rules state otherwise. Conclusive evidence of abuse will result in bans (current cup and possibly future cups).
3.2.1 Changing team names
A team may change its name at any time (including after restructuring). Changing a team name to deceive other teams is prohibited. Extremely long names or frequent changes may be punished.
3.2.2 Players in team
A player may only play for one team in a tournament or league.
4. Match Rules
4.1 Game preparations
4.1.1 Game version
All matches must be played on game patch 1.01. Third-party clients such as EternalJK are allowed provided required settings are enforced. Restrictions of the original basejamp client must be followed and never abused (no wallhacks or equivalent built-in cheats).
4.1.2 Nickname
Players must use a nickname related to their cup nickname. Colors, symbols and clan tags are allowed if identity remains clear.
4.2 Substitutions, spectators and intermissions
4.2.1 Exchanging players
Player exchanges during a match are allowed only immediately after the player to be replaced has died.
4.2.2 Player drops
If a player disconnects or cannot continue for a valid reason, pause immediately and take a screenshot of score and time. If the match cannot continue that day it must be rescheduled. If rescheduling fails, admins may award a default win.
4.2.3 Intermissions
If interrupted, scored points are saved. Take a screenshot if possible. The match resumes with remaining time (examples: interruption at 9:12 with max 15 minutes → 6 minutes remain; interruption at 9:00 → 6 minutes; at 8:59 → 7 minutes).
4.2.4 Spectators
Teams may request rounds without spectators (including substitutes) but at least one admin must be present. Substitutions mid-round require pausing so the substitute can join the server.
4.2.5 Swapping / replacing a team member
Players may be replaced only if they have not participated in any match during the cup. Admin approval is required for all swaps; admins may decline.
4.3 Illegal actions
4.3.1 Exploits / Bugusing
Exploiting map bugs is prohibited. Examples: glitching through impassable objects, exploiting textures to gain vision through objects. (Killing by jumping on a player using an elevator is not considered a map bug.)
4.3.2 Modded content
Using content that alters gameplay or provides advantage is forbidden. When in doubt, contact admins before the match.
4.3.2.1 Modified / new sabers
Non-compliant sabers are not allowed. Violation leads to severe penalties.
4.3.2.2 Player models and skins
Only models/skins selectable by default in the main menu Profile are allowed. Custom models from the in-game character creator are allowed. Custom files or cvar-only models/skins are forbidden.
4.3.3 Third-party software / patches
Any software that alters gameplay or gives advantage is strictly forbidden. Matches where the winner used such software will be deleted.
4.3.4 Excessive avoidance / strategic evasion
Continuous avoidance of opponents (beyond brief passive play) is prohibited. Examples of prohibited behaviour:
- Constantly using map objects to hide or escape to prevent opponent engagement.
- Extensive running, jumping or hiding to avoid enemy contact for long periods.
- Using small unplayable map parts to create unbalanced tactics (e.g., 'king of the hill').
Permitted passive play: as long as the player does not make themselves unreachable and does not constantly change main map locations. Attackers may counter-attack while allowing opponents to reach them.
4.3.5 Intentionally killing / laming
Intentionally killing a player who is in chat is unsportsmanlike and will be penalized: frag removal and warnings; repeat offenders receive larger penalties and temporary bans. Accidental lames due to chat pop-up are not penalized.
4.3.6 Excessive usage of special moves
Staffers: maximum of 5 BF/GBF during a 10-minute round and 7 during a 15-minute round. Exceeding this results in removal of 7 frags from the team and a warning; continued intentional use may lead to default loss.
Penalty System
General
- No show — Disqualification. Repeated no-shows may result in bans.
- Using a player not on the team (name faking or playing unlisted player) — Disqualification and team ban from the next tournament.
Unsportsmanlike behaviour & deception
- Multiple/fake accounts — Ban from the next cup.
- Deception — Disqualification from current cup and ban from next cup.
- Fake result or fake match media — Disqualification and admin review; further penalties possible.
- Fake match — Disqualification and ban from 3+ future cups.
- Cheating — Minimum ban of 3 future cups plus immediate disqualification (severity assessed by admins). Same applies to abused settings or modded hilts (see §3.2 & §4.1.2).
- Usage of map bugs — May result in disqualification.
- Excessive avoidance (§4.3.4) — Usually punished with round replay; further penalties possible.
Demos and screenshots
- Failure to provide requested screenshots or demos may result in disqualification.
- Intentionally laming (§4.3.5) — 1 frag removed; repeat offence: 5 frags removed and player banned for 3 matches.
- Excessive special moves (§4.3.6) — 7 frags removed; continued intentional abuse leads to default loss.