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.

## Fighter Planes + Ranken Darts: A Balancing Disaster?

Hey! If this is your first visit on symthic.com, also check out our weapon damage charts.
Currently we have charts for Battlefield 3, Call of Duty: Black Ops 2, Medal of Honor: Warfighter and Call of Duty: Modern Warfare 3

PvF 2017 Champion

Posts: 6,957

Date of registration
: Apr 3rd 2012

Platform: PC

Battlelog:

Reputation modifier: 19

Friday, April 21st 2017, 1:52am

### Quoted from "Ritobasu"

I thought a senseless appeal to authority goes against the very spirit of Symthic's discourse on gameplay balancing, but here we have an actual Battlefield Grandmaster who claims to know better than us casuals on what works for the game.

There is a difference between an Appeal to Authority where we listen to someone simply because of who they are and listening to someone who knows what they are talking about and can articulate their arguments because of it. People who know what they are talking about typically have invested a lot of time into the game and know how to play it well. Of course, this does not mean they are infallible. They still need to back up their arguments with proof instead of "I said so."

Nowhere do I claim to be a Grandmaster either.

The reason I wrote sentence is because people who have no idea what they are talking about should not be taken seriously. We call this the Dunning-Kruger Effect. People who lack the proper knowledge of a subject also lack the ability to accurately judge their proficiency in said subject. Someone who is well-versed in a subject like a Chess Grandmaster is going to be able to completely wreck someone who has no idea what they are doing both in the game and when discussing how it's played.

Of course, I can always try a different analogy. Let us say you have developed an infection in your foot. Would you rather listen to an actual doctor's medical advice or some random advice I found through 5 minutes of googling? I would hope you would listen to the person who knows what they are talking about.

### Quoted from "Ritobasu"

Conquest was completely fine before, so why was the change from the bleed style ticket system to what we have now even necessary in the first place? Again, another example of a completely unneeded and unwarranted change from the "Grandmasters" who apparently know best.

The problem with Conquest has been discussed before. Search for it if you want to find out why.

The TL;DR is that the old system was not an accurate display of the gamestate.

### Quoted from "Ritobasu"

You yourself state that people with a major flag deficit had to pump out a ridiculous amount of kills per minute in BF4 to catch up. In a system where people gain points for just having their own team's flags existing, it completely depreciates the value of holding and defending the majority of flags and discourages back capping. It goes beyond just simple killing, although that is a considerable factor right now as is.

I'm fairly certain a one flag difference led to 15.0 KPM difference. That isn't a big flag deficit.

The main point is that kills influence the score a lot. Enough to invalidate flag possession in some cases.

@tankmayvin

It is almost as if I base my point of view on what can be proven and demonstrated.

Though I'd appreciate if you can go dig up the post where I said that. I have no recollection of it.
Data Browser

Passive Spotting is the future!

With this, I'll rid MGO3 of infestation. Sans bad gameplay MGO3 will be torn asunder. And then it shall be free. People will suffer, of course - a phantom pain.

Reddit and Konami will rewrite the records... And I will be demonized in human memory. But... The thirst for good gameplay that I have planted will infest MGO3. No one can stop it now. The Rebalance Mod will unleash that thirst unto the future.

Are you a scrub?

### Quoted from "blahdy"

If it flies, it dies™.

This post has been edited 1 times, last edit by "NoctyrneSAGA" (Apr 21st 2017, 1:57am)

Posts: 1,879

Date of registration
: Jan 12th 2014

Platform: PC

Battlelog:

Reputation modifier: 13

Friday, April 21st 2017, 2:29am

### Quoted from "NoctyrneSAGA"

@tankmayvin

It is almost as if I base my point of view on what can be proven and demonstrated.

Though I'd appreciate if you can go dig up the post where I said that. I have no recollection of it.
Can't find it, sadly. Or rather don't feel like putting in the effort to pour through my post.

Either way, I'm glad that the conq ticket system, which was widely lauded here as being superior to prior titles, is now being recognized as a serious problem because it leads to lame duck situations where rounds simply cannot be turned around via a surge of map control or clever back camping. Teams that have a slight flag advantage are typically outkilling too, and are unlikely to stop out-killing.

