Sniper bot buff #6606
Merged
Sniper bot buff #6606
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
must be more than gun range
The yaw speed was being set equal to the unit turn speed (90), while the actual desired stats are 70/50 yaw speed, so this is a very significant change. In terms of commit history, the 90 yaw speed dummy weapon came in a game change (aug 2017) before the balance changes to the desired yaw speeds (jan 2018).
Minimal dummy weapon setup based off the one in FAForever#6574
Aeon: 60 -> 65 Seraphim: 55/65 -> 60/70
1570 damage does less overkill against harbs/othuums, and in general lower damage and faster reload makes overkill less of an issue
Movement speed: Seraphim: 2.2/1.8 -> 2.4/1.8 Aeon: 2.4 -> 2.2 The theory is that Seraphim can engage at long range but will be slow for enough time during the reload for Aeon snipers to catch up. If they disengage with the fast mode, Aeon snipers will have a range advantage. Absolvers are also very fast and have high range, so they can be used to directly counter Seraphim snipers. In relation to Percy/Brick, this makes Seraphim snipers sniper mode speed be less of an extreme downside as you can flee better. It also introduces micro capability when using sniper mode vs bricks.
this further encourages use of sniper mode over normal mode, especially as the regular damage output of the sniper as opposed to being reserved for alpha-striking targets such as experimentals or ACUs.
Non-0 tolerance would cause them to miss their first shot during a turn/retarget, since the gun would be allowed to fire when it is not on target
|
We decided to buff speed instead of range as it would be helpful in low apm/1v1 scenarios and because it would encourage more proactive back and forth gameplay. We decided to tackle the sniper mode DPS and damage model changes in the next patch so we can have more time to discuss it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
Snipers bots are too micro-heavy and do not get enough value for their cost so they rarely get built. They used to be a powerful choice for beating Percivals/Bricks, but now they're not even viable and only firebases and T4s remain viable options.
Description of the proposed changes
Both snipers:
Firing tolerance: set to 0
This fixes them consistently missing on the first shot after turning/retargeting, especially for the Seraphim sniper which now has lower yaw speed than turn speed. For reference, hitting a size 1 brick at 70 range requires 0.41 degrees firing tolerance.
Range: Seraphim: 55/65 -> 60/70; Aeon: 60 -> 65
This partially reverts the range nerf from the most recent changes to snipers. The cost changes solved most of the issues, and the range nerf introduced too much micro and too little range to deal damage to enemy units before they catch up, so the experience was made worse. The range is only partially reverted so that Seraphim sniper mode does not outrange Ravagers (70 range).
Seraphim sniper speed in normal mode swapped with Aeon sniper: Aeon: 2.4 -> 2.2; Seraphim: 2.2 -> 2.4
This creates a more interesting interaction between Aeon and Seraphim snipers as they swap who outranges or outspeeds who, instead of Aeon always outspeeding Seraphim. Aeon has the very fast Absolver to counter Seraphim's alpha strike capability as well.
Seraphim sniper:
Sniper mode speed: 1.65 -> 1.8
Since the sniper mode speed is coded as a multiplier, it was unnecessarily nerfed by the recent speed changes. 1.65 is slower than ACU (1.7), so it is clearly excessive, and made sniper mode even more difficult to use against fast mainline units.
Turret Yaw speed: 90 -> 70 (normal mode) / 50 (sniper mode)
This is due to the aforementioned fix in the weapon code. It further emphasizes a steady, long range sniping style for Seraphim in contrast to Aeon's quick turning and more mobile firing.
The Seraphim sniper has a mini rework to make it more favorable to use the sniper mode regularly, instead of reserving it for alpha-striking experimentals and ACUs:
Normal mode and sniper mode DPS swapped: 153/132 -> 132/152 respectively
Sniper mode damage reduced, reload sped up: 2000 dmg/15.2s (132 DPS) -> 1570 dmg/10.3s (152 DPS)
This reduces for how long the sniper slows down after firing and makes it overkill Harbingers and Othuums much less (30%/28% overkill -> 2%/0%).
Testing done on the proposed changes
Additional context
Checklist