This repository has been archived by the owner on Oct 27, 2023. It is now read-only.
Some death korps options are marked "collective" incorrectly. #2452
Assignees
Labels
Area: validation
Limits, modifiers, conditions and other validations
💾 Cat: Imperium - FW Death Korps of Krieg
✔ Res: merged
The solution was merged into the master branch
Comments
|
It’s not the collective itself; it’s a shared constraint. @CrusherJoe will fix it |
|
Okay, I am unfamiliar with exactly how this file is structured. Unchecking collective appeared to fix it for me. |
CrusherJoe
added
💾 Cat: Imperium - FW Death Korps of Krieg
Area: validation
CrusherJoe
added a commit
that referenced
this issue
Feb 10, 2018
|
This was indeed a weird one. Thanks for finding and reporting! |
|
This has been happening to me all the damn time, and I couldn't figure out why, lol. I thought it was something I was doing, I never realized it was a bug. |
GenWilhelm
added
the
✔ Res: merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
File/Catalogue: FW Death Korps of Krieg v35
BattleScribe version: 2.01.
Platform: Windows/iOS/Android/Mac/Linux
Dropbox: Yes/No
Description: Detailed issue description.
In the "Grenadier Storm Squad", and in the "Infantry Squad", the standard unit upgrade is marked as "Collective". This causes a bug where you have multiple instances of a squad in a roster, and modifying the number of guardsmen down in one squad also affects all the other squads in the roster.
The text was updated successfully, but these errors were encountered: