Symthic Forum was shut down on January 11th, 2019. You're viewing an archive of this page from 2019-01-09 at 01:06. Thank you all for your support! Please get in touch via the Curse help desk if you need any support using this archive.
yes, that's the whole point. people don't use recon for the spawn beacons/tugs, people use recon to be a l33tqu1cksc0p1ngn0sc0ping-sniper = team is basically one man down, or five, or ten
yes, that's the whole point. people don't use recon for the spawn beacons/tugs, people use recon to be a l33tqu1cksc0p1ngn0sc0ping-sniper = team is basically one man down, or five, or ten
Sniper recon can be used well enough to make another team feel inadequate. There have been countless times in Rush where I've secured victory by stopping people from arming/ disarming when my team couldn't make it in time. There is also the psychological hate for a sniper that causes other people to
1) switch to sniper, and get into "duels" with you or
2) waste vehicular/other resources for the sole purpose of hunting you down and extricating revenge.
Both help your team greatly, as more and more people get desperate to only kill the sniper that they forget about the objective.
However most people are 1); therefore, your assertion is correct, and these vast majority of people are why the sniper recon is so loathed.
![]() |
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 |
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
Hell no
I get what you're trying to do, make the recon class more useful, but:
- taking things away from the rest doesn't improve the other, it makes it a necessity instead
- if anything, people should be "scared away" from using the recon class (in its current state). The class seems to be solely based towards making your own team lose.
If dice were to give a benefit like this to the recon, then a solution with spotting-distance might be a better option.
I.e: engis/supports can spot up to 70 meter, assaults up to 100 meter, recon up to 300 meter
This could work, IF dice would be as desperate to implement such a buff to the recon class to promote long-range spotcamping (instead of making it a useful class)
Tl;dr: hell no
I have been witness to this situation and I have instigated it as well. If you are an accurate sniper you can certainly force an assault whore to counter-snipe which is a detriment to the other team. I remember one instance on Noshahr Canals Rush where my team was receiving quite the beating and we could not escape the Carrier. No matter what forces were sent forward, we would just die on an endless loop, so I decided to snipe the camping bastards. I am efficient with a bolt action as I abused the Recon class when the game first released, so scoring multiple headshots wasn't much of an issue once I realized the bullet velocity of the rifle I was utilizing. Slowly, but surely, a large portion of their team gravitated towards the Recon class in an attempt to kill me, but this allowed the rest of my team to obtain a foothold on the docks and the blues managed a miracle arm with minimal tickets remaining. One by one I sniped three to four panicking Defenders praying for a last second disarm until *Boom* the B-MCOM detonated and our tickets were replenished. Absolutely stunned and, I imagine, frustrated beyond belief we wiped them off the next four sets of bombs and took the victory in only 5 min. after the first set. Needless to say, it was glorious.
TUGs are pretty fucking useful in my opinion. You just hate recon cause you don't know how to *properly* use it
RIP SRAWPersonally, i don't take a stance on whether or not there is a creating entity because i'm humble enough to realize, in my fucking insignificance, the concept escapes my comprehension with a lead of 9001 light years.
No. I hate that couple of players that use it and make their whole team lose because they only care about pulling off 500-meter qu1cksc0p3n0sc0p3tr1cksh0tz and because the fault for the team's failure is exclusive for them and not for the average player on the team
I have been witness to this situation and I have instigated it as well. If you are an accurate sniper you can certainly force an assault whore to counter-snipe which is a detriment to the other team. I remember one instance on Noshahr Canals Rush where my team was receiving quite the beating and we could not escape the Carrier. No matter what forces were sent forward, we would just die on an endless loop, so I decided to snipe the camping bastards. I am efficient with a bolt action as I abused the Recon class when the game first released, so scoring multiple headshots wasn't much of an issue once I realized the bullet velocity of the rifle I was utilizing. Slowly, but surely, a large portion of their team gravitated towards the Recon class in an attempt to kill me, but this allowed the rest of my team to obtain a foothold on the docks and the blues managed a miracle arm with minimal tickets remaining. One by one I sniped three to four panicking Defenders praying for a last second disarm until *Boom* the B-MCOM detonated and our tickets were replenished. Absolutely stunned and, I imagine, frustrated beyond belief we wiped them off the next four sets of bombs and took the victory in only 5 min. after the first set. Needless to say, it was glorious.
Which is exactly my point. The fuck that a significant team is switching to recon, makes them lose almost all mcoms in 5 minutes, already says enough about the class.
TUGs are pretty fucking useful in my opinion. You just hate recon cause you don't know how to *properly* use it
No. I hate how people use it only for those bolt-actions, and make their team lose.
T-UGS are good, yes. That's part of the recon kit. The bolt-actions, the "f*ck my team i got a 500 meter headshot!" weapon, that everyone apparently has to use for it is what's wrong with the class.
We've been over this before.
A recon that pushes along his squad, helping out the 2 medics and 1 engineer as they do their job, planting a beacon once they push up, and putting a T-UGS/mav/etc down whenever he has to defend an important area in a bottleneck-map is a good recon.
A sniper, however...
This post has been edited 1 times, last edit by "DaRubester" (May 10th 2013, 1:32pm)
Forum Software: Burning Board®, developed by WoltLab® GmbH
© Design by Symthic.com