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

Praetor Rampage (2) #3261

Closed
Jedirev opened this issue Jun 12, 2024 · 4 comments
Closed

Praetor Rampage (2) #3261

Jedirev opened this issue Jun 12, 2024 · 4 comments
Labels
Battlescribe Only This issue is not reproducible in new recruit bug

Comments

@Jedirev
Copy link

Jedirev commented Jun 12, 2024

Describe the bug
Legion Praetors of any legion appear to have picked up Rampage (2). (Cataphractii and Tarts don't have the issue.)

To Reproduce
Create a new list
Add a Legion Praetor
View the list

Expected behavior
Legion Praetors shouldn't have Rampage.

Device and data (please complete the following information):

  • OS: Android
  • App: Battlescribe
  • App version: 2.03.27
  • Data release version: 19.0.4
@Jedirev Jedirev added the bug label Jun 12, 2024
@nstephenh
Copy link
Contributor

This looks configured in the data properly, and new recruit is handling it fine, but battlescribe is not respecting the hidden flag.
image

For now, I'd recommend not using battlescribe and switching to new recruit.

@nstephenh nstephenh added the Battlescribe Only This issue is not reproducible in new recruit label Jun 12, 2024
@Mayegelt
Copy link
Contributor

BS hates Hidden is false on linked rules that the rule that it is linked to is not hidden.

@nstephenh
Copy link
Contributor

To fix this we should just invert all the logic so it's shown by default and we hide it. Very annoying.

@Mayegelt
Copy link
Contributor

Mayegelt commented Aug 8, 2024

Just required the logic reversal on the Praetor option
Will be fixed in #3302

Mayegelt added a commit that referenced this issue Aug 8, 2024
@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 8, 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
Battlescribe Only This issue is not reproducible in new recruit bug
Projects
None yet
Development

No branches or pull requests

3 participants