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

Date of registration
: Jun 9th 2012

Platform: PC

Battlelog:

Reputation modifier: 10

  • Send private message

231

Tuesday, March 14th 2017, 1:35am

From what I have seen about Frontlines, it is just a king of the hill gamemode that have different points/telegraph to capture/arm. The defenders don't get time to setup, nor do the defenders have a spawn advantage for the telegraphs like in previous rush. Not interested at all.

Posts: 2,014

Date of registration
: Jan 12th 2014

Platform: PC

Battlelog:

Reputation modifier: 14

  • Send private message

232

Tuesday, March 14th 2017, 1:56am

2/4 infantry maps?

Best fucking DLC ever, holy shit
Aftermath? Those technicals didn't count.


Afermath was definitely the best DLC ever made for any battlefield.

i don't know, i actually liked bc2 vietnam a lot, but for different reasons... in terms of maps, b2k and aftermath were definitely some of the best in terms of dlc, while bf4 dlcs were.... ok, i guess? in general battlefield's dlc maps have never been all that great, but this one seems to be turning out ok even though soissons is cancer gameplay-wise.
Vietnam was fucking amazing though, I mean minus the tear inducing awfulness of the tank flamethrower and the paper helicopters.

I really enjoyed the BF4 DLC, the second assault imports and the China rising vehicle maps in particular. Also the hover tank was the shit. All but the titan map were great.

  • "JSLICE20" started this thread

Posts: 3,292

Date of registration
: Apr 26th 2013

Platform: PS4

Location: Arizona, USA

Reputation modifier: 15

  • Send private message

233

Tuesday, March 14th 2017, 2:15am

From what I have seen about Frontlines, it is just a king of the hill gamemode that have different points/telegraph to capture/arm. The defenders don't get time to setup, nor do the defenders have a spawn advantage for the telegraphs like in previous rush. Not interested at all.

Now hold on just a minute, I didn't get that impression at all from the clips I saw and linked. And no team is truly on the defensive, that is until the Telegraphs in the HQ but even then a team previously on the defensive can steal the momentum and push the opposing team all the way to their HQ. It's all about momentum, which is consistent in that of many sports like American Football, Football (Soccer), or even Basketball. But if you don't like it, you don't like it; that cannot be disputed. I just don't agree with why you don't like it.
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: 281

Date of registration
: Jun 9th 2012

Platform: PC

Battlelog:

Reputation modifier: 10

  • Send private message

234

Tuesday, March 14th 2017, 2:46am

Maybe my understanding is wrong, but say there are ABC 3 capture points. Team on the A side captured B. Now B is uncap-able, but C is also uncap-able and unspawnable, for 30 seconds or so. Team on the C side now has to spawn at the telegraphs. Isn't that like a dynamic KotH? And what does it have to do with momentum?

Posts: 7,809

Date of registration
: Feb 25th 2012

Platform: PC

Location: italy

Battlelog:

Reputation modifier: 19

  • Send private message

235

Tuesday, March 14th 2017, 4:13am

Maybe my understanding is wrong, but say there are ABC 3 capture points. Team on the A side captured B. Now B is uncap-able, but C is also uncap-able and unspawnable, for 30 seconds or so. Team on the C side now has to spawn at the telegraphs. Isn't that like a dynamic KotH? And what does it have to do with momentum?

it's war of attrition, afaik, only 1 flag is available at a time.
"I'm just a loot whore."


stuff mostly unrelated to BF4 that interests nobody



bf4
on 13/05/2016
23rd M320FB user on pc(13/05/16)
rush mode score RANK:2794 TOP:2% OUT OF:215398
obliteration mode scoreRANK:994 TOP:1% OUT OF:159466
handgun medals RANK:2236 TOP:2% OUT OF:143874
longest headshot RANK:9512 TOP:4% OUT OF:257589
recon score RANK:10871 TOP:4% OUT OF:274899
general score per minute RANK:10016 TOP:4% OUT OF:294774

bf3
31/3/2012 4:58:

Headshot distance RANK:493* TOP:0%
Revives per assault minute RANK: 6019 TOP: 3%
Headshots / kill percentage RANK:25947 TOP:13%
MVP ribbons RANK:18824 TOP:11%

*= 6 if we not count the EOD BOT headshots