Killing should be important to direct scoring (otherwise things like trenchie should be flat removed since it doesn't have the OHK rate to clear out flags compared to other air and thus gets depricated in utility). But flag control should also be very relevant. I don't see how you can balance bleed rates so that both conditions are satisfied.

PvF 2017 Champion

Posts: 6,957

Date of registration
: Apr 3rd 2012

Platform: PC

Battlelog:

Reputation modifier: 19

Friday, April 21st 2017, 2:32am

Well, it's the Beta version that is lauded.

Not the post-Beta one. People like to pretend the Beta one doesn't exist apparently.
Data Browser

Passive Spotting is the future!

With this, I'll rid MGO3 of infestation. Sans bad gameplay MGO3 will be torn asunder. And then it shall be free. People will suffer, of course - a phantom pain.

Reddit and Konami will rewrite the records... And I will be demonized in human memory. But... The thirst for good gameplay that I have planted will infest MGO3. No one can stop it now. The Rebalance Mod will unleash that thirst unto the future.

Are you a scrub?

### Quoted from "blahdy"

If it flies, it dies™.

Posts: 205

Date of registration
: Jun 9th 2012

Platform: PC

Battlelog:

Reputation modifier: 9

Friday, April 21st 2017, 3:38am

I need an update here. Isn't Ammo 2.0 scheduled to be implemented in some way in the April Spring patch?

Also on the topic of Conquest scoring system, it is less of a foot infection problem, but more of a subjective opinion/preference. I am not going to repeat my arguments of why I do not like the current system, but if DICE is going down the "implement what we like" path and ignoring the community on this type of issues, it does not do anything but drive the community away.

Salt Miner

Posts: 3,429

Date of registration
: Mar 19th 2014

Platform: Xbox One

Battlelog:

Reputation modifier: 15

Friday, April 21st 2017, 6:28am

### Quoted from "sid_tai"

I need an update here. Isn't Ammo 2.0 scheduled to be implemented in some way in the April Spring patch?

Also on the topic of Conquest scoring system, it is less of a foot infection problem, but more of a subjective opinion/preference. I am not going to repeat my arguments of why I do not like the current system, but if DICE is going down the "implement what we like" path and ignoring the community on this type of issues, it does not do anything but drive the community away.

New timers and such yes, but without the regen.

That's exactly it. This isn't a case of "knowing better", it's a case of claiming personal preferences as objectively superior. It's more like people claiming to be experts at enjoying music.

The classic CQ system and Beta CQ system are purely a matter of preference. This claim of the classic system "not representing the gamestate" is an extremely flimsy excuse to shoehorn in a pet project. You don't completely change/replace a gamemode over what is simply a UI issue, and to claim that as the reason is either worryingly disconnected from the game/community, or simply making excuses.
Who has fun, wins.

PvF 2017 Champion

Posts: 6,957

Date of registration
: Apr 3rd 2012

Platform: PC

Battlelog:

Reputation modifier: 19

Friday, April 21st 2017, 7:01am

### Quoted from "BleedingUranium"

it's a case of claiming personal preferences as objectively superior. It's more like people claiming to be experts at enjoying music.

CQ and Ammo 2.0 are systems. Evaluating how well the systems work and what they do is entirely possible. We can actually judge pros and cons of the systems.

A closer comparison for music is whether the chord progression, embellishments, and other music theory you have works for the style you are going for.

Though music in this context simply doesn't work for a comparison and really is just being used here for "It's an opinion! It's subjective! It's preference!"

Also, if you're trying to describe what's so great about your design, it's kind of hard to do it without talking about what it does better than the current iteration.

If you're going to argue for a position, it helps to actually talk about why it is better.

### Quoted from "BleedingUranium"

This claim of the classic system "not representing the gamestate" is an extremely flimsy excuse to shoehorn in a pet project.

Flimsy how?

### Quoted from "BleedingUranium"

You don't completely change/replace a gamemode over what is simply a UI issue,

It is not simply a UI issue. The score itself is derived from how the rules of the game work. It'd be a UI issue if the two sides were swapped or if the score failed to display.

The representation of gamestate itself was not accurate. We've been over this before.
Data Browser

Passive Spotting is the future!

With this, I'll rid MGO3 of infestation. Sans bad gameplay MGO3 will be torn asunder. And then it shall be free. People will suffer, of course - a phantom pain.

Reddit and Konami will rewrite the records... And I will be demonized in human memory. But... The thirst for good gameplay that I have planted will infest MGO3. No one can stop it now. The Rebalance Mod will unleash that thirst unto the future.

Are you a scrub?

### Quoted from "blahdy"

If it flies, it dies™.

Posts: 205

Date of registration
: Jun 9th 2012

Platform: PC

Battlelog:

Reputation modifier: 9

Friday, April 21st 2017, 10:21am

### Quoted from "sid_tai"

I need an update here. Isn't Ammo 2.0 scheduled to be implemented in some way in the April Spring patch?

Also on the topic of Conquest scoring system, it is less of a foot infection problem, but more of a subjective opinion/preference. I am not going to repeat my arguments of why I do not like the current system, but if DICE is going down the "implement what we like" path and ignoring the community on this type of issues, it does not do anything but drive the community away.

New timers and such yes, but without the regen.

That's exactly it. This isn't a case of "knowing better", it's a case of claiming personal preferences as objectively superior. It's more like people claiming to be experts at enjoying music.

The classic CQ system and Beta CQ system are purely a matter of preference. This claim of the classic system "not representing the gamestate" is an extremely flimsy excuse to shoehorn in a pet project. You don't completely change/replace a gamemode over what is simply a UI issue, and to claim that as the reason is either worryingly disconnected from the game/community, or simply making excuses.
Okay so auto-regen is removed so after your timer goes down to 0 and you touched a ammo box you get a grenade back right? Is auto-regen removed on gadget as well? or just the grenades?

Posts: 3,252

Date of registration
: Apr 26th 2013

Platform: PS4

Location: Arizona, USA

Reputation modifier: 15

Friday, April 21st 2017, 10:27am

The auto regen concept for gadgets was violently bludgeoned, maybe it'll stay for grenades but it's probably all gone. All that potential, wasted. All because the Battlefield Reddit community will fight tooth and nail to keep Battlefield in the dark ages of FPS game mechanics. Seriously, where was the hissy fit when auto regen was implemented for heals? Oh right, it's existed since the time where Internet bitching, moaning, whining, and crying at developers wasn't nearly as prevalent (or present at all) as it is today. -_-
To Aim Assist or not to Aim Assist, that is the question.

### 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

### 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

### 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