RULESET INTRODUCTION
All players are required to set their in-game name before the start of the tournament in accordance with the player checklist.
To support the growth of the competitive Battlefield scene and keep the community active, all teams are required to stream their matches.
Streaming helps maintain transparency and allows tournament admins to review gameplay if any issues or rule violations occur.
It also gives the community the opportunity to watch matches and see the level of teamwork, strategy, and skill involved in competitive play.
Public streams help promote the league, attract new players, and grow the competitive Battlefield scene.
Additionally, it is mandatory for all players to be on the BFNations Discord and present in the designated voice channels during their matches.
This allows admins to communicate quickly with teams, monitor the games more effectively, and manage the tournament smoothly if any issues arise.
0.0 The following page is referred as 'Ruleset Introduction' and apply to all BFNations tournaments.
0.1: Not following these rules may results in a disqualification of tournaments.
0.2: For PC players, please make sure to download and install the MOSS Anti-Cheat: https://nohope.eu.
0.3: For PC players, failure to show MOSS proof in case of disputes may impact decisions.
_________________________________________________________
1: Reporting Results & Format
Reporting Results:
Matches shall be played, and results shall be reported via Discord using the designated channels and the win/loss/confirm buttons.
Format:
Swiss System vs Round Robin
Swiss system tournaments pair players with similar scores each round, allowing for large tournaments without elimination, whereas Round Robin requires every participant to play everyone else.
1.0: Starting 2026, BFNations BF6 tournaments may use the Swiss System. If that's the case, we'll specify it when announcing the tournament.
1.1: Otherwise, BFNations tournaments are composed of a round-robin group stage, followed by a single-elimination finals stage for the top two teams of each group. Each group is generally made of (4) teams.
1.2: For Battlefield 1 and Battlefield V, the game is not cross-platform. For 2042, console can participate with PC, but not the other way around. BF6 is cross-platform.
1.3: During the tourney, teams will play BO3. One round per side, per team, for a maximum of six (6) rounds.
1.4: If teams are tied for playoff positions after group stage completion, the following tiebreakers will be used:
-Head-to-head matchup (which team, if any, won their group stage encounter)
-Maps won/lost difference
-Maps won
_________________________________________________________
2: Map Scoring
2.1: The BFN Bot must be used for matches & scores. Click win/loss at the end of the match. The other team leader click must confirm. The score will be automatically saved and appear in the tournament result channel.
2.2: Each team will play Side A round and Side B round on each map.
2.3: Score will be determined by tickets at each round. The team with the most tickets after two (2) rounds wins the map.
2.4: If both teams have won an equal number of maps after four (4) rounds, a third map shall be played (BO3).
2.5: During the group stage, for each match, the possible results are either: 2-0 or 2-1.
2.6: For each weekly win, the winning team shall receive three (3) tournament points: one (1) point for each map won and one (1) point for winning the overall match.
_________________________________________________________
3: Schedule:
3.1: Every 7 days nations/teams have to play 1 match.
3.2: Use the scheduled channel to post your matches in advance (1-2 days). Keep the chat clean using the template.
3.3: Standard Match Day is scheduled for the weekly Saturday at 8PM GMT (EU tournament) or 8PM GMT -4/-5 (NA-SA tournament) in case no other time was agreed upon.
3.4: Standard Match Day for OCEN tournament is scheduled for the weekly Saturday at 8PM UTC +8 in case no other day / time was agreed upon.
3.5: The nation who initially forfeits loses the match and a win is given to the other nation. In the case of playoffs the nation who forfeits the match will be eliminated.
3.6: For special full tournaments or special tournament final matches (e.g., NA-SA vs EU-ME-OCEN), both teams must agree on the scheduled match time for the match to be considered valid. In the absence of an agreement, the match time may be set by an administrator.
_________________________________________________________
4: Host Rights
4.1: In Battlefield 2042 and BF6, the server region is based on the location of the person hosting the game.
4.2: For continental (e.g: EU vs EU) matches the following applies:
-
Higher seeded nation has hosting rights.
4.3: For intercontinental (e.g: NA vs EU) matches the following applies:
-
Higher seeded nation has hosting rights.
4.4: For intercontinental (e.g: NA vs EU) matches with more one map played during the match, the following applies:
-
The higher seeded nation hosts the first team region rounds, the second team region rounds will be hosted by the lower seeded nation.
4.5: If the higher-seeded nation has not provided server details after 15 minutes of the scheduled start time and the opposing team is ready, the match may be forfeited.
For the information to be considered valid, the higher-seeded team leader must post the server details in the match channel created of the BFNations Discord server.
All server details, including the experience name, must be clearly visible to the opposing team leader. The server password must be sent in the match channel or via direct message to the opposing team leader at the same time.
The owner of the participating nation team is considered the team leader and is responsible for communicating the server details within the required timeframe.
4.6: For OCEN vs India matches both games are played on a Singapore server. If both teams mutually agree to use a different server, that server shall apply.
4.7: For CH vs US West matches, both rounds shall be played on JP servers. For CH vs US East matches, both rounds shall be played on EU servers. For CH vs EU matches, both rounds shall be played on German (EU) servers. If both teams mutually agree to use a different server, that server shall apply.
▪ EU vs ME – One EU server and one ME server
▪ NA vs NA – NA East, NA West, or both
▪ NA vs EU – One NA East server and one UK server
▪ NA vs ME – EU server
▪ NA vs SA – One NA East server and one SA server
▪ EU vs AUS – NA West server
▪ SA vs EU – NA East server
▪ SA vs ME – NA East server
▪ SA vs AUS – NA West server
▪ NA vs AUS – Japan server
▪ AUS vs ME – Singapore server
▪ AUS vs Asia – Singapore server
__________________________________________________________
5: Map Veto (Ban)
5.1: Map decision takes place in the form of a map veto system. Best of 3 maps veto is used.
5.2: Best of 3 maps:
A BO3 VETO will continue until there are three maps remaining in the map pool.
-
The higher seeded nation must VETO one map. The lower seeded nation follows and must VETO one map.
-
When two maps have been VETOed, both nations may pick a map they want to play as their ‘home map’.
-
When two home map have been decided, the higher seeded nation must VETO one map. The lower seeded nation follows and must VETO one map. Repeat this until 2 map remains.
-
When there are two maps remaining, the lower seed will VETO one map. The remaining map will be played as the 3rd map.
_________________________________________________________
6: Player & Server Crashes
6.1: Player Crashes
If a player disconnects within the first 15 seconds of a map side and before any kills have occurred, the side must be restarted, and the opposing team leader must be informed by replying in the BFNations Discord server.
-
If a player disconnects while a kill has been made in the side and the side is therefore live, the player must rejoin the match as soon as possible.
6.2: Server Crashes
If the server crashes DURING the first 4 minutes of the side, the round is to be fully replayed.
-
If the server crashes AFTER the first 4 minutes of the side, nations will be required to keep the point score obtained thus far and continue playing the second half of the map.
_________________________________________________________
7: Roster & Substitutions
7.0: In case of disputes, decisions shall be based on proof that the IGN (in-game name) has been set via the /ign set command on the BFNations Discord server.
The IGN must be visible on the player’s profile at all times during the tournament, must match the name used in-game, and must be usable to locate the player’s statistics at any time during the tournament.
7.1: Nations and teams must be registered using the BFNations Tournament Registration.
7.2: Team size: minimum required of the format of the tourney, no maximum.
7.3: It is strictly forbidden for a player not registered in the roster of a nation/team to play for the same nation/team unless a derogation has been allowed by the organizer.
7.4: In the same way, it is formally forbidden for a player to play for a different nation/team than his/her own, except in extraordinary circumstances where in this case also a derogation is allowed by the organizer.
7.5: No changes are allowed for the Final Stage.
7.6: Each player must have only one of his accounts in the nation roster, sharing accounts between players is strictly prohibited.
7.7: Account sharing & cheating devices usage.
-
Penalties going from but not limited to score penalties up to BFNations permanent I.P ban will be enforced for all teams where a cheater or player is found sharing or cheating his account during a tournament.
-
Due to the complex nature of filtering cheaters and players sharing accounts, no details will be given when penalties or ban applied for account sharing.
-
Rule break information will be shared to major league owners of the competitive Battlefield scene.
7.8: It is possible for the nation leader to make player changes during a match, but only between rounds (the round must be finished).
7.9: All players must have register following the steps described in the Tournament Registration page.
7.10: Roster changes are not eligible to play in any matches for 24 hours after your change.
7.11: Use the bfn template in our discord to indicate roster change.
7.12: Group stage roster modification/changes allowed: 7. Final stage changes allowed: 0. The Final Stage starts when the Group Stage ends.
7.13: A roster change is defined by either a player addition to the team, or a player replacement of the team.
_________________________________________________________
8: Glitches
8.1: Nations/Clans using known glitches to get an advantage in matches are subject to ticket or round loss. Each report will be reviewed individually on the severity, and a decision will be made by the admins.
8.2: Nations/Clans are therefore expected to maintain a high standard of fair play when participating in our events.
_________________________________________________________
9: Match Delay
9.1: Nations/teams have 15 minutes to join after the agreed play time, or from the time server details are provided if late communication occurs within the first 15 minutes of the scheduled match time, as specified in Rule 4.5.
If one nation/team does not have enough players after these 15 minutes and the opposing team is ready, the match may either be played with the missing players or forfeited by the team that is not ready.
9.2: If both nations don’t have their full roster ready in after 15 minutes, these 15 minutes are extended by 5 minutes. If after this time both of the national team is not ready, repeat the rule above. Repeat this until 1 national team is fully ready.
_________________________________________________________
10: Penalties & Disputes
10.1: All cases will be discussed internally with all the BFN Staff to have the best possible outcome.
10.2: As we are not able to write down every possible outcome, a certain amount of logic has to be applied with these Penalties. Admin penalties decisions are final.
-
Teams are required to report and provide proof of any rule infraction(s) at the end of the map in which the infraction occurred. Failure to do so can possibly void any penalty for the opposing team.
-
If one of the nations/teams spawned before the agreed time was reached, it will cost that nation twenty (20) tickets.
-
Rooftops ban – twenty (20) tickets deducted per kill
-
Flashlight – twenty (20) tickets deducted per kill
-
Thermal Scope – twenty (20) tickets deducted per kill
10.3: BFNations requires clear MOSS and video proof (or screenshots if tickets-only related dispute), which is preferably uploaded to a web space, accessible via link to an unlisted/not public accessible video source.
10.4: In the event of a player name dispute, the in-game name set by the player using the /ign set command shall be considered the official name and must match the name used in-game. This name must be visible via the /player view command on the BFNations server.
The displayed in-game name will be used to access the player’s statistics through the Battlefield stats bot command /bf6 stats.
All players are required to set their in-game name before the start of the tournament in accordance with the player checklist.
10.5: You are able to send any disputes until one (1) hour after the match has ended. Failure to do so will leave the opposing nation without any penalty.
10.6: If a rule violation happens, you have to make your opponent aware of this!
Good luck, have fun!
