CCP Wolfman wrote:Hi
We are currently testing an update to the TAC AR and we hope to release it next week. The changes being tested include a smaller clip size, increased hip-fire dispersion to make it less effective in CQC and a lower ROF. WeGÇÖre not aiming to nerf hammer it so weGÇÖll monitor the weapon carefully after that to see the impact of the change.
CCP Wolfman
Full disclosure up front - I am/was a TAC user, but unlike most, I agree that a nerf was needed. That being said, the gun was rendered instantly unplayable, as the nerfing went too far, and in the wrong direction.
So... 3 main things changed.... Clip Size, Rate of Fire, Hip Fire Spread.
Damage, recoil and range were unchanged.
Logically, it makes no sense to put the hip fire spread anywhere below that of an automatic AR. Automatic ARs have recoil and such, whereas the TAC is theoretically a single shot and therefore has less recoil. Also, as the TAC has a longer range, the angular deviation will only increase over distance. The fire will look like a cone... what may be a 1m wide cone 10m from the target will be a 1.2m cone 20m from the target, etc. Range naturally amplifies any deviation, so logically dropping accuracy below that of a regular AR (auto) is just silly.
Clip size.... 100% agree. Way too much damage available in that gun before a reload was needed.
Rate of Fire - Agree somewhat. My mouse finger allowed me to get way too many rounds per second, but a hard cap at 400 seems a bit low.
I was an AR user before, in Chromosome, but never picked up a TAC until Uprising. Why, you ask? Well, the answer is simple: range. The changes to sharpshooter meant that i was putting my sights over someone, but inflicting no damage to the range hard cap. It doesn't take people very long to realize that keeping range is key, and so people switched to the TAC to keep their RANGE. The Damage that people did was a nice bonus, but honestly secondary to keeping their Chromosome-level range.
EVE actually gives us a good balance example here... Javelin and Spike, two rail-gun ammos that fill two different needs.
Javelin - Higher damage shells, but much shorter range (-75% range reduction)
Spike - Lower damage shells, greatly expanded range (80% range bonus)
So... following this template, the automatic ARs, that have shorter range, should do more damage. Longer range TAC ARs should do less damage.
DPS is simply a product of RoF and raw damage scores. You can increase or decrease one stat to completely change the feel of the weapon. And unless you want to work tracking into the calculation (as there is with turrets in EVE), accuracy (i.e. hipfire spread) should remain constant.
So... here is my feedback following the TAC changes:
1 - Keep the clip size where it is for the Duvolle... but slightly higher (perhaps 20, or 22) for the GLU. It is a lower damage gun, and should therefore have more rounds.
2 - Drop the damage on TACs across the board - in the mid-70s is too high.... range should be mid 50s.... so drop a full 20 points per round. There should also be a larger gradient between the weapons... GLU should have 2-4 damage points less than the Duvolle, but have a couple extra rounds in the magazine. Duvolle should have higher damage, but fewer rounds.
3 - At the very least, return hip-fire accuracy to the same level as other ARs. Perhaps play with the accuracy of the various tiers.... GLU slightly more accurate, less damage. Duvolle less accurate, more damage.
4 - Rate of fire - Higher than the current 400, but less than the Breach's ~540. Perhaps a flat 500, hard capped to get rid of the "modded controllers", or people like me who use KB/M
Based on the above, the guns could look like this:
GLU
Damage - 54
Clip Size - 21
RoF - 510
Accuracy - 58
Duvolle
Damage - 58
Clip Size - 18
RoF - 510
Accuracy - 56.5
Anyway, that's my feedback. I'll be using either the Breach or the GEK in the mean time, but I do have to say... how you could nerf the crap out of the TAC but leave the scramblers alone is beyond me.
Also... you want game-breaking? How about the free murder taxis driving around? Where's the fix for that?