@kataklism

ARGUMENT DESTROYED 100

ENEMY KILLED [REASON] JSLICE20 100


WRITING SPREE STOPPED 500

link to full-size old avatar:
http://i.imgur.com/4X0321O.gif




  • "JSLICE20" started this thread

Posts: 3,292

Date of registration
: Apr 26th 2013

Platform: PS4

Location: Arizona, USA

Reputation modifier: 15

  • Send private message

236

Tuesday, March 14th 2017, 4:22am

Maybe my understanding is wrong, but say there are ABC 3 capture points. Team on the A side captured B. Now B is uncap-able, but C is also uncap-able and unspawnable, for 30 seconds or so. Team on the C side now has to spawn at the telegraphs. Isn't that like a dynamic KotH? And what does it have to do with momentum?

No, I think you got it but each objective is spaced out evenly by the looks of it, so no team has a distance advantage. And since flag B becomes un-cap-able or un-spawn-able once flag A has been taken, the team contesting flag B, who now has to fall back to defend an imminent advance, has an opportunity to reach flag C before the 'attacking' team does. Then once either side takes flag C, flag B begins to unlock or the Telegraphs become available. Whichever team has more momentum or whichever team steals the momentum will win the objective.
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" (Mar 14th 2017, 4:44am)


Posts: 281

Date of registration
: Jun 9th 2012

Platform: PC

Battlelog:

Reputation modifier: 10

  • Send private message

237

Tuesday, March 14th 2017, 5:25am

Maybe my understanding is wrong, but say there are ABC 3 capture points. Team on the A side captured B. Now B is uncap-able, but C is also uncap-able and unspawnable, for 30 seconds or so. Team on the C side now has to spawn at the telegraphs. Isn't that like a dynamic KotH? And what does it have to do with momentum?

No, I think you got it but each objective is spaced out evenly by the looks of it, so no team has a distance advantage. And since flag B becomes un-cap-able or un-spawn-able once flag A has been taken, the team contesting flag B, who now has to fall back to defend an imminent advance, has an opportunity to reach flag C before the 'attacking' team does. Then once either side takes flag C, flag B begins to unlock or the Telegraphs become available. Whichever team has more momentum or whichever team steals the momentum will win the objective.

I am a little bit confused by your explanation. How does all 3 flags come into play? Aren't there only two flags involved for every transition?

  • "JSLICE20" started this thread

Posts: 3,292

Date of registration
: Apr 26th 2013

Platform: PS4

Location: Arizona, USA

Reputation modifier: 15

  • Send private message

238

Tuesday, March 14th 2017, 6:07am

I am a little bit confused by your explanation. How does all 3 flags come into play? Aren't there only two flags involved for every transition?

Yes, one flag locks while another unlocks after what looks like 30s. Once the flag has finished unlocking it is the only objective available to capture. In my mind that's essentially what I wrote, but my mind can overcomplicate things...
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


VincentNZ

Holy War? No Thanks.

(2,248)

Posts: 2,660

Date of registration
: Jul 25th 2013

Platform: PC

Battlelog:

Reputation modifier: 15

  • Send private message

239

Tuesday, March 14th 2017, 5:17pm

So I assume the assignments for the Chauchat and the RSC are a typo? 15 headshots in one round? I just checked my .35 stats and am proud to say that my HS (I assume it is HSK), is somewhere between 10-15%. Surprisingly it is the same fort he Benet-Mercier (Telescope). Am I leaning myself out of the window in saying that these two classes are not particularly meant for relying on headshots? Then again to unlock the Lebel Rifle you need five HS with the Russian 1895, which does seem doable.

However even five headshots with the Benet-Mercier and .35 seems rather unlikely. I like it when assignments are a bit harder and fun to do, like unlocking the L85 in BF4, with a Defi kill, but this is just dull and rather impossible. Opens the gates for farmruns, which is what people hated about assignments in the first place.

Gecko99

thank mr skeltal

(454)

Posts: 214

Date of registration
: Dec 17th 2016

Platform: PC

Location: Kauai

Battlelog:

Reputation modifier: 3

  • Send private message

240

Tuesday, March 14th 2017, 6:00pm

Must be a typo, in the CTE it was only 15 kills in a round, not 15 headshots.
Autoloading 8 .25 extended user.