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: 292

Date of registration
: Jun 9th 2012

Platform: PC

Battlelog:

Reputation modifier: 10

  • Send private message

11

Friday, March 10th 2017, 3:44am

I also hate team stacking, where a squad just dominates and making the rest of the game like 27(dominating squad side) vs 20. I think if the team balancer is unable to balance the game without splitting up the squad, the squad needs to be split up. I do not believe the welfare of an elite squad (5 man) is bigger than the welfare of the rest of the players, like 59 of them. If they do not want to be split up, they should leave the game, or play as 2 and 3 on both sides and match up against each other. On the rare case that they love pubstomping, most other people don't like getting stomped, and I do not want to be on the team where the dominating squad is either because there is no one left for me to kill, leaving me just running around giving ammo/health and capping flags, which is boring. I usually leave the game or switch sides in that case.

Posts: 566

Date of registration
: Aug 27th 2013

Platform: PC

Battlelog:

Reputation modifier: 8

  • Send private message

12

Friday, March 10th 2017, 6:34am

Oh, how awful, people playing with friends to increase their chance of winning!

You have the choice to make friends or choose a different server.
Hackintosh user, european player, suppressor lover.
Latest creation

Posts: 3,292

Date of registration
: Apr 26th 2013

Platform: PS4

Location: Arizona, USA

Reputation modifier: 15

  • Send private message

13

Friday, March 10th 2017, 7:23am

Oh, how awful, people playing with friends to increase basically guarantee their chance of winning!
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: 566

Date of registration
: Aug 27th 2013

Platform: PC

Battlelog:

Reputation modifier: 8

  • Send private message

14

Friday, March 10th 2017, 3:06pm

Oh, how awful, people playing with friends to increase basically guarantee their chance of winning!


Change servers, make friends or become so good that teamstackers do not pose a threat / you can still achieve success.
Hackintosh user, european player, suppressor lover.
Latest creation

Posts: 3

Date of registration
: Feb 26th 2017

Platform: PS4

Location: Gensokyo (AL)

Battlelog:

Reputation modifier: 3

  • Send private message

15

Friday, March 10th 2017, 4:51pm

I wouldn't say that "team stacking" is an issue. If a person wants to play with friends and are somehow dominating with said friends due to teamwork, let them. Just as long as the teams are equal and fair.

Posts: 292

Date of registration
: Jun 9th 2012

Platform: PC

Battlelog:

Reputation modifier: 10

  • Send private message

16

Monday, March 13th 2017, 10:30pm

I also hate team stacking, where a squad just dominates and making the rest of the game like 27(dominating squad side) vs 20. I think if the team balancer is unable to balance the game without splitting up the squad, the squad needs to be split up. I do not believe the welfare of an elite squad (5 man) is bigger than the welfare of the rest of the players, like 59 of them. If they do not want to be split up, they should leave the game, or play as 2 and 3 on both sides and match up against each other. On the rare case that they love pubstomping, most other people don't like getting stomped, and I do not want to be on the team where the dominating squad is either because there is no one left for me to kill, leaving me just running around giving ammo/health and capping flags, which is boring. I usually leave the game or switch sides in that case.
Erm, I don't know if you guys have learned logic or you are just careless in reading, but this is a conditional statement.

Posts: 292

Date of registration
: Dec 2nd 2013

Platform: PC

Location: California

Battlelog:

Reputation modifier: 10

  • Send private message

17

Monday, March 13th 2017, 11:00pm

Why should a group of friends not allowed to play with each other just to balance teams? The onus is on the losing team to git gud and not leave the game, punishing a great squad carrying a team is a surefire way to make a significant portion of your playerbase quit permanently

Me and my friends have encountered this situation on both sides frequently. What losing players fail to do is refrain from bitching in chat, pick a different class than Scout, and start working with their team to capture objectives instead of sitting behind a corner throwing nades and refusing to budge. Punishing a MVP squad by splitting them up is not going to magically turn things around, especially with how fucking stupid BF1's Conquest ticket system is

Posts: 2,015

Date of registration
: Jan 12th 2014

Platform: PC

Battlelog:

Reputation modifier: 14

  • Send private message

18

Monday, March 13th 2017, 11:12pm

Why should a group of friends not allowed to play with each other just to balance teams? The onus is on the losing team to git gud and not leave the game, punishing a great squad carrying a team is a surefire way to make a significant portion of your playerbase quit permanently

Me and my friends have encountered this situation on both sides frequently. What losing players fail to do is refrain from bitching in chat, pick a different class than Scout, and start working with their team to capture objectives instead of sitting behind a corner throwing nades and refusing to budge. Punishing a MVP squad by splitting them up is not going to magically turn things around, especially with how fucking stupid BF1's Conquest ticket system is
Splittling my squad of friends, or even the rare squad of randos actually working together is a pretty much guaranteed to make the lot of us quit.

You can't make a game oriented around teamplay and then pushing people for being good at it.

Posts: 292

Date of registration
: Jun 9th 2012

Platform: PC

Battlelog:

Reputation modifier: 10

  • Send private message

19

Tuesday, March 14th 2017, 1:59am

I am sorry then, I misunderstood a lot of people in that they actually find stomping on a noobish team collectively is fun. I, on the contrary, take pride in helping the losing team to edge out a win, or at least try to.

Posts: 226

Date of registration
: Sep 20th 2016

Platform: PC

Battlelog:

Reputation modifier: 3

  • Send private message

20

Tuesday, March 14th 2017, 3:11am

There's really nothing you can do to address this, certainly not forcing autobalance since it would only piss me off to be randomly booted off the team playing well to a team that isn't


That's assuming a very very bad balancing algorithm. What noob would code such a thing?

What I can say is, BF1's Conquest ticket system is awful because a 100 ticket difference is a massive amount compared to previous titles. Me and my friends used to be able to join servers mid-game with a ~250 ticket deficit and say, "This is winnable, we can reverse this by capping some flags and holding it". The same deficit in BF1 means that we waste time in a losing game that is virtually unsalvageable


Yeh that's driving me nuts. On Suez yesterday I all-capped the enemy but my team was awful. I warned them if they didn't start spotting I was going to switch, several times, and then did, at 600-400 tickets. I got the opposing tank, immediately all-capped them again and we still lost.