Skip to content
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

Fix aerospace attack values for LBX autocannons #5565

Closed
wants to merge 1 commit into from

Conversation

neoancient
Copy link
Member

The AV for LBX autocannons (other than the LB2X) are incorrect. See TW, pp. 303-4.

Copy link
Collaborator

@IllianiCBT IllianiCBT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@gsparks3
Copy link
Collaborator

I seem to recall this previously causing issues with aerospace units not doing the correct amount of damage with LBX autocannons. LBXHandler.java in particular contains code (lines 67-74) that will reduce LBX attack values to 60% of their specified value. If it is preferred to have the correct values in the weapon definition files, removing that code might be best. Either way, this could use testing to confirm that aerospace units are doing the expected amount of damage with LBX autocannons after the changes.

@gsparks3
Copy link
Collaborator

Tested the Gradle artifact for the PR; I can now confirm that this causes LBX autocannons to do less damage than intended. Does seem to be following the Math.floor(0.6 * av) behavior from that bit of code in LBXHandler.java (6 * 0.6 = 3.6, floor to 3 for LBX10, 12 *0.6 = 7.2, floor to 7 for LBX20).
image

If you decide to remove the LBXHandler code and leave the adjusted weapon AVs (a perfectly reasonable choice), also fix the Silver Bullet Gauss Rifle AV, since it counts as an LBX weapon.

@Sleet01
Copy link
Collaborator

Sleet01 commented Jun 13, 2024

Pretty sure this is the way it is because we have multiple consumers of the AV values, only some of which are actually Aerospace units. Just changing the AV values won't produce correct behavior in all cases.

@Sleet01
Copy link
Collaborator

Sleet01 commented Jun 13, 2024

If you decide to remove the LBXHandler code and leave the adjusted weapon AVs (a perfectly reasonable choice), also fix the Silver Bullet Gauss Rifle AV, since it counts as an LBX weapon.

Also note that I changed the SB Gauss AV value to 15 from 9 specifically because of this code. Which has been in place for 11 years.

Was this PR submitted due to an issue, or just because the values looked wrong?

@Sleet01 Sleet01 requested a review from IllianiCBT June 13, 2024 23:40
@gsparks3
Copy link
Collaborator

gsparks3 commented Jun 13, 2024

Also note that I changed the SB Gauss AV value to 15 from 9 specifically because of this code. Which has been in place for 11 years.

That must have been where I remembered it from, I was looking for the issue report or change history for a LBX change and couldn't find anything, heh.

@Sleet01 Sleet01 self-requested a review June 15, 2024 08:42
Copy link
Collaborator

@Sleet01 Sleet01 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd like us to hold off on this unless it also includes updating the LBX handler that already lowers the AV value, as well as any other weapons currently affected by it (such as the Silver Bullet Gauss).
It may be that we no longer need to have both a full and an Aero-specific AV value, but I don't think that question has been answered satisfactorily yet.

@SJuliez
Copy link
Member

SJuliez commented Sep 4, 2024

It feels like we can close this, right?

@IllianiCBT
Copy link
Collaborator

I opted to withhold the review requested from me, as I don't know enough about the rules to make a reliable judgement call. Also, this was before I opted to avoid reviewing MM content too much due to my unfamiliarity with the codebase.

@SJuliez
Copy link
Member

SJuliez commented Sep 21, 2024

Closing this as per the above comments (seems unnecessary or at least, it would require the LBX handler to be updated)

@SJuliez SJuliez closed this Sep 21, 2024
@SJuliez SJuliez deleted the lbx_attack_value branch November 1, 2024 16:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants