#2612 closed enhancement (fixed)
[PATCH] Allow logical combinations (and/or) in class checks
| Reported by: | sanderd17 | Owned by: | sanderd17 |
|---|---|---|---|
| Priority: | Should Have | Milestone: | Alpha 17 |
| Component: | UI & Simulation | Keywords: | patch |
| Cc: | mimo | Patch: |
Description (last modified by )
Currently, technologies is the only place where affected classes are denoted with 2D lists. Where the first dimension means OR, and the second means AND.
It's not possible to combine required classes with AND in other filters (s.a. attackability, garrisonability, ...)
I have a patch for that, allowing to use the '+'-sign in entity templates to denote AND. But I wonder if this will cause problems with the AI.
The function to check classes is a global function though. So all logic could be united this time.
This example unifies the Technology handling with the new method, and also implements it to check garrisonability.
Attachments (1)
Change History (5)
by , 10 years ago
| Attachment: | classes.diff added |
|---|
comment:1 by , 10 years ago
| Description: | modified (diff) |
|---|---|
| Keywords: | patch review added |
comment:2 by , 10 years ago
| Summary: | Allow logical combinations (and/or) in class checks → [PATCH] Allow logical combinations (and/or) in class checks |
|---|
comment:3 by , 10 years ago
| Owner: | set to |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
comment:4 by , 10 years ago
| Keywords: | review removed |
|---|
Note:
See TracTickets
for help on using tickets.
In 15294: