Welcome to symthic forums! We would love if you'd register!
You don't have to be expert in bit baking, everyone is more than welcome to join our community.

You are not logged in.

  • "OldBFAddict" started this thread

Posts: 63

Date of registration
: Mar 4th 2017

Platform: PS4

Battlelog:

Reputation modifier: 1

  • Send private message

1

Thursday, April 20th 2017, 3:16am

Is Frontlines headed to an early grave?

I just played all four maps in under an hour, three under 10 minutes each.

It seems like everyone has it figured out: a squad gets one objective behind the enemy (ahead of the one their team is attacking). If the other side gets pushed back, they almost instantly have the next one captured and can go on to the next once the rest of the team is up. If their team gets pushed back, they can wait or attack the enemy from behind.

Seems like someone is waiting at the telegraph for the last one too fall. The lady barely finishes saying attack the new objectives (A&B) before announcing one is armed.

The tactic can be countered by people staying back to combat the advance guard, but how long before no one is fighting the actual objective?

Posts: 3,191

Date of registration
: Apr 26th 2013

Platform: PS4

Location: Arizona, USA

Reputation modifier: 15

  • Send private message

2

Thursday, April 20th 2017, 3:33am

That tactic shouldn't work at all. If there's a squad from team A lying in wait to back cap that's 5 players who aren't at the current objective, and if Team A is capping with an automatic 5 less potential players then Team B is complete trash because all they have to do is put one more body in the radius to out-burn Team A. Technically, the squad camping an invisible flag is putting their own team at a huge disadvantage since there are only 16 players per team on official servers. I wouldn't be worried one bit about this for the mode as a whole. It's still more balanced and wayyyy more functional than Conquest.
To Aim Assist or not to Aim Assist, that is the question.

Nope. Aim Assist or bust; here's why:

Default Aim Assist Data

Source code

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
AccelerationInputThreshold 0.98
    AccelerationMultiplier 5.0
    AccelerationDamping 4.0
    AccelerationTimeThreshold 0.15
    SquaredAcceleration 0.0
    MaxAcceleration::Vec2
        x 2.0
        y 2.0
    YawSpeedStrength 1.0
    PitchSpeedStrength 1.0
    AttractDistanceFallOffs::Vec2
        x 1.0
        y 1.2
    AttractSoftZone 0.75
    AttractUserInputMultiplier 0.45
    AttractUserInputMultiplier_NoZoom 0.5
    AttractOwnSpeedInfluence 0.0
    AttractTargetSpeedInfluence 0.85
    AttractOwnRequiredMovementForMaximumAttract 0.0
    AttractStartInputThreshold 0.1
    AttractMoveInputCap 0.0
    AttractYawStrength 1.0
    AttractPitchStrength 0.34
    MaxToTargetAngle 45.0
    MaxToTargetXZAngle 45.0
    ViewObstructedKeepTime 0.0
    SnapZoomLateralSpeedLimit 1000.0
    SnapZoomTime 0.2
    SnapZoomPostTimeNoInput 0.2
    SnapZoomPostTime 0.2
    SnapZoomReticlePointPriority 999
    SnapZoomAutoEngageTime 0.0
    SnapZoomBreakTimeAtMaxInput 0.2
    SnapZoomBreakMaxInput 0.2
    SnapZoomBreakMinAngle 90.0
    SnapZoomSpamGuardTime 1.2
    SoldierBackupSkeletonCollisionData *nullGuid*
    CheckBoneCenterOnlyDistance 40.0

No Slowdown Data

Source code

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
AccelerationInputThreshold 0.98
    AccelerationMultiplier 5.0
    AccelerationDamping 4.0
    AccelerationTimeThreshold 0.15
    SquaredAcceleration 0.0
    MaxAcceleration::Vec2
        x 2.0
        y 2.0
    YawSpeedStrength 1.0
    PitchSpeedStrength 1.0
    AttractDistanceFallOffs::Vec2
        x 1.0
        y 1.2
    AttractSoftZone 0.0
    AttractUserInputMultiplier 1.0
    AttractUserInputMultiplier_NoZoom -1.0
    AttractOwnSpeedInfluence 0.0
    AttractTargetSpeedInfluence 0.0
    AttractOwnRequiredMovementForMaximumAttract 0.0
    AttractStartInputThreshold 0.0
    AttractMoveInputCap 0.0
    AttractYawStrength 0.0
    AttractPitchStrength 0.0
    MaxToTargetAngle 45.0
    MaxToTargetXZAngle 45.0
    ViewObstructedKeepTime 0.0
    SnapZoomLateralSpeedLimit 1000.0
    SnapZoomTime 0.2
    SnapZoomPostTimeNoInput 0.0
    SnapZoomPostTime 0.0
    SnapZoomReticlePointPriority 999
    SnapZoomAutoEngageTime 0.0
    SnapZoomBreakTimeAtMaxInput -1.0
    SnapZoomBreakMaxInput 0.2
    SnapZoomBreakMinAngle 90.0
    SnapZoomSpamGuardTime 0.5
    SoldierBackupSkeletonCollisionData *nullGuid*
    CheckBoneCenterOnlyDistance 40.0
    DisableForcedTargetRecalcDistance 7.0


No Auto Rotation Data

Source code

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
 AccelerationInputThreshold 0.98
    AccelerationMultiplier 5.0
    AccelerationDamping 4.0
    AccelerationTimeThreshold 0.15
    SquaredAcceleration 0.0
    MaxAcceleration::Vec2
        x 2.0
        y 2.0
    YawSpeedStrength 1.0
    PitchSpeedStrength 1.0
    AttractDistanceFallOffs::Vec2
        x 1.0
        y 1.2
    AttractSoftZone 0.75
    AttractUserInputMultiplier 0.45
    AttractUserInputMultiplier_NoZoom 0.5
    AttractOwnSpeedInfluence 0.0
    AttractTargetSpeedInfluence 0.85
    AttractOwnRequiredMovementForMaximumAttract 0.0
    AttractStartInputThreshold 0.1
    AttractMoveInputCap 0.0
    AttractYawStrength 1.0
    AttractPitchStrength 0.34
    MaxToTargetAngle 45.0
    MaxToTargetXZAngle 45.0
    ViewObstructedKeepTime 0.0
    SnapZoomLateralSpeedLimit 1000.0
    SnapZoomTime 0.2
    SnapZoomPostTimeNoInput 0.0
    SnapZoomPostTime 0.0
    SnapZoomReticlePointPriority 999
    SnapZoomAutoEngageTime 0.0
    SnapZoomBreakTimeAtMaxInput -1.0
    SnapZoomBreakMaxInput 0.2
    SnapZoomBreakMinAngle 90.0
    SnapZoomSpamGuardTime 0.5
    SoldierBackupSkeletonCollisionData *nullGuid*
    CheckBoneCenterOnlyDistance 40.0
    DisableForcedTargetRecalcDistance 7.0

Prepare your laughbox

the Sebstalder is quiet good since it can 3hit kill at any distanc ,but In my opinion i actually thikn the sweeper is better, its got a really really fast firerate that can beat alll those Noobmaticos, Helregall adn shitguns in close quarters , and its also really accurate out to like l;ong range,. overall great allround gun, jsut my 2$ tho

This post has been edited 1 times, last edit by "JSLICE20" (Apr 20th 2017, 4:13am) with the following reason: Changed to 3rd person.


Posts: 1,733

Date of registration
: Jan 12th 2014

Platform: PC

Battlelog:

Reputation modifier: 13

  • Send private message

3

Thursday, April 20th 2017, 4:45am

That tactic shouldn't work at all. If there's a squad from team A lying in wait to back cap that's 5 players who aren't at the current objective, and if Team A is capping with an automatic 5 less potential players then Team B is complete trash because all they have to do is put one more body in the radius to out-burn Team A. Technically, the squad camping an invisible flag is putting their own team at a huge disadvantage since there are only 16 players per team on official servers. I wouldn't be worried one bit about this for the mode as a whole. It's still more balanced and wayyyy more functional than Conquest.
It's probably a highly viable strategy given the inherently lopsided arrays of players that are stacked up by the auto-balance system.

  • "OldBFAddict" started this thread

Posts: 63

Date of registration
: Mar 4th 2017

Platform: PS4

Battlelog:

Reputation modifier: 1

  • Send private message

4

Thursday, April 20th 2017, 5:02am

I think tankmayvn is correct. This is doubly true on Soissons & Rupture when one team has really good tankers (especially Soissons.)

What I notice more & more:
when the enemy gets pushed back, at least a couple of players don't vacate the objective with their team, often more than a couple. They're trying to stay behind the other team.
When my team gets pushed off an objective, the diamond for the new one behind us shows red as soon as it appears, telling me players from the other team are camping.

Posts: 3,245

Date of registration
: Mar 19th 2014

Platform: Xbox One

Location: Canada

Battlelog:

Reputation modifier: 14

  • Send private message

5

Thursday, April 20th 2017, 5:09am

The mode would likely benefit from the "only current objectives are in-bounds" system that Operations uses, meaning only the current flag objective section and your current spawn section would be in-bounds.
Who has fun, wins.

Posts: 3,191

Date of registration
: Apr 26th 2013

Platform: PS4

Location: Arizona, USA

Reputation modifier: 15

  • Send private message

6

Thursday, April 20th 2017, 5:22am

The cruddy team balance ruins the game as a whole though, not just Frontlines. I wouldn't call it a legitimate strategy because BF1's team balancing is broken to shit.
To Aim Assist or not to Aim Assist, that is the question.

Nope. Aim Assist or bust; here's why:

Default Aim Assist Data

Source code

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
AccelerationInputThreshold 0.98
    AccelerationMultiplier 5.0
    AccelerationDamping 4.0
    AccelerationTimeThreshold 0.15
    SquaredAcceleration 0.0
    MaxAcceleration::Vec2
        x 2.0
        y 2.0
    YawSpeedStrength 1.0
    PitchSpeedStrength 1.0
    AttractDistanceFallOffs::Vec2
        x 1.0
        y 1.2
    AttractSoftZone 0.75
    AttractUserInputMultiplier 0.45
    AttractUserInputMultiplier_NoZoom 0.5
    AttractOwnSpeedInfluence 0.0
    AttractTargetSpeedInfluence 0.85
    AttractOwnRequiredMovementForMaximumAttract 0.0
    AttractStartInputThreshold 0.1
    AttractMoveInputCap 0.0
    AttractYawStrength 1.0
    AttractPitchStrength 0.34
    MaxToTargetAngle 45.0
    MaxToTargetXZAngle 45.0
    ViewObstructedKeepTime 0.0
    SnapZoomLateralSpeedLimit 1000.0
    SnapZoomTime 0.2
    SnapZoomPostTimeNoInput 0.2
    SnapZoomPostTime 0.2
    SnapZoomReticlePointPriority 999
    SnapZoomAutoEngageTime 0.0
    SnapZoomBreakTimeAtMaxInput 0.2
    SnapZoomBreakMaxInput 0.2
    SnapZoomBreakMinAngle 90.0
    SnapZoomSpamGuardTime 1.2
    SoldierBackupSkeletonCollisionData *nullGuid*
    CheckBoneCenterOnlyDistance 40.0

No Slowdown Data

Source code

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
AccelerationInputThreshold 0.98
    AccelerationMultiplier 5.0
    AccelerationDamping 4.0
    AccelerationTimeThreshold 0.15
    SquaredAcceleration 0.0
    MaxAcceleration::Vec2
        x 2.0
        y 2.0
    YawSpeedStrength 1.0
    PitchSpeedStrength 1.0
    AttractDistanceFallOffs::Vec2
        x 1.0
        y 1.2
    AttractSoftZone 0.0
    AttractUserInputMultiplier 1.0
    AttractUserInputMultiplier_NoZoom -1.0
    AttractOwnSpeedInfluence 0.0
    AttractTargetSpeedInfluence 0.0
    AttractOwnRequiredMovementForMaximumAttract 0.0
    AttractStartInputThreshold 0.0
    AttractMoveInputCap 0.0
    AttractYawStrength 0.0
    AttractPitchStrength 0.0
    MaxToTargetAngle 45.0
    MaxToTargetXZAngle 45.0
    ViewObstructedKeepTime 0.0
    SnapZoomLateralSpeedLimit 1000.0
    SnapZoomTime 0.2
    SnapZoomPostTimeNoInput 0.0
    SnapZoomPostTime 0.0
    SnapZoomReticlePointPriority 999
    SnapZoomAutoEngageTime 0.0
    SnapZoomBreakTimeAtMaxInput -1.0
    SnapZoomBreakMaxInput 0.2
    SnapZoomBreakMinAngle 90.0
    SnapZoomSpamGuardTime 0.5
    SoldierBackupSkeletonCollisionData *nullGuid*
    CheckBoneCenterOnlyDistance 40.0
    DisableForcedTargetRecalcDistance 7.0


No Auto Rotation Data

Source code

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
 AccelerationInputThreshold 0.98
    AccelerationMultiplier 5.0
    AccelerationDamping 4.0
    AccelerationTimeThreshold 0.15
    SquaredAcceleration 0.0
    MaxAcceleration::Vec2
        x 2.0
        y 2.0
    YawSpeedStrength 1.0
    PitchSpeedStrength 1.0
    AttractDistanceFallOffs::Vec2
        x 1.0
        y 1.2
    AttractSoftZone 0.75
    AttractUserInputMultiplier 0.45
    AttractUserInputMultiplier_NoZoom 0.5
    AttractOwnSpeedInfluence 0.0
    AttractTargetSpeedInfluence 0.85
    AttractOwnRequiredMovementForMaximumAttract 0.0
    AttractStartInputThreshold 0.1
    AttractMoveInputCap 0.0
    AttractYawStrength 1.0
    AttractPitchStrength 0.34
    MaxToTargetAngle 45.0
    MaxToTargetXZAngle 45.0
    ViewObstructedKeepTime 0.0
    SnapZoomLateralSpeedLimit 1000.0
    SnapZoomTime 0.2
    SnapZoomPostTimeNoInput 0.0
    SnapZoomPostTime 0.0
    SnapZoomReticlePointPriority 999
    SnapZoomAutoEngageTime 0.0
    SnapZoomBreakTimeAtMaxInput -1.0
    SnapZoomBreakMaxInput 0.2
    SnapZoomBreakMinAngle 90.0
    SnapZoomSpamGuardTime 0.5
    SoldierBackupSkeletonCollisionData *nullGuid*
    CheckBoneCenterOnlyDistance 40.0
    DisableForcedTargetRecalcDistance 7.0

Prepare your laughbox

the Sebstalder is quiet good since it can 3hit kill at any distanc ,but In my opinion i actually thikn the sweeper is better, its got a really really fast firerate that can beat alll those Noobmaticos, Helregall adn shitguns in close quarters , and its also really accurate out to like l;ong range,. overall great allround gun, jsut my 2$ tho


Posts: 1,733

Date of registration
: Jan 12th 2014

Platform: PC

Battlelog:

Reputation modifier: 13

  • Send private message

7

Thursday, April 20th 2017, 5:31am

Or they could spend the time perfecting conquest instead of wasting copious dev-time making game modes that virtually no one plays. Conq is like 84% of player-base scores.

Drop a few game modes and spend the time banging out a balancing algorithm that ACTUALLY works.

Posts: 3,191

Date of registration
: Apr 26th 2013

Platform: PS4

Location: Arizona, USA

Reputation modifier: 15

  • Send private message

8

Thursday, April 20th 2017, 5:38am

There are many elements of Frontlines that should be implemented into Conquest. Some would say Frontlines is a straight upgrade to Conquest because it's actually a balanced gamemode. That's why matches can run on for hours and hours; it's an indication that the mode actually works properly. We can see Conquest does not experience the same most of the time.
To Aim Assist or not to Aim Assist, that is the question.

Nope. Aim Assist or bust; here's why:

Default Aim Assist Data

Source code

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
AccelerationInputThreshold 0.98
    AccelerationMultiplier 5.0
    AccelerationDamping 4.0
    AccelerationTimeThreshold 0.15
    SquaredAcceleration 0.0
    MaxAcceleration::Vec2
        x 2.0
        y 2.0
    YawSpeedStrength 1.0
    PitchSpeedStrength 1.0
    AttractDistanceFallOffs::Vec2
        x 1.0
        y 1.2
    AttractSoftZone 0.75
    AttractUserInputMultiplier 0.45
    AttractUserInputMultiplier_NoZoom 0.5
    AttractOwnSpeedInfluence 0.0
    AttractTargetSpeedInfluence 0.85
    AttractOwnRequiredMovementForMaximumAttract 0.0
    AttractStartInputThreshold 0.1
    AttractMoveInputCap 0.0
    AttractYawStrength 1.0
    AttractPitchStrength 0.34
    MaxToTargetAngle 45.0
    MaxToTargetXZAngle 45.0
    ViewObstructedKeepTime 0.0
    SnapZoomLateralSpeedLimit 1000.0
    SnapZoomTime 0.2
    SnapZoomPostTimeNoInput 0.2
    SnapZoomPostTime 0.2
    SnapZoomReticlePointPriority 999
    SnapZoomAutoEngageTime 0.0
    SnapZoomBreakTimeAtMaxInput 0.2
    SnapZoomBreakMaxInput 0.2
    SnapZoomBreakMinAngle 90.0
    SnapZoomSpamGuardTime 1.2
    SoldierBackupSkeletonCollisionData *nullGuid*
    CheckBoneCenterOnlyDistance 40.0

No Slowdown Data

Source code

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
AccelerationInputThreshold 0.98
    AccelerationMultiplier 5.0
    AccelerationDamping 4.0
    AccelerationTimeThreshold 0.15
    SquaredAcceleration 0.0
    MaxAcceleration::Vec2
        x 2.0
        y 2.0
    YawSpeedStrength 1.0
    PitchSpeedStrength 1.0
    AttractDistanceFallOffs::Vec2
        x 1.0
        y 1.2
    AttractSoftZone 0.0
    AttractUserInputMultiplier 1.0
    AttractUserInputMultiplier_NoZoom -1.0
    AttractOwnSpeedInfluence 0.0
    AttractTargetSpeedInfluence 0.0
    AttractOwnRequiredMovementForMaximumAttract 0.0
    AttractStartInputThreshold 0.0
    AttractMoveInputCap 0.0
    AttractYawStrength 0.0
    AttractPitchStrength 0.0
    MaxToTargetAngle 45.0
    MaxToTargetXZAngle 45.0
    ViewObstructedKeepTime 0.0
    SnapZoomLateralSpeedLimit 1000.0
    SnapZoomTime 0.2
    SnapZoomPostTimeNoInput 0.0
    SnapZoomPostTime 0.0
    SnapZoomReticlePointPriority 999
    SnapZoomAutoEngageTime 0.0
    SnapZoomBreakTimeAtMaxInput -1.0
    SnapZoomBreakMaxInput 0.2
    SnapZoomBreakMinAngle 90.0
    SnapZoomSpamGuardTime 0.5
    SoldierBackupSkeletonCollisionData *nullGuid*
    CheckBoneCenterOnlyDistance 40.0
    DisableForcedTargetRecalcDistance 7.0


No Auto Rotation Data

Source code

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
 AccelerationInputThreshold 0.98
    AccelerationMultiplier 5.0
    AccelerationDamping 4.0
    AccelerationTimeThreshold 0.15
    SquaredAcceleration 0.0
    MaxAcceleration::Vec2
        x 2.0
        y 2.0
    YawSpeedStrength 1.0
    PitchSpeedStrength 1.0
    AttractDistanceFallOffs::Vec2
        x 1.0
        y 1.2
    AttractSoftZone 0.75
    AttractUserInputMultiplier 0.45
    AttractUserInputMultiplier_NoZoom 0.5
    AttractOwnSpeedInfluence 0.0
    AttractTargetSpeedInfluence 0.85
    AttractOwnRequiredMovementForMaximumAttract 0.0
    AttractStartInputThreshold 0.1
    AttractMoveInputCap 0.0
    AttractYawStrength 1.0
    AttractPitchStrength 0.34
    MaxToTargetAngle 45.0
    MaxToTargetXZAngle 45.0
    ViewObstructedKeepTime 0.0
    SnapZoomLateralSpeedLimit 1000.0
    SnapZoomTime 0.2
    SnapZoomPostTimeNoInput 0.0
    SnapZoomPostTime 0.0
    SnapZoomReticlePointPriority 999
    SnapZoomAutoEngageTime 0.0
    SnapZoomBreakTimeAtMaxInput -1.0
    SnapZoomBreakMaxInput 0.2
    SnapZoomBreakMinAngle 90.0
    SnapZoomSpamGuardTime 0.5
    SoldierBackupSkeletonCollisionData *nullGuid*
    CheckBoneCenterOnlyDistance 40.0
    DisableForcedTargetRecalcDistance 7.0

Prepare your laughbox

the Sebstalder is quiet good since it can 3hit kill at any distanc ,but In my opinion i actually thikn the sweeper is better, its got a really really fast firerate that can beat alll those Noobmaticos, Helregall adn shitguns in close quarters , and its also really accurate out to like l;ong range,. overall great allround gun, jsut my 2$ tho


  • "OldBFAddict" started this thread

Posts: 63

Date of registration
: Mar 4th 2017

Platform: PS4

Battlelog:

Reputation modifier: 1

  • Send private message

9

Thursday, April 20th 2017, 6:23pm

There are many elements of Frontlines that should be implemented into Conquest. Some would say Frontlines is a straight upgrade to Conquest because it's actually a balanced gamemode. That's why matches can run on for hours and hours; it's an indication that the mode actually works properly. We can see Conquest does not experience the same most of the time.

Frontlines is by far the best IMO. Conquest is a total bore to me.

But the long matches are getting less common.

I like the idea of operations sectors in FL. The problem with that when a team gets pushed back, how do you ensure everyone clears the zone (as in hockey). Or does that sector stay open?

VincentNZ

Holy War? No Thanks.

(2,008)

Posts: 2,531

Date of registration
: Jul 25th 2013

Platform: PC

Battlelog:

Reputation modifier: 14

  • Send private message

10

Thursday, April 20th 2017, 7:09pm

There are many elements of Frontlines that should be implemented into Conquest. Some would say Frontlines is a straight upgrade to Conquest because it's actually a balanced gamemode. That's why matches can run on for hours and hours; it's an indication that the mode actually works properly. We can see Conquest does not experience the same most of the time.


Hmm, while I do enjoy Frontlines, I do not think it is a particular balanced or well implemented mode at all. People enjoy it for the lack of vehicles and planes in particular as well as a more infantry dominationesque gunplay, with less players but still a lot of engagements. A long round is not indicative of a well balanced match or thought out gamemode either. Maps like Soissons in particular just have little room for winning. B flag is just incredibly hard to take, and the MCOMs on that side also make it hard to push onto. The long rounds really show the flawed map design. The mode is also pretty mindless and brute-forces even more the "get to tha objective" doctrine of conquest, as capture zones are still cramped and back capping is not enabled.

It is true though that teamstacking and the obscure auto-balancer is indeed very likely the cause for fast rounds. Since stacking your teammates on the cap is the only thing that counts and with a high TTK flanking maneuvers or fast offenses to hinder people from entering the zone or holding them back is not a decisive tactic. I think the mode would have worked better in BF4.

I agree with tankmayvin. BF1 and BF4 as well was bloated with irrelevant features and modes, while the vast majority of players only play a certain amount of modes and maps. Feature creep is the term, right? So in BC2 everybody played Rush and a little Conquest, it was the other way around in BF3 and by BF4 all everybody ever played was Conquest.
This is a major issue, because you need maps that work in any mode and playercount, that is why every map has a distinct infantry only area in BF4, which is also why maps like Dragon Valley, Silk Road and Karelia on Conquest are awful to play as Infantry. Also the maps need to work from 32-64 players, which is just not doable, you have Locker and Metro on one end and Dragon Valley and Fu-She Pass on the other.
It is particularly bad with Rush though, and Operations, too I guess, because you need a rather large and long area to play in that offer asymmetric but fair and fun opportunities for both teams, but are really susceptible to player counts.

My suggestion is the same, kill the modes, kill the different playercounts. Focus on the simple core, like Battlegrounds did. For BF I would say Rush and Conquest, let variation come in by the maps. I do not think anyone would complain if infantry and vehicles worked on every map, but we only had three conquest maps and three rush maps if they worked well and catered to everyone. You could still have maps without vehicles and maps with more of them, but keeping each one relevant is the key.

Edit: What a long post again. :D