-
Notifications
You must be signed in to change notification settings - Fork 565
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adds a proper warning dot to thermobaric missile direct fire #7216
Adds a proper warning dot to thermobaric missile direct fire #7216
Conversation
code stealer!!! thief!!! |
codewise: this is balance PR mark it as such, also that changelong is at least inacurate if not intentionaly deciving, change it to "adds additional warning to thermobaric missile" or such. addition wise: imagine if there was some warning about the possibility of hitting there, or wait, there is, the bloody target for it need to be there for at least three seconds before it hits there (realisticly 5 or more with flare as it does now show up for few secs after placed and laser has several seconds of preaim for the target to show up), when you willingly ignore the target and die to it, that is up to you. Instead of giving 4 seconds of warning to missile with impact range that you can clear under two seconds and can not even kill a drone on its own. even tho you take it from missile that easily had two times wider impact area... if you want to give it more warnining make it extra 1 second not 5 (3 with targeting) |
I think this is a balance PR more than anything, as there /is/ a warning for the vacuum missile already, from what I can tell you're simply extending it. Also, take it with a grain of salt as I play CAS a lot and might be biased, but imho there's already a lot of passive warning for a missile to land, if you don't want to get hit by CAS you shouldn't be standing next to CAS flares (flashing green, should be easy to spot) or lasers (also pretty obvious). This makes the BLU nearly unusable, and would probably make more sense as a removal than just nerfing it into the ground never to see the light of day again. |
Its an addition, if devs wanna pop a balance tag onto it they can and probably should do so, but cl's correct.
I steal the code, they steal old FATTY """"arguments"""", the cm cycle.
The issue is that by the time it flashes green you're already dead to this, as I said in the PR it's the only missile that's undodgeable from the warning. As for lazes you can just stop lazing the moment PO fires - that way there's no laze before the (insufficient for this missile) direct fire warning appears - same as fatty.
Maybe. I don't think there's any balance issue with using it in firemissions though so I don't wanna remove it entirely if the direct fire issue can be fixed.
It doesn't have a proper warning unlike other missiles, see above. And no, you cannot clear the area because you're pulled back into it. It also doesn't matter how little damage it does on its own, because you fire a second missile alongside it that kills anything pulled into it including t3s. |
all the people against the nerf are people who are abusing the items, curious |
cas.d.mp4they're extremely fast and don't give you much of window of opportunity to escape. before someone says "why are you hanging around a red dot", i could have been trying to melt a CAS flare and i would have suffered the same exact consequences. |
curious when you do it with warriors and and prae that you personaly buff them hmm. I am for extra warning but 4 or 6 seconds of warning is a BIT too much considering you can cross easily cross 15 tiles in that time. increasing the warning to two seconds of flashing light from one second of fleshing light is fair as I wrote. show footage with the missile warning after your change so people can compare |
I do agree the BLU probably needs a nerf, but as I've said, and should probably stop saying (this will be my last comment likely) this is just going to kill it and turn it to never use or you're bad at CAS status. |
I like idea of giving it actually proper warning, because normally you hear it 2 seconds before it hit (-1second to realize what is happening, and even if you run away you still get sucked in), so giving it long warning before it hits its very good change, however, the actuall change is little unbalanced for CAS side, because it mean you have very expensive missles that can be easy dodged, it show for 8 seconds (the moment you fire it) on open space will be too easy to spot and dodge, so to make people happy it would need one of this changes:
|
CAS Is very strong right now in my opinion, and i agree that Xenos should have proper warnings as with how it currently sucks xenos in can be destructive to say the least. Balance Approved. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just some nits
Co-authored-by: harryob <[email protected]>
Co-authored-by: harryob <[email protected]>
Co-authored-by: harryob <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
code approved
About the pull request
Stole code from #5957 to add a proper warning dot.
Explain why it's good for the game
Thermobaric is currently the only CAS direct fire missile that cannot be dodged through the warning intended to make it possible because you cannot clear the AoE before it pulls you back in. This fixes that.
Essentially the same kinda issue that caused the FATTY rocket to be removed in the past. No warning = bad.
Testing Photographs and Procedure
Screenshots & Videos
2024-09-25.18-55-02.mp4
Changelog
🆑
add: Added a warning to thermobaric missile direct fire.
/:cl: