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.

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: 3,272

Date of registration
: Apr 26th 2013

Platform: PS4

Location: Arizona, USA

Reputation modifier: 15

  • Send private message

371

Wednesday, March 29th 2017, 3:19am

> Implying damage values weren't going to be adjusted if necessary
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: 3,450

Date of registration
: Mar 19th 2014

Platform: Xbox One

Location: Canada

Battlelog:

Reputation modifier: 15

  • Send private message

372

Wednesday, March 29th 2017, 6:57am

This forum looks suspiciously like reddit now. Come on guys, you're better than this.
Who Enjoys, Wins

Posts: 1,889

Date of registration
: Jan 12th 2014

Platform: PC

Battlelog:

Reputation modifier: 13

  • Send private message

373

Wednesday, March 29th 2017, 8:34am

> Implying damage values weren't going to be adjusted if necessary
Starting off with evidently bad values is:

1) Insulting/wasting our time

2) Making things an uphill battle in terms of gaining acceptance.

Under these conditions it was destined to fail.

Posts: 3,272

Date of registration
: Apr 26th 2013

Platform: PS4

Location: Arizona, USA

Reputation modifier: 15

  • Send private message

374

Wednesday, March 29th 2017, 8:51am

"Wasting our time" - They were preliminary values for the CTE to be TESTED and it couldn't even make it to that stage because whining wins when you're the consumer, apparently. No company or business can do anything that may be slightly controversial anymore for fear of the consumers acting out. That's the name of the game industry now: appeal to your playerbase no matter how ignorant they may be and do basically everything they ask for as a whole and follow every order they demand as a whole. Majority wins, unfortunately the majority of the Battlefield community is stubborn, emotional, immature, and ignorant. <s>I'm so excited for future Battlefields to suck because of the community.</s>
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


NoctyrneSAGA

PvF 2017 Champion

(9,645)

  • "NoctyrneSAGA" started this thread

Posts: 6,980

Date of registration
: Apr 3rd 2012

Platform: PC

Battlelog:

Reputation modifier: 19

  • Send private message

375

Wednesday, March 29th 2017, 9:51am

@tankmayvin

The values were also conservative to reduce complaints about potential spam

You have to play the community as much as the game

Use good values from the start and you leavevlittle room for negotiation

Play off the community expectations of a dialogue and set yourself up for the end result to be what you wanted

It seems though that the community was not interested in any negotiation or compromise
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?

If it flies, it dies™.

VincentNZ

Holy War? No Thanks.

(2,088)

Posts: 2,586

Date of registration
: Jul 25th 2013

Platform: PC

Battlelog:

Reputation modifier: 14

  • Send private message

376

Wednesday, March 29th 2017, 9:59am

Well we still get different timers for grenades and likely gadgets, too.

And then there are some things that might have not been scrapped, like min/max ammo, who knows. That does sound like a compromise to me.

Also, I would want to say this again, if you take CTE seriously, you should not feel bad for them, because it was just a test. I think it is actively hurting them to have made such a fuss about CTE in the first place.

NoctyrneSAGA

PvF 2017 Champion

(9,645)

  • "NoctyrneSAGA" started this thread

Posts: 6,980

Date of registration
: Apr 3rd 2012

Platform: PC

Battlelog:

Reputation modifier: 19

  • Send private message

377

Wednesday, March 29th 2017, 10:07am

the entire system is pretty dependent on the consistent source provided by cooldowns

Removing the core component the entire system depends on is hardly negotiation

It is ultimately just begging for the continuation of the status quo: find an Ammo Box or get fucked
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?

If it flies, it dies™.

Posts: 1,889

Date of registration
: Jan 12th 2014

Platform: PC

Battlelog:

Reputation modifier: 13

  • Send private message

378

Wednesday, March 29th 2017, 10:27am

"Wasting our time" - They were preliminary values for the CTE to be TESTED and it couldn't even make it to that stage because whining wins when you're the consumer, apparently. No company or business can do anything that may be slightly controversial anymore for fear of the consumers acting out. That's the name of the game industry now: appeal to your playerbase no matter how ignorant they may be and do basically everything they ask for as a whole and follow every order they demand as a whole. Majority wins, unfortunately the majority of the Battlefield community is stubborn, emotional, immature, and ignorant. I'm so excited for future Battlefields to suck because of the community.
The poor choice of preliminary values simply does not build confidence.

I didn't need to playtest to know that the AT gadget changes were not a net improvement for either the infantry or the vehicles. The problems with the RG aren't solved by a floating ammo pool whose quality is tied to a supply of ammo. Getting sent to the respawn screen to try again works perfectly fine as a mechanic and it ensures that you will face an increasingly easy fight with a full ammo load vs a somewhat damaged tank.

The entire premise that a mix of support and assault should be better at tank killing than n+1 assaults is flawed concept and should die.

The support class is already hugely and decisively relevant to vehicle combat because they repair friendly vehicles. 1 support repairing 1 tank can let something like a breakthrough solo 2 enemy 1 man tanks - how is that not decisively powerful? It's a hell of lot more powerful than dropping ammo and herpa-derping away.

Support doesn't need to be decisive on both ends of the equation.

And why the hell should medic be relevant in fighting tanks? They've already got the two most powerful abilities in the game, and the best general purpose weapon.

Bad values + flawed premise = design failure. If they want to fix grenade spam, fix grenade spam.

Posts: 1,889

Date of registration
: Jan 12th 2014

Platform: PC

Battlelog:

Reputation modifier: 13

  • Send private message

379

Wednesday, March 29th 2017, 10:30am

@tankmayvin

The values were also conservative to reduce complaints about potential spam

You have to play the community as much as the game

Use good values from the start and you leavevlittle room for negotiation

Play off the community expectations of a dialogue and set yourself up for the end result to be what you wanted

It seems though that the community was not interested in any negotiation or compromise
Yeah, because we are 6 months into a game that is short on fun, and now they are fixing something that isn't really broken.

The whole grenade spam thing is basically just a Fort Vaux and Argonne issue anyway.

VincentNZ

Holy War? No Thanks.

(2,088)

Posts: 2,586

Date of registration
: Jul 25th 2013

Platform: PC

Battlelog:

Reputation modifier: 14

  • Send private message

380

Wednesday, March 29th 2017, 10:34am

Yeah but he will elementally disagree, I said ammo was rarely an issue, because of death mostly and finding an ammo crate wasn't either. Also you could always look for a suport player and hit him with an axe.

With the new system they would have shifted the focus from looking for a support, to the support looking for the guys to resupply them so they could do their job again. I still think the way to go is to buff the ammo crates and pouches to allow a mobile and therefore constant resupply, to not break the flow of the game.
It does also help with balancing potentially very strong gagdets, like the K-Bullet.