-
Notifications
You must be signed in to change notification settings - Fork 411
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
Magnetar Stacking Damage Penalty #2009
Comments
How it should work according to theory, after looking at data:
It should be stacking penalized, but just should be in another stacking penalty chain. |
Now, how it is implemented in pyfa. Missiles:
Missiles should be correctly calculated (magnetar is in separate stacking penalty chain). Please share full fit and skills, the value you have in pyfa and the value you see in game. Strip of irrelevant modules (those which do not affect missile damage) if you prefer to conceal the fit. It is possible that on-character proxy uses postMul to apply intermediate value to missiles and this needs to be fixed (but #159 states that it uses preMul). I'd prefer to have data for that. Guns:
Those should also show correct values (magnetar in common penalty chain). If after double-check they do not - share naglfar fit as well. Drones:
Those should also be correct |
C3 magnetar. Gun test:
In-game: 20.67x damage modifier Missile test:
In-game: 603.06 kin damage on missile, 276.1 dps Drone test:
In-game: 8.883x hob dmg mult, 263.3 dps Conclusion is that damage mod vs magnetar stacking penalty seems to be working as intended, but there might be some shenanigans with siege module. |
Another test, this time on sisi. Revelation, t1 guns, t2 siege, 3x t2 heat sinks, c2 magnetar, cap gun skill 4, t1 multifreqs EVE: 23.735x dmg mult, 2069.5 dps So, looks like at least for HAW guns stacking penalty is working like intended. |
While working on the issue, I discovered the following:
I filled bug report in CCP bug tracker - EBR-180798. |
Phoenix (t2 siege, 3x t2 BCS, 2x t1 xl cruise launchers with t1 em missiles, 1x t2 rapid torpedo launcher with rage thermal missiles), capital launcher operation skills are 1, the rest are 5. Rapid Torp Launchers:
XL cruise launchers:
So by the looks of it we have siege missile HAW bonus wrongly penalized. |
Naglfar (t2 siege, 3x t2 gyrostabs, 2x t1 haws, 1x t1 3500mm), capital gun operation skills are 1, minmatar dread skill is 1. 800mms:
3500mms:
So, for Naglfar pyfa shows correct numbers with all the modifiers (damage mods, siege, magnetar) - and looks like siege HAW bonus is still stacking penalized. |
Looks like it was an omission on our part. Damage mods use postMul for modification, siege module uses postPercent. Fixed in cecf5d7. So, to summarize:
|
@PaladinOne if you can give exact numbers - please post them here still, maybe I've missed something. |
another old throwback bug, this one back to #159...
A friend and I were testing Dreadnought fits (Naglfar and Phoenix), with a C5 Magnetar effect projected onto them. We noticed that the displayed damage numbers were a bit below where they should be. Examination of the guns' Affected By tab, and subsequently looking at /eos/effects.py indicates that the projected Magnetar Effect was being stacking penalized, which it should not be.
We then tested this explicitly in game using a Rattlesnake, with one Gecko, and 2 Drone Damage Amplifiers, in a C5 Magnetar. Strangely, for this test, PYFA gave the correct values, with no stacking penalty from the Magnetar effect. So the bug seems to specifically be affecting turrets/launchers, and not Drones.
v2.9.4, Windows 10
The text was updated successfully, but these errors were encountered: