Tweaking the ticket count and server guidance

Another week of BF2042 Conquest. More games and more feedback. The more we are getting experience the more we get ideas how to improve. It’s still early stages and we don’t want to change the rules too much before we have a proper vote.

The rules are reaching the point where they could be put to a real test. We will soon announce a test cup. All the attending team get a vote in future council. The council members are casting their votes for the final rules.

Minor ticket tweak

Las week we lowered the ticket count 560 to 300. It was a major improvement on the gameplay and it changed the game phase substantially. Full 6 rounds of conquest was concluded in about an hour. While it was an improvement it also made one round a bit too short. One slip up in the start spawn and the whole round was done. 300 tickets was perhaps just a little too few. We have decided to tweak the ticket count to 350 to make rounds less brutal.

Targeting 350 tickets

With the new ticket count of 350 it give a team a change to come back even if there is a brief moment of full cap in early stages if the round. The new theoretical round times are

To be hones, the ticket count in Portal is not exact number of ticket. One can adjust the ticket count, but not in number of tickets but rather a percentage of original ticket count. By setting the ticket count to 50% it will be on standard map with 700 ticket 350. But for example Noshahr Canals have more ticket to start with so there will be more than 350 tickets in adjusted server.

How the ticket bleed works in BF2042

Ticket bleed means the automatic reduction of the tickets from the team controlling less flags. In every Battlefield the ticket bleed works a bit differently. In Battlefield 2042 the ticket bleed is not happening at all if both team control the same amount of tickets. When a team gains a flag majority the opposing team start to loose tickets every 5 seconds. The number of lost tickets depends on the number of flags the team with flag majority controls.

Example
The total number of flags on the Caspian Border is 5. In the BCL comp setting, 2 of those are “home sector flags” that are capped in the beginning of the round. When the round starts and both teams have captured their home sector they both control 1 flag and there is no ticket bleed. Once one team captures a second flag and the opposing team still have only 1 flag the team with 2 flags will start bleeding 2 tickets every 5 seconds from their opponent. Once the captures are balanced – both teams controls 2 flags the bleed stops.

The final flag, the 5th flag mastery will determine who starts bleeding. Once a team captures the 5th flag making the capture total to 3, their opponent starts to bleed 3 tickets every 5 seconds. If they manage to get a “full cap” capping all 3 open flags + their home flag the bleed would be 4 tickets every 5 seconds.

In addition to the bleed every kill reduces the opponents tickets by 1 capping capping a flag from the enemy instantly removes 10 tickets from the opponent!

Server settings guide

There has been some questions regarding the server setup and arranging teams on the server. To simplify the process and make the game start more fluent we have made a short introductory video about the server start process. Most of you probably already know the drill, but there are always newcomers who would need some guidance.

Test League

We are planning to have a test league soon™  We have not decided the specifics yet, but we are targeting a short league for teams to get familiar with the game mode and get more experience on the rules. We will announce shortly how it will be concluded.