-
Notifications
You must be signed in to change notification settings - Fork 94
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
Crusade Implementation Tracker #1527
Comments
@Dunamis55 Can you add a short description of what needs to be done in each catalogue? |
1. Each unit needs to have the following logic added to the top level entry:
2. Each Unit profile also needs logic to adjust characteristics:
3. You'll have to set up any Battle Traits that are unique to the army, which will need to be added to the Crusade Entry Group for each unit:
4. Every weapon profile on a single-model unit & on unit champion will need logic added:
Melee and Ranged weapons are different profiles, so they technically need different logic, even though it all does the same thing. 5. Allow Enhancements to be taken by CHARACTERS regardless of Detachment in a Crusade Force:
6. Root entry level needs to be linked to the GST's Order of Battle
7. If you have a specific Crusade campaign-type tracker, that would also need to be added in the above Root EntryFor Tau, this is a number of Entries that allow users to track the star systems that they conquer. The important bit here is to keep as simple as possible, so that the system isn't overwhelmed with logic. If users can just us a non-logic number, then we should aspire to leave it in the hands of the user to sort out, as long as they can enter a number somewhere for tracking. Tau example: |
Tracker for the purpose of seeing which armies currently have had Crusade rules implemented for them:
The text was updated successfully, but these errors were encountered: