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.

## Improving class role effectiveness: Increasing the availability of both fundamental player to player interactions as well as situational gadgets. (Suggestion)

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

Posts: 2,015

Date of registration
: Jan 12th 2014

Platform: PC

Battlelog:

Reputation modifier: 14

Friday, May 19th 2017, 1:47am

### Quoted from "BleedingUranium"

This is something I've brought up numerous times now. Vehicle damage (and repair) points need to be based on raw HP, not percentage-of-HP. Instead of 15, it would be 150. Infantry kills are 120 in total for a full kill (100 plus 20 bonus for the kill), and vehicles should be the same, so 1200 for a solo vehicle destroy. 750+ points would be an Assist Counts As Kill, with a 100 assist bonus.

Other teamplay actions should go up to match. Health is pretty good as-is, but spotting, Scout-spotting, suppression, and even ammo points need to go up. A single infantry kill should be one of the lowest-scoring things you can do, not only because a single kill in a BF game is fairly meaningless, but also to help encourage other actions, partly because people don't need encouragement to get kills in an FPS.

Eh?

A single infantry kill is worth way more, and is way harder than healing back 80 HP or giving someone a couple of grenades.

Salt Miner

Posts: 3,674

Date of registration
: Mar 19th 2014

Platform: Xbox One

Battlelog:

Reputation modifier: 16

Friday, May 19th 2017, 4:51am

### Quoted from "tankmayvin"

Eh?

A single infantry kill is worth way more, and is way harder than healing back 80 HP or giving someone a couple of grenades.

As I said, that's only part of it, how much various acts both should be or need to be encouraged is also a major factor. Kills are at the very top of the list of things that need little encouragement, it's simply what people do in shooters.
Who Enjoys, Wins

Posts: 292

Date of registration
: Dec 2nd 2013

Platform: PC

Location: California

Battlelog:

Reputation modifier: 10

Friday, May 19th 2017, 7:51am

### Quoted from "NoctyrneSAGA"

Also there is a very easy way to tell if what you're doing is contributing to your team's success.

You look at the score. If you are winning, in all likelihood you are doing something right.
This is the same justification used by the people who are on the winning team with an 18-4 score as Scout, but #21 on their team, spending the entire match sniping from shitter peak 150m away from any objective where their gadgets weren't of any use. No, you didn't do jack shit to accomplish victory, and if you were on the losing team your KDR and score would be more accurately reflective of your actual contribution to the team. Now replace that Scout with a Support doing nothing but firing mortars, an Artillery Truck or Heavy Tank that refuses to advance, that one guy who stays in the Fortress Cannon at the gimme flag all game, etc

I love the way Sun Tzu is twisted to legitimize running meme setups like Airburst Mortar/Frag Xbow, or Rifle Grenades over health or syringe. Tankmayvin once again hit the nail on the head; your own killing effectiveness may be (and that's a huge "may be") bolstered, and killing is just as important to help achieve victory as supporting teammates. But you also lose gadgets that not only directly buff your own combat effectiveness (ammo, health), but also the fighting effectiveness of your nearby teammates. You're presuming that people replacing "teamplay" (and I put "teamplay" in quotes, because they also serve to benefit you) with "non-teamplay" gadgets are just as effective as accomplishing the same task in a different way, by supposing hypothetical situations where your indirect fire gadgets would've killed an enemy and prevented loss of life in the first place.

What actually happens in regular in-game pubs? I think that's the real question that needs to be asked. Just as much as other "game theories" that actually need to be shown in-game to witness how flawed they are, like the Behemoths being a fighting game "rage" mechanic. Or Ammo 2.0 shown in its fullest, as BU said.

PvF 2017 Champion

Posts: 7,285

Date of registration
: Apr 3rd 2012

Platform: PC

Battlelog:

Reputation modifier: 19

Friday, May 19th 2017, 8:31am

What makes the Behemoth flawed? The only problems with it right now are that most drivers are idiots that don't know how to properly leverage it and that its spawn logic isn't really doing a good job of figuring out how badly it is needed.

Also how does extra damage not benefit your teammates? Especially if they're running healbot set-ups that reduce their damage output. Someone has to make up the loss in damage somehow. There is nothing theoretical about the damage you bring with 2 damage utilities versus a teammate bringing just 1 damage utility and 1 replenishment utility. Or versus a teammate bringing no damage utilities whatsoever.

The point I've been repeatedly trying to make is that damage is a team utility that shouldn't be dismissed just because it doesn't interact directly with teammates. That's just plain silly. Nor is saving a teammate's life the only application of extra damage. The more you send enemies to the respawn screen, the less they are able to get anything done. You create gaps in their map presence that your teammates can exploit.

The part about Sun Tzu was to address VincentNZ basically saying that an action that gets recognition is worth more than an action that goes unrecognized. Recognition is irrelevant to an action's value.

Seeing as how the team with the "useless" backliner is still winning, they aren't detrimental enough to be a problem. Who knows, they might actually be helpful by deleting enemies before they get anything done.

I see a lot of people demanding that blueberries conform the to conventional ideas of how the game should be played (and sure there is nothing wrong with playing conventionally) but I don't see people trying to play around the strategies that the "meme" loadouts are creating.

Sure if the backliner isn't getting anything done, then they're useless. But that's not a problem with the playstyle that's a problem with the player.

For all the complaints leveled against backliners for not helping capture objectives, I'm pretty sure that there are backliners out there bemoaning the frontliners that are too scared to enter a cleared out flag. I know I've felt that way.
Data Browser

Passive Spotting is the future!

"Skill" may indeed be the most magical of words. Chant it well enough and any desire can be yours.

Are you a scrub?

### Quoted from "blahdy"

If it flies, it dies™.

This post has been edited 3 times, last edit by "NoctyrneSAGA" (May 19th 2017, 9:12am)

Posts: 292

Date of registration
: Dec 2nd 2013

Platform: PC

Location: California

Battlelog:

Reputation modifier: 10

Friday, May 19th 2017, 10:11am

### Quoted from "NoctyrneSAGA"

What makes the Behemoth flawed? The only problem with it right now is that most drivers are idiots that don't know how to properly leverage it.

You've already listed one reason why Behemoths are flawed, and wildly inconsistent.

Let me ask another rhetorical question again: How many times have you seen a Behemoth leverage a significant impact on the outcome of the match, like the rage mechanic from fighting games?

### Quoted

Also how does extra damage not benefit your teammates? Especially if they're running healbot set-ups that reduce their damage output. Someone has to make up the loss in damage somehow. There is nothing theoretical about the damage you bring with 2 damage utilities versus a teammate bringing just 1 damage utility and 1 replenishment utility. Or versus a teammate bringing no damage utilities whatsoever.

Because you are equating 2 damage utilities with twice the damage effectiveness, or that damage and utility are zero sum choices that have to be consciously made on behalf for your team. We are suddenly supposed to believe that a Support's overall utility is just as useful when he runs Mortar/Xbow instead of Ammo/Mortar or Ammo/Xbow, when Assaults and Scouts are begging for gadget replenishment to do their jobs. (In before "muh Ammo 2.0 was supposed to fix that!")

Realistically, running both Airburst Mortar and Frag Xbow at the same time, or Rifle Grenades over health/syringe, is not going to make that much of a significant difference over getting enemies killed and sent back to respawn. If teammates are running heal/ammo slut setups, they indirectly increase the fighting capabilities of your team. You know what's just as useful or even more so than Rifle Grenades? Getting 1, 2, even 4+ teammates topped off on their HP and reviving them back from the dead so they can fight for you. You know what actually kills everything much more efficiently than running dual Airburst and Fragbow? Topping off Scout flares so you can figure out where enemies are, and giving Assaults more AT resupplies to harass both infantry and tanks.

The notion that pure damage utility is viable because someone else will make up for the lack of replenishment utilities doesn't actually pan out well in reality, because replenishment utility is ALWAYS appreciated and utilized, and damage utility isn't always capable of accomplishing its task meaningfully. This is even worse when Supports run double damage utility gadgets, when 1 is usually already enough to get the job done. The "Missing ammo/health? Sorry, I'm not **that** guy!" concept is what frustrates people who want consistency from classes that are specifically designated to support others, but they're also given the freedom to eschew that completely. Kind of why I think Rifle Grenades and Repair Wrench should be swapped between Support and Medic, Support and Medic being restricted to always carry 1 "teamplay" gadget like in BF3, bringing back Hardline's "interact to receive health/ammo", but these are all ideas I'll elaborate upon later.

### Quoted

I don't see people trying to play around the strategies that the "meme" loadouts are creating.

I don't really find "meme" loadouts that aggravating to play against, since the people who run them are mostly bad players, or they're being used in response to their team losing badly. It's more playing around them when they're on your team is is my beef, for reasons I've already said.

### Quoted

Seeing as how the team with the "useless" backliner is still winning, they aren't detrimental enough to be a problem. Who knows, they might actually be helpful by deleting enemies before they get anything done.

The original argument was over the useless backliner "doing something right," not being "detrimental enough to be a problem." They're not the same thing.

I don't think dingleberries or anyone should be told how to play the game. In fact, that's one of the biggest reasons why the Battlefield franchise is fun. You want to play hard and run and gun between objectives? Go ahead. You want to backline and snipe/mortar at a leisurely pace? Feel free to do that. You want to spend the entire round focusing on ruining the game for those people who do nothing but snipe/mortar from shitter peak, sit on a hill with the tank, or squat the gimme flag's Fortress Gun, objectives and team score be damned? I do that all the time, more than I care to admit.

What people don't get a free pass on is grossly overstating their actual usefulness and impact on a game.

### Quoted

Sure if the backliner isn't getting anything done, then they're useless. But that's not a problem with the playstyle that's a problem with the player.

For all the complaints leveled against backliners for not helping capture objectives, I'm pretty sure that there are backliners out there bemoaning the frontliners that are too scared to enter a cleared out flag. I know I've felt that way.

You seem to think that I'm against backlining in general. There's nothing inherently wrong with backlining, you're confusing backlining that actually makes a meaningful impact vs terrible players that are too scared to do anything. Or that backlining and frontlining are mutually exclusive and can never be done together in a single game or lifetime.

If there's a tank or Scout that provides overwatch for his squad across multiple objectives by keeping an eye on spawnpoints, that's backlining.

If there's a tank or Scout that absolutely refuses to budge from the mountain overlooking C on Empire's Edge the entire game, that's also backlining. Now which player is more useful?

And if a frontliner is too scared to enter even contested flags that backliners are watching... then they're not frontliners, are they? Or if the backliner is complaining that nobody wants to enter an empty flag, what's stopping him from capturing the flag himself? It's hilarious how Artillery Trucks and Scouts openly complain in chat how their team is too stupid to capture points, but they themselves are allergic to flags like Genji to the payload.

Posts: 3,292

Date of registration
: Apr 26th 2013

Platform: PS4

Location: Arizona, USA

Reputation modifier: 15

Friday, May 19th 2017, 10:22am

>Mfw Scouts and Artillery Trucks are meant to cap flags
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