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

Support/Update/Add Checks for the Correct Usage of the Garrison_Category and Space_Or_Garrison_Category Tags #6

Open
gruenwaldlk opened this issue Jan 22, 2021 · 0 comments
Labels
enhancement New feature or request prio2 v2.x.x
Milestone

Comments

@gruenwaldlk
Copy link
Member

Specification

[EAW/FOC] Corrected AI_Combat_Power for space invasions being ignored on special structures such as the Hypervelocity Gun and Ion Cannon which can damage units in space. This problem also seemed to ignore any secondary space structures. The AI would previously not send enough units to account for a defense with one of these structures. Additional details:

  • Space special structures are now calculated as part of the SpaceTotalUnnormalized token. We modified the Garrison_Category to be a Space_Or_Garrison_Category. So something that can be garrisoned should also not be a special space structure.
  • The XML tags <Garrison_Category> and <Space_Or_Garrison_Category> are actually the same. You can specify either one, but should only specify one, and they'll work the same for units and structures that can be garrisoned.
  • For land-based space units and space special structures you can use the <Space_Or_Garrison_Category> as a secondary category mask for the AI to determine what to bring to counter. Since Structure is not one of the matching categories in PGAICommands.lua::Set_Contrast_Values(). If <Space_Or_Garrison_Category> is empty it will default to Capital for land-based space units and space special structures.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request prio2 v2.x.x
Projects
None yet
Development

No branches or pull requests

1 participant