incorrectly named function in LSML code 'canDoubleFire'
sestrand opened this issue · comments
LSML version: 2.0.14
Screen resolution: 3440x1440
Java version: 8u330
In the lsml code, canDoubleFire() in BallisticWeapon.class returns true if jamming chance is not zero. this is not really the definition of the value and I think it has lead to some potential misinterpretation or misuse in the code in other spots. I do not think we can guarantee that jamming chance will always be >0 for all UACs. and in the code, RAC behavior is tied to this being true as well... I think this boolean should have a different name...
canDoubleFire() is also potentially incorrect both for which class it is applied to and the name itself. While the value in the PGI files for ShotsDuringCooldown currently sits in only autocannons and always has a value of 1... this does not mean PGI will leave it as 1. or just to UACs.
