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

OpenTopped logic dehardcoding for Technotypes #7

Closed
Musketmarine opened this issue Nov 11, 2020 · 0 comments · Fixed by #374
Closed

OpenTopped logic dehardcoding for Technotypes #7

Musketmarine opened this issue Nov 11, 2020 · 0 comments · Fixed by #374
Labels
Feature / Enhancement Anything new not present in vanilla/Ares

Comments

@Musketmarine
Copy link

This is a suggestion

Allow a technotype to ignore the opentopped conditions.
The conditions are OpenToppedRangeBonus, OpenToppedDamageMultiplier, and OpenToppedWarpDistance

The new logic should work as follows:
If the Opentopped Technotype has any of these flags declared on it, it will use the value declared on the Technotype, rather than as listed in [CombatDamage]. Obviously the unit will need OpenTopped=yes, and [CombatDamage]'s values will be used by default.

However if you make new flags that override the opentopped bonuses, then i'd be down for those too!

@Metadorius Metadorius added the Feature / Enhancement Anything new not present in vanilla/Ares label Nov 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature / Enhancement Anything new not present in vanilla/Ares
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants