| Tournament format: | Group then Single Elimination |
| Game mode | AAS |
| Teams size | 40 vs 40 |
| Map format | Large |
| Time limit | 1 Hr (Not including 120sec staging) |
| Server settings | Tournament Mode |
| Vehicles | Trucks, Light Vehicles, APCs, IFVs, Tanks Helis |
| Squad | Tournament Mod used: SC |
| Discord | https://discord.gg/VcZnU6cgQw |
| Settings |
|---|
| No Shadows |
| No Light / Fog |
| No Shadows |
| No Light / Fog |
| Staging Time = 120 Sec |
| Match Time = 3720 Sec |
| Tickets = 270 |
| 5 Flags |
| Ticket Bleed from mid flag = -1 per Minute |
| Mercy Bleed = -60 per Minute |
| First cap precapped |
| Flag Capture Gain = +60 |
| Flag Capture Lost = -30 |
| Neutral Capture Gain = +30 |
| No deployables with camo nettings |
| 1 mortar per FOB |
| Layers may have specific rules |
Each team must submit a roster, but rosters are not locked and may be updated up to 30 minutes before match start. If a team wants to make changes closer to match start time then they must seek approval from Tournament Organisers.
If a team is short on players close to match time, and wish to continue short of players, they must immediately notify a Tournament Manager for approval.
Roster changes are permitted only if:
Both team representatives agree to the transfer
The change is communicated to and approved by tournament staff in advance, and
Both teams involved are still active in the tournament (not eliminated or forfeited).
If a player is found playing for a team other than the one they are bound to without proper approval, penalties will be enforced.
Players with active game bans are not permitted to be involved with a team in any capacity. If a banned player is found to be involved, the team may be penalised and face disqualification.
All players are strictly prohibited from using any third-party software or making any modifications that alter Squad or its gameplay in any form outside of what is possible through the in-game settings. This includes, but is not limited to: .ini file edits, NVIDIA Inspector, NVIDIA Filters, “GamePP” filters, ESPs, wallhacks, aimbots, macros, crosshairs or any similar tools or techniques.
The only exceptions to this rule are operating system–level accessibility tools that are pre-installed with Windows (e.g., color calibration, colorblind modes) or their direct equivalents on other platforms. Any external software or configuration not explicitly approved will be treated as a violation of this policy.
Attempts to bypass or obscure these restrictions—regardless of intent—will result in a permanent tournament ban. The player’s team may also face penalties, including disqualification, depending on the circumstances.
Permitted Programs and Configuration Adjustments Include:
Heli Ramming: Is allowed
Heli Skybox abusing: Not Allowed – Warned and Penalty will be enforced
The use of any bugs or glitches for advantage is strictly prohibited. This includes both known and unknown bugs, unless explicitly listed as allowed in the rules.
Exploiting visual bugs such as disappearing textures in walls, terrain, or other surfaces to gain an advantage is not allowed.
Using main base protection with vehicles to engage in combat (e.g., firing from within the protection zone) is not permitted and considered abuse.
Creating a commander squad with only one player is permitted as under certain circumstances Rally hopping is used as a valid game mechanic.
It is forbidden to enter, shoot through, or look through solid objects or surfaces that are not intended to be transparent.
Passing the squad leader role to another player in your squad to access the shovel is permitted and not considered kit glitching.
Further, disconnecting from the Server to regain a full Kit is not allowed and will result in punishment.
This is allowed, as ragdoll and player model positions may differ between clients, which can make revives appear inconsistent.
Placing buildables through the use of a drone is strictly prohibited.
Vehicles must not be moved during the staging phase. To avoid accidental violations, it’s strongly recommended to refrain from using your keyboard entirely during this period.
In cases of serious abuse of bugs or glitches, tournament staff reserves the right to impose a technical defeat for the round or match. (See Section 3.2.4 – Penalties.)
| Obeject | Number |
|---|---|
| Mortars | 1 per Radio |
| CAMO NETTING(Excluding Personal Netting) | REMOVED |
| Commander and Assets | ALLOWED |
| MG Emplacements | 2 per Radio |
| TOW | 1 per Radio |
| Repair Station | 1 per Radio |
| HAB | 1 per Radio (unless IMS Faction is played, 2 in that case) |
| Ammo Crates | UNLIMITED |
| Any other Deployable (apart from CAMO NETTING) | UNLIMITED |
Each match is played over two rounds on the same map, with teams switching sides after the first round. The winner is determined by the total number of tickets accumulated across both rounds.
In the event that both teams finish with an equal ticket count in the elimination bracket, the victory goes to the team that secured their round win in the shortest combined time.
During the group stage, points are awarded based on match wins— 3 points per win. 1 point for a tie.
Servers will be provided during the match week. The teams must decide on regions. If a decision can not be agreed, the Tournament Managers will decide. A decision must be made before Wednesday 19:00 UTC
If teams are unable to agree on a match time, the game will be scheduled during one of the designated time windows on the upcoming weekend, as determined by the Tournament Managers. Please note that these time slots may be adjusted to account for daylight saving changes.
By default, if no agreement is reached, the match will be played on the Sunday of the match week.
Times and days will be on a first come, first serve basis. Exceptions may be allowed.
Pre-Match Coin Toss
The winner of the coin toss may choose one of the following:
No later than 48 hours before the scheduled match start time, a coin toss will be conducted between the two teams. This will determine which team has the first choice regarding initial faction selection or server preference (if two servers are being used).
Before the start of a match, both teams must clearly confirm that they are ready to begin. This readiness confirmation also applies prior to any map change.
Teams must be on the server at least 10 minutes before the agreed match start time.
Matches will automatically start at the agreed time, regardless of team readiness.
If a player experiences connection issues, referees or admins may allow a delay of up to 5 minutes at their discretion.
If a team is missing more than 10 players and there is no server-side technical issue, the match will be considered an automatic forfeit for the team missing players. Unless they chose to play 10 people short.
After the map change and during the staging phase, teams are allowed to withdraw their readiness if there is a valid reason—such as major server problems or technical issues, including mass disconnects (5 or more players). This exception is intended only for legitimate situations. Abusing this rule may result in penalties, including ticket deductions (see Section 3.2.4 – Penalties).
Only officially assigned casters and referees are permitted to use the admin cam during a match, including the staging phase. They must not interfere with team rollouts or communicate with players via VoIP unless explicitly authorized by tournament staff.
After the first Round is played there will be a 5 minute break. Should there be a server switch the break time will be used to that, for that break time may be prolonged to 10 minutes after that time the same rules as above apply with the difference that team present wins the round with 270-0 by default.
In the event of a server crash during a match, the referee must immediately escalate the issue to the most senior available tournament staff member. A server is considered to have crashed if the game instance itself crashes or if more than 50% of the players disconnect from the server unexpectedly.
If the crash occurs within the first 20 minutes of the round, the round will be restarted immediately.
If the crash occurs after 20 minutes but before 30 minutes, the referee will mediate a discussion between team captains to determine a resolution, with input from the referee. Both teams must agree on the proposed solution. The available outcomes in this case are:
The round is considered over, and the ticket values at the time of the crash are final.
Both teams agree to replay the round from the start.
If the crash occurs after the 30-minute mark, no options will be given. The round is automatically considered over, and the ticket values at the time of the crash will be used to determine the result.
If the teams are unable to agree on a solution during the 20–30 minute window, the ticket gap will be assessed:
If the ticket difference is equal to or greater than 20% of the starting ticket count, the team with more tickets will be declared the winner.
If the ticket gap is inconclusive, the round will be replayed.
In the case of a second crash during a replay where the ticket values are again inconclusive, tournament staff will determine the winner at their discretion.
Players can be changed at any time during the match. The new player has to fulfil all requirements and has to be eligible to play in the match.
Potential infractions will be identified and flagged by the referee, who is responsible for capturing the best possible footage of the incident. The footage and incident report will then be submitted to the Tournament Manager, who, in collaboration with the tournament staff team, will determine the appropriate penalty.
Penalties carry over between matches and will reset after one season, except for penalties that apply across the entire tournament.
To maintain fairness, staff members are not permitted to vote on penalty decisions involving their own team or their team’s direct opponents in a match.
| Number of Offense | Penalty |
|---|---|
| First offense | -50 tickets |
| Second offense | -100 tickets |
| Third offense | Forfeit Match |
| Fourth offense | Removal from Season |
| Fifth offense | Banned from Tournament |
| Number of Offense | Penalty |
|---|---|
| First offense | banned from one game |
| Second offense | Banned from Season |
| Third offense | Banned from Tournament |
Depending on the severity of the infraction, punishments may be escalated, up to and including disqualification or an instant ban.
If a team fields a player who is currently sanctioned or banned from the tournament, penalties will apply, and the team may be banned from the current tournament.
It is the responsibility of each team to ensure that all players in their lineup are eligible to participate.
Each team has the right to file a protest regarding a match by posting in the appropriate match channel on the tournament Discord within 24 hours of the played match. Only players or teams directly involved in the match in question are permitted to file a protest.
Protests must be made exclusively in the relevant match channel. Posting protests in unrelated channels is strictly prohibited.
All players are required to record their gameplay VODs for every official match and retain the footage until the end of the season.
Recordings must use display capture, not game capture, to ensure full transparency.
If a player is unable to record their VOD, their team representative must inform Squad Esports (SE) to receive an exemption. The SE team will then arrange a meeting with the team rep and the player to assess if the exemption is valid.
SE will notify referees accordingly and may take precautionary measures.
The admin team will initiate a VOD review automatically in cases where a player’s score is deemed exceptionally high.
The VOD review process will proceed, but without the benefit of the defendant’s submitted evidence to support their case. (3.2.6)
If a team believes that cheating has occurred, they must submit a formal accusation alongside any available video or other relevant evidence from the match. Evidence from previous tournaments is not permitted.
Once an accusation and supporting evidence are received, Squad Esports (SE) will publicly acknowledge the claim and confirm that a review is underway.
A panel consisting of neutral referees, casters, and designated SE officials will review all submitted footage and evidence.
Note: Representatives from the accused and accuser teams are not permitted to be involved in the review process, even if they are SE Staff.
After a thorough review, the SE team will come to a final decision.
The decision will be made public, along with the reasoning and any relevant clips or evidence used in the determination.
Penalties will be determined based on the severity of the offence and whether it is a repeat violation.
Note: These actions are separate from any consequences resulting from VOD reviews, which may incur additional sanctions.
Wherever possible, sanctions will be applied to the individual responsible. However, if the infraction has a direct impact on the match outcome, team-wide penalties may be enforced.
In cases of team-wide misconduct, the following will apply:
Disciplinary actions during the Grand Final will differ from standard procedures:
Last updated: 02.06.2025
NONE
These rules govern all tournament matches hosted by Squad Esports. By participating in the tournament, all players and teams agree to abide by them.
Rules may only be changed during a running tournament after prior notice has been given to all participating team representatives. Any rule changes will take effect 24 hours after a public announcement has been made.
Additionally, rules may only be changed before or after the matches of a given week have been played—never during an ongoing match week.