💥 Dominate the Skies! 💥

Ready your rotors and crew! Battlefield 6 Helicopters vs Helicopters is here to settle the score on who the true aerial aces are. This isn't about infantry, it's raw, explosive, airborne warfare.

This competition pits two helicopters againts one another, each manned by two teammates in pure helicopter combat, using only the weapons mounted on your aircraft. Each team deploys two separate attack helicopters in fast-paced round-based elimination matches.

🚁 Get Your Team in the Fight!

The skies are calling, but you can't go alone!

• Teams need a minimum of 2 and a maximum of 10 players on the roster. Assemble your crew of expert pilots and gunners!
• Ready to fly? Click the Create Team button to start your own air squadron, or check out the Teams already queued on the ladder and join an existing squad.

🏆 The Format: Best-of-3 Maps

Think you're the best? Prove it! Matches are played across 3 maps, with each map being a Best-of-11 rounds. First team to win 6 rounds takes the map, and first to win 2 maps wins the match!

🔥 More Ways to Compete!

The helicopter ladder is just the beginning of the return to classic competitive action!

• The rules are based on the legendary and successful TWL 2v2 helicopters competition. Expect fast, fair, and fun matches.
• Sign up your team NOW to join the queue and show us you're ready to rumble!
• We're actively exploring bringing back more classic formats, including 2v2 planes and tanks.
• Beyond the ladder, we're looking at hosting full leagues and special tournaments.

Your legacy on the TWL ladder continues today! Sign up, squad up, and let the rotors spin!

🚁 TWL Battlefield 6 Helicopters vs Helicopters Ladder Rules

1. Introduction

1.1 Rule Hierarchy

Ladder Specific rules supersede the corresponding general ladder rule.

• Type of Gameplay: Round-Based Vehicle Elimination (Vehicle-only scoring)
• Number of Maps: 3 (selected from supported map pool)
• Members per Team: 2 (1 Attack Helicopter Pilot, 1 Attack Helicopter Gunner)
• Time Limit: Per Admin settings (Rounds end on 1 target kills or 3 minute timer expiry)
• Friendly Fire: On (no exceptions)
• Rounds: Best of 11 (First to win 6 rounds)
• Map Selection:
  • System picks tie-breaker
  • There are 5 maps
  • Each team then bans 1 map
  • Home team chooses first map to play
• Side Selection: Away team always chooses side
• Server Selection: Hosted via Portal Experience Code
• Map Play Order:
  • Home team chooses first map to play.
  • You only have to play the tie-breaker if you have to.

2. Server settings

• Servers must be hosted using the TWL Portal experience codes
• Alternative specific map codes are available in Section 3.
• The server host is the home team; the one hosting the experience is the "Server Admin".
• The experience includes an Admin panel for live tuning (round kills target, wins, ties, clock, round start/end) and auditing. This is accessible in the top right while the triple-tap "Ready-Up" screen is visible.
• Mandatory Tuning Settings:
  • HEAT Seekers: Banned.
  • Helicopter HP: 180%.
  • Damage: 93%.

3. Maps

Maps will be selected as such:

• System picks tie-breaker
• There are 5 maps
• Each team then bans 1 map
• Home team chooses first map to play

Use the Experience Codes below. When starting the server, please specify the code corresponding to the agreed map configuration.

Mirak Valley Experience Code: Z Q X D Y Firestorm Experience Code: Z Q X D N Manhattan Bridge Experience Code: Z Q X D 4 Liberation Peak Experience Code: Z Q X D D Sobek City Experience Code: Z Q X D H

4. Map Rotation

• Total maps: 3 maps
• Map order: as dictated in the match details on TWL or agreed by both captains and admin beforehand in Match Comms

5. How you win

5.1 Victory Conditions

Matches follow a Best-of-3 Maps and Best-of-11 Rounds per map. The first team to win 6 rounds wins the map. A round is won by achieving 1 target kills (destroying the opposing team's helicopter). In the case of a tie the last round will have a flag to capture to determine the winner.

5.2 Helicopter Combat Flow

1. Triple-tap the interact key to display the Ready Up dialog.
2. Use the dialog to set your per-player ready state.
3. Vehicles register to a team on first entry. Wait for the "Vehicle Registration" message to pop up when entering your helicopter. If you don't see this, get out and back into your helicopter.
4. Once the match is live, destroying a registered helicopter awards the opposing team a round kill.
5. Resupply: Use ammo crates for resupply. More ammo crates are given once returning to your main base between rounds.
6. Respawning is allowed, but you only have one helicopter!

5.3 Scoring and Tie-Breakers

• Rounds and kills are tracked automatically in a custom HUD. Screenshot this at the end of every round!
• Tie-Breakers: The Portal experience handles Map ties and round logic automatically via the Admin panel settings.
• Teams must add up all 3 data points across all three maps: Map Wins, Round Wins, Total Kills. These are the tie breakers in order:
  • Most Map Wins: if these are even (e.g. 1-1-1), then:
  • Most Round Wins: if these are even (e.g. 6 round wins each), then:
  • Most Total Kills is the last tie breaker (e.g. 14 total kills vs 12 total kills)
• HUD and victory/round-end dialogs mirror the authoritative match state.

5.4 Default Game Mode / Ceiling

• You must select "Helos Only - TWL 2v2" in the ready screen and press confirm and apply mode changes.
• Once the settings take hold you should see the confirmation on the upper left of your screen.
• The exception to this is if both teams agree to play custom settings in match comms.
• NOTE: As soon as you set a custom ceiling you lose the ability to restore the BF6 Vanilla aircraft ceiling setting and need to reset the map in order to play Vanilla ceiling settings again.
• Take lots of screenshots in case there's a dispute.

6. Match behaviour

All members of all teams are responsible for treating each other with respect during the match. Please respect those in the server at all times and don't be careless with your language. The server as well as all members of each team should be running the latest patch available from EA Games.

Players are expected to conduct themselves in match play with a professional and courteous attitude towards other players and Admins at all times. Unsportsmanlike behavior consists of constant global spamming, taunting, and direct insulting. Any unsportsmanlike conduct reported to the ladder Admins and verified can lead to disciplinary action against said player(s) or even the team itself if severe and blatant enough to warrant such actions. Severe and gross misconduct may even lead to more severe repercussions such as dismissal from a team, ladder, or TeamWarfare. Said resolutions will be at the discretion of the ladder Admins as well as TeamWarfare Admins.

Racist or sexist remarks will not be tolerated. Simple, straight forward... Play nice.

7. Player and vehicle limits

7.1 Helicopter-Specific Rules

This is a 2 vs. 2 helicopter ladder. Teams must deploy both attack helicopters with proper pilot/gunner crews.

Important Technical Limitations:

• Cannot edit vehicle loadout once in-game. You must reconnect to reconfigure and then rejoin.
• Tip: Choose and select your optimal/desired attack helicopter loadouts before joining the server. Consider equipping Light Rockets for infantry, Heavy Rockets for vehicles, or TOW Missiles for aircraft.
• Control Assist: Helicopter Control Assist is allowed and recommended. It makes helicopters automatically hover when no control input is detected.
• If you have issues spawning in, ensure your loadout is properly configured before entering the helicopter.

7.2 Team Composition

Each team is to field a minimum of 2 players. If a team is unable to meet this requirement, the offending team must either forfeit or reschedule the match at a later date with cooperation from the opposing team captain. If neither team is able to fill 2 positions at the start of the match, the match will be nullified unless both teams choose to play the match with less than the required number of players.

8. Team rosters

8.1 Roster Requirements

• Minimum roster size: 2 players
• Maximum roster size: 10 players
• Roster changes: May be made on any day outside of a match challenge. Rosters lock as soon as a challenge is issued.
• Two-week rule: Once a team joins a ladder, that team has 2 weeks to bring their roster to the minimum roster requirement for that ladder. Failure to do so will result in removal from that particular ladder.

8.2 Roster Eligibility

Ladder members join teams per ladder and may only be a member of one team per ladder. In order for a player to be considered 'eligible' for a match, they must be on their team's roster before the Defender accepts the challenge and remain on the team until the match is completed.

8.3 Player Identification & Verification

To maintain competitive integrity and prevent "smurfing" or the use of unauthorized ringers, all players must compete using their primary, verifiable identities.

• 8.3.1 Mandatory Account Linking: Competitors are required to link their EA and Steam accounts to their TWL profile. This establishes a "true-to-true" identity that must match the player participating in the match.
• 8.3.2 Streamer Mode Prohibited: The use of "Streamer Mode" or any in-game setting that obscures, anonymizes, or alters a player’s EA ID/In-Game Name (IGN) is strictly prohibited during any ladder match. Real account names must be visible on the scoreboard and in all submitted media (screenshots/recordings).
• 8.3.3 Naming Consistency: The in-game name (IGN) appearing on the Battlefield 6 scoreboard must match the name listed on the official TWL Match Roster. If a player updates their EA ID, they must update their TWL profile accordingly before participating in any further matches.
• 8.3.4 Verification Failures & Ringer Protocols: If a player is found using Streamer Mode, or if a player's name does not match the roster, the following steps must be taken:
  • Immediate Notification: The opposing team must notify the player/captain via match comms as soon as the discrepancy is noticed.
  • Correction Period: The player must be given the opportunity to disable Streamer Mode or clarify the identity (e.g., "I updated my EA ID and forgot to update the TWL profile").
  • Refusal to Comply: Refusal to disable Streamer Mode or provide identity verification upon request constitutes a Major Infraction (Match Forfeit) as outlined in Section 13.3.
• 8.3.5 Pre-Match Validation & Dispute Finality: To prevent post-match disputes over minor clerical errors (e.g., a single-character misspelling or an outdated EA ID that clearly belongs to the same person):
  • Proactive Verification: Team captains are expected to verify the opposing roster BEFORE the match begins.
  • Finality of Play: If a match is played in its entirety without a dispute being raised in match comms regarding player identity, the results are considered final. You cannot "play through" a match and then dispute a name typo after a loss.
  • Verification Truth: Since TWL utilizes account linking (Steam/EA), the linked ID is the "source of truth." If the link is correct but the display name has a minor typo, an Admin will rule in favor of the match result. Don't be a "Rule Lawyer"—verify your opponents before you ready up.

8.4 Roster Flexibility

If a player drops from a team after a challenge is accepted and rejoins, they will only be allowed to legally play if the other team agrees to it in match comms. Leniency is given for people that sign up on the same day a match is accepted.

8.5 Substituted Players/Rejoining

Due to the nature of the internet, it is possible for players to be disconnected from the internet or dropped from a server. Should this happen, you may substitute an eligible player to fill the spot or the dropped player may rejoin. However, upon joining the server the player must rejoin their respective team immediately. Anyone joining the opposing team's side for over 30 seconds will be considered observing and will subject their team to forfeiture of the match or replaying the map.

Due to the sizes of some teams, it is acceptable to rotate players at the beginning of new maps. However, this should be done in a timely manner that does not hinder the progress of the game. In other words, please have your teammates "waiting in the wings."

Substitute players, brought in during match, that are not eligible players by the above criteria, will force an immediate forfeiture on the part of the team they were playing for.

8.6 Smurf Policy

Smurfing is signing up for more than one team (or the same team) on the same ladder, either under the same name, or a different name. It is also the act of playing for a team you are not registered to play for, under a false identity.

Playing for a team you are not registered to play for is prohibited. Playing on more than one team per ladder is also prohibited, as is registering multiple accounts for use on the same team or ladder.

Minimum punishment for the violation of this paragraph is as follows but not limited to: (It will ultimately remain sole discretion of TeamWarfare Staff)

• The team that the smurf joined or played for most recently will be deleted.
• The smurf's original team will be dropped 33% of the ladder.
• The smurf's account(s) on, and possibly access rights to, TWL will be revoked.

Additionally, team captains and founders can contact your games coordinator (Admin). The Admins will cooperate fully with team captains and founders in order to combat and prevent smurfing. We will NOT hand out IP's so don't ask, but we will be more than happy to check a certain player on your team.

8.7 Inactivity

Teams of the TWL are expected to remain active while on the ladder. Any team showing inactivity for a period of three weeks will be deleted from the appropriate ladder. This time frame of course does not include "Rest" time taken.

Teams are allowed to take vacation time out of an available pool that is shown to team owners and captains. Teams in #1 position are not eligible for a timeout and must drop to a lower rung to take the vacation time.

9. Captain's Responsibility

9.1 Challenge Acceptance

You can challenge anyone above you 10 slots or 50% of the remaining ladder from your current rank - whichever is higher. (Ex: Rung 100 can challenge rung 50. Rung 48 can challenge to rung 24. Rung 15 can challenge to rung 5).

All ladders have a time limitation for match responses. This includes Acceptance of a Challenge and/or Date Acceptance. The present time frame is 72 hours. At that time a "Flag" is created for the Ladder Admins to address the next time they login to their Admin Console. If the problem is resolved by that team prior to the Admin logging in, then the match continues as before. If the Admin logs in first, the appropriate action will be taken. In this case, forfeits will be granted and rungs dropped.

9.2 Match Confirmation

Matches are to start at the agreed time, and a 15-minute grace period will be allowed should a team run late or have a problem rounding up members. After this grace period, the team with members present and waiting on the designated server should contact an Admin immediately in Discord in the appropriate channel. Please supply both teams involved in the match and ladder should that apply.

Teams should have the minimum number of players on the appropriate server no later than 15 minutes after the scheduled match time. Failure to meet this requirement will result in an immediate forfeit against the non-compliant party. Both teams should be ready to play no later than 30 minutes from the scheduled match time (Unless agreed upon by both parties). Failure to agree to start the match at this time will result in forfeiture by the non-compliant party.

9.3 Roster Verification

It is each team's responsibility before the match starts to see that all players are legally registered on each team's roster. After match start or completion, roster disputes are not valid justification for forfeiture or Admin intervention.

9.4 Side Selection and Map Choices

Side selection and team swaps are facilitated by the Portal Experience, which includes a Team Swap button with forced undeploy to ensure fair side rotation.

Map side choices and order must be relayed to the attacking team no more than 24 hours after the attacker schedules the match. Failure to keep these deadlines may result in your forfeit of these options at the opposing team's (and Admin's) discretion.

9.5 Screenshot and Evidence Requirements

• Please have either demos or screenshots available if requested for verification. Please make use of the match communications system in place for captains and founders to use to reinforce attempts to set up match details.
• You need a screen shot of the final match results
• Each team should be aware of the admin panel
• Note that you can/should drop relevant screenshots into Match Comms channel

9.6 Team Management

Teams have one (1) Owner and any number of Captains. Captains are assigned at a ladder level. Owners are captains on all ladders. The team Owner should determine who should be in charge of issuing challenges per ladder and maintaining the team information. Multiple team captains can be assigned to perform such duties.

• There are only to be a maximum of 2 captains assigned to any ladder match.

You can only issue a challenge by making it in your Team's Admin Console on your ladder control panel on any day of the week. Access to the Team Admin Console is available to all Captains. NOTE - You must login to the ladder in order to administer your team.

9.7 Challenge Cancellation

On the TWL, there is no availability for the team Captains or Founders to cancel a challenge. All Cancellations must be coordinated through a Ladder Admin. Cancellations are not always guaranteed.

9.8 Rescheduling

Should a match require rescheduling, the new match time should be within 3 days of the original match time. Matches can only be rescheduled once. Mutual consent via match comms between opponents is required. If teams can not agree to an alternative time for their match within one week of the challenge being issued, they must either be forced to play the original default dates or both agree to cancel the match.

9.9 Punctuality (Preparation)

In between maps, a maximum preparation time of 10 minutes (15 minutes if you're switching servers) is allowed before starting the next map. Your opponents may start the map if you exceed these time limits.

9.10 Match Results Reporting

Match results will be reported no later than 1 HOUR after the conclusion of a match. Failure to do so will result in:

1. First Offense: Dropped a percentage of total rungs on ladder (10 rungs)
2. Second Offense: Removed from ladder

Teams will have the opportunity to rejoin if removed, but will have to start at the bottom. Infractions of this rule are left at the discretion of the Admins and may vary depending on the circumstances.

By reporting the results, teams waive their rights to protest (ultimately decided by TeamWarfare Staff). It is also to be known that once a match has been played/reported, neither team can attack each other for 7 days.

10. Match Communications

All match communications must take place through the TWL Discord Match Comms system. This system provides dedicated channels for each match to facilitate coordination between captains and Admins.

10.1 Discord Channel Usage

Discord channels are available if you wish to use them in order to meet up with your team members and the opposing team before the match. We suggest you use this in order to ensure nobody has any problems joining the server, etc. Additionally, an Admin will be available specifically for Battlefield 6.

10.2 Server Communication

Server preference and choices are communicated through the "Match Communication" Portion of your Team Admin Console. All servers must be posted in the online match communications 48 hours prior to the match time. If no attempt is made to offer a server for your team, and the opposing team has offered a server, all matches may be played on the opposing team's server per their request.

10.3 Match Comms Requirements

Please make use of the match communications system in place for captains and founders to use to reinforce attempts to set up match details. All important match-related decisions and agreements must be documented in Match Comms.

11. Disputes

11.1 General Dispute Policy

All disputes will be handled by the ladder Admin. Each and every dispute inevitably involves different aspects and will be dealt with individually. Disputes must be submitted NO MORE than 1 hour after completion of the match. DO NOT REPORT A LOSS IF YOU PLAN TO DISPUTE. Use the built-in dispute feature found in your administration panel.

Once a match has started, it is understood that both teams agree to the terms of the match (number of players, time limit, rosters, etc). If there is a disagreement of match terms AFTER match completion, the disagreement will be thrown out.

11.2 Cheating Disputes

Until a demo feature is supported or confirmed to be present in the game, screenshots will have to suffice as evidence.

11.3 Evidence Submission

If match results are being protested, a ladder Admin and the opposing team captains must be made aware of the protest within one hour from the completion of the match via the "Dispute Results" link in your admin panel AS WELL AS through match comms. Failure to do BOTH may result in an Admin reporting the match.

After a protest has been initiated, both teams have 24 hours to gather evidence. In this time, the team being protested against may issue a counter-protest.

11.4 Resolution Timeline

ALL match issues should be resolved within 48 hours from match completion.

11.5 Server Disputes

Server disputes must be handled before match completion. Disputing a server after a match has been played will result in the dispute being thrown out.

12. Exploits

12.1 General Exploit Policy

The rules are intended to be guidelines for competitive matches. We reserve the right to review any disputes against the published set of rules and declare something outside the published set of rules.

12.2 Helicopter and Map Exploits

• Bailing Policy: Bailing out of your helicopter to avoid being destroyed or to deny a kill to the opposing team is strictly prohibited. Crews must stay with their aircraft during combat. Landing the helicopter to perform repairs or drop ammo boxes is permitted, provided the crew re-enters the aircraft immediately upon completion. Staying outside the helicopter while not actively repairing or resupplying is prohibited. These actions should only occur while the helicopter is fully landed.
• Main Base Gating: The experience includes main-base entry/exit tracking. Obey pre-round "over-line" warnings.
• Terrain Exploitation: Hiding helicopters inside terrain geometry or using map glitches for invulnerability is prohibited.

12.3 Map Bugs

Exploiting map bugs, including but not limited to going under the map and moving through or shooting from places where flaws in the textures allow you to see through walls, using the 180 view (looking down) to hide underwater while taking/holding flags, etc. is prohibited.

13. Cheating/Hacking

13.1 Zero Tolerance Policy

TWL maintains a zero tolerance policy for cheating and hacking. Any violation will result in immediate action against the offending player and potentially their team.

13.2 Prohibited Actions

The following are NOT permitted in Battlefield 6 gameplay while participating in a ladder match for the TWL:

• Switching teams after being killed in order to observe the other team's players
• Running a server-side mod without the permission from the other captain
• Removing the other team's players by means of kicking or vote kicking
• Changing the map outside of agreed rotation
• Dead players communicating with live players via the console during match play
• Use of any client-side modification that enhances your aim (including aimbots but not including custom crosshairs)
• Exploiting map bugs (see Section 12.3)
• Not following any of the specific rules above
• Any client side mod that changes fog distances (i.e., No fog or less fog)
• Any client side mod that changes the skins to aid in friendly/enemy difference (i.e., red/green/pink helmets)

13.3 Consequences

Violation of ANY of these will result in an automatic forfeit and potentially expulsion from the TWL ladders. Un-sportsmanlike conduct during matches will not be tolerated by the TWL. If an Admin is called in to resolve an issue regarding un-sportsmanlike conduct, the judgment/punishment will be swift, efficient, and final.

14. Qualified servers

14.1 Server Requirements

Servers must use a TWL BF6 experience code (See section 3). The server should be password protected and the password posted before the match in match comms, but we recognize that currently Battlefield 6 makes this experience frustrating at times so you can agree to not use a password.

14.2 Server Equity Rules

NOTICE: Server selection is required to be equitable for both teams. If the teams cannot agree on either of the presented servers as being equitable, a TeamWarfare Admin will mandate a neutral server.

Server selections are bound by a "reasonable difference" in ping. If the average ping differential is substantial, the opposing team has the right to refuse a server, provided there is a viable alternative server open for match use.

Servers with vast differences in average ping are not considered equitable. Ping difference should not exceed 75ms between the teams. Players with over 250ms ping should be discarded from the average.

14.3 Server Selection Protocol

The defending/home team chooses the server.

If a neutral server cannot be agreed upon, then the 1st and 3rd maps will be played on the Defender's/Home's Choice, and the 2nd will be played on the Attacker's/Away's choice.

14.4 Server Stability

Please ensure the server's stability and capability to withstand 4 players before the match begins. In the event of excessive lag, another server may be chosen or the match may be rescheduled.

14.5 Server Type

Server hosting requirements: Use the official TWL Portal Experience Codes (e.g., ZKBX5).

15. Admins

15.1 Admin Roles

TWL Admins are responsible for overseeing ladder operations, resolving disputes, and ensuring fair play. Admins have the authority to make final decisions on all match-related issues.

15.2 Admin Observation

Admins may observe any match at any time. Extra server slots should be available for Admin observation.

15.3 Admin Contact

Any questions or concerns in regards to match play by other teams, players, or questions in general can be directed to the Battlefield 6 Staff. A TWL Admin should be contacted immediately (via Discord) for a ruling to be made. If an Admin isn't available, then the match should be postponed, and a dispute must be filed.

15.4 Self-Policing

Teams are expected to self-police and report suspected cheating or rule violations. Admins will cooperate fully with team captains and founders in maintaining competitive integrity.

Final Remarks

Remember: Please handle all situations such as server difficulties with a mature, responsible, and reasonable attitude. Good luck and we hope this brings you a side of Battlefield 6 that you have been wanting to see.

16. Changelog

• March 26th, 2026
  • dox: Updated server settings (HEAT Seekers banned, HP 180%, Damage 93%).
• March 15th, 2026
  • dox: Reorganized "Additional Rules" into relevant sections (1.1, 8.7, 9.10, 15.4) for better document flow.
  • dox: Updated Section 8.3 (Player Identification & Verification) to enforce account linking and prohibit Streamer Mode.
• March 2nd, 2026
  • dox: Added scheduling agreement deadlines (Section 9.8), and clarified vacation/timeout eligibility for top teams (Inactivity).
• February 1st, 2026
  • uberdubersoldat: Completed rule adaptation for Duo helis beta launch
• January 3rd, 2026
  • uberdubersoldat: Refactored rules to align with 1.0 Portal experience
  • dox: Cleaned up antiquated bits and clarified server selection, etc
• December 27th, 2025
  • dox: Refactored rules to align with Portal Experience alpha mechanics.
  • dox: Updated map codes to include ZKBX5 and specific map variants.
  • dox: Changed Victory Conditions to Best-of-3 rounds with 2-kill round limit.
  • dox: Updated Combat Flow to include Ready Up dialog, repair proximity, and resupply mechanics.
  • dox: Added vehicle loadout limitations.
• January 7th, 2026
  • dox: Adapted 2v2 Helicopters ruleset from 2v2 Tanks for Battlefield 6, incorporating helicopter-specific mechanics including flare management, fragility considerations, and aerial positioning requirements. rations, and aerial positioning requirements.