#2187 closed defect (fixed)
[PATCH] Remove EntityLimitsChanger
Reported by: | sanderd17 | Owned by: | sanderd17 |
---|---|---|---|
Priority: | Should Have | Milestone: | Alpha 16 |
Component: | UI & Simulation | Keywords: | patch |
Cc: | Patch: |
Description
The EntityLimitsChanger component is unnecessary.
Instead, the information should be present in the EntityLimits component. The base working should be with classes, and every time a new entity is made (or one is destroyed), the limit should be checked.
As extension, the limit tooltip should be extended to include the classes that are limiting the creation of that entity.
Attachments (1)
Change History (10)
comment:1 by , 11 years ago
Cc: | added |
---|
comment:2 by , 11 years ago
Cc: | removed |
---|---|
Keywords: | simple added |
comment:3 by , 11 years ago
by , 11 years ago
Attachment: | entityLimits.diff added |
---|
comment:5 by , 11 years ago
Keywords: | patch review added; simple removed |
---|---|
Milestone: | Backlog → Alpha 15 |
I opted to put it in a separate list, as IMO it wasn't nice to have a difference between <Cat>5</Cat> and <Cat><Limit>5</Limit></Cat>.
The UI is also automatically updated, and the AI can access the information.
comment:6 by , 11 years ago
Summary: | Remove EntityLimitsChanger → [PATCH] Remove EntityLimitsChanger |
---|
comment:7 by , 10 years ago
Milestone: | Alpha 15 → Alpha 16 |
---|
comment:9 by , 10 years ago
Keywords: | review removed |
---|
Note:
See TracTickets
for help on using tickets.
How the new EntityLimits could look: