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

Custodes hetaeron guard unit size displaying incorrectly when vexilla and sentinel blade selected #3165

Closed
Sera-A-H opened this issue Mar 31, 2024 · 3 comments
Labels

Comments

@Sera-A-H
Copy link

Describe the bug
Custodes hetaeron guard unit size displaying incorrectly when vexilla and sentinel blade selected - choosing vexilla and SB adds an additional +1 to unit size, but the points remain correct (Bug appearing specifically on NewRecruit)

To Reproduce
Steps to reproduce the behavior:

  1. in a legio custodes detachment, add a unit of hetaeron guard
  2. add an additional guard up to 4, which currently reads correctly
  3. change weapon selection from meridian swords to "vexilla and sentinel blade"
  4. points cost increases by expected 20pts, but squad sizes erroneously increases by 1 (up to 5)

Device and data (please complete the following information):

  • iOS, Safari
  • Site: New Recruit
@Sera-A-H Sera-A-H added the bug label Mar 31, 2024
@Mayegelt
Copy link
Contributor

Mayegelt commented Aug 8, 2024

This seemed to have been resolved at some point.

@Mayegelt Mayegelt closed this as completed Aug 8, 2024
@The4D6
Copy link
Collaborator

The4D6 commented Aug 8, 2024

Is this issue fixed but not released? It still appears to be present on new recruit

@The4D6 The4D6 reopened this Aug 8, 2024
@Mayegelt
Copy link
Contributor

Mayegelt commented Aug 9, 2024

Misunderstood the display issue. Got a fix now put up in #3302
It seems that the 5 weapon options were also being classified as "Model" rather than upgrade.

@Mayegelt Mayegelt added the Done (in PR) but not on Release Branch This fix is awaiting a PR in to the Release Branch but could benefit from additional testing/input. label Aug 9, 2024
@Mayegelt Mayegelt removed the Done (in PR) but not on Release Branch This fix is awaiting a PR in to the Release Branch but could benefit from additional testing/input. label Aug 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants