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

Simplified check for armored component eligibility. #426

Merged
merged 1 commit into from
Feb 7, 2020

Conversation

neoancient
Copy link
Member

@neoancient neoancient commented Feb 7, 2020

Per TacOps, p. 282: "Any component on a unit’s Critical Hit Table can be armored except for ammunition bins, CASE and other items that have a “roll again” effect (such as Ferro-Fibrous Armor slots)."

I simplified the check to follow this rule. The current implementation leaves some things out and also includes some equipment, such as shields and spikes, which are not excluded by either the armored component rules or by their own.

Fixes #418.

@neoancient neoancient merged commit 9b1c6fc into master Feb 7, 2020
@neoancient neoancient deleted the case_armored_component branch February 7, 2020 17:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CASE/CASE II can be armored.
2 participants