Better formatting for general filter rules

This commit is contained in:
Yair Morgenstern
2023-11-18 22:54:39 +02:00
parent 2fd7779395
commit b55c4497d0

View File

@ -11,15 +11,23 @@ Note that all of these are case-sensitive!
## General Filter Rules
- All filters except for `cityFilter` and `populationFilter` accept multiple values in the format: `{A} {B} {C}` etc, meaning "the object must match ALL of these filters"
- For example: `[{Military} {Water}] units`, `[{Wounded} {Armor}] units`, etc.
- No space or other text is allowed between the `[` and the first `{`.
- All filters accept `non-[filter]` as a possible value
- For example: `[non-[Wounded]] units`
- These can be combined by having the values be negative filters
- For example: `[{non-[Wounded]} {Armor}] units`
- These CANNOT be combined in the other way - e.g. `[non-[{Wounded} {Armor}]] units` is NOT valid and will fail to register any units.
- This is because to the player, the text will be `non-Wounded Armor units`, which parses like `[{non-[Wounded]} {Armor}] units`
All filters except for `cityFilter` and `populationFilter` accept multiple values in the format: `{A} {B} {C}` etc, meaning "the object must match ALL of these filters"
Example: `[{Military} {Water}] units`, `[{Wounded} {Armor}] units`, etc.
No space or other text is allowed between the `[` and the first `{`.
All filters accept `non-[filter]` as a possible value
Example: `[non-[Wounded]] units`
These can be combined by having the values be negative filters
Example: `[{non-[Wounded]} {Armor}] units`
These CANNOT be combined in the other way - e.g. `[non-[{Wounded} {Armor}]] units` is NOT valid and will fail to register any units.
This is because to the player, the text will be `non-Wounded Armor units`, which parses like `[{non-[Wounded]} {Armor}] units`
## civFilter