Opened 11 years ago
Closed 9 years ago
#33 closed enhancement (fixed)
Add centralised requirement checker
Reported by: | ibboard | Owned by: | ibboard |
---|---|---|---|
Priority: | major | Milestone: | WarFoundry API 0.2 |
Component: | WarFoundry-API | Version: | Unknown or N/A |
Keywords: | Cc: | ||
Blocked By: | Blocking: | #35, #36, #104 |
Description (last modified by )
For improved plugability, requirements should be checked through a centralised "requirement handler". This would allow better handling of Warhammer 40K's roster-style or Warhammer's numbers based on army size restrictions through plugins by giving a central point to add the requirements to. It would also separate out "one blob, one job" functionality by removing functions like CanAddToArmy
from classes like UnitType
.
Change History (11)
comment:1 Changed 11 years ago by
Blocking: | 35 added |
---|
comment:2 Changed 11 years ago by
Blocking: | 36 added |
---|
comment:3 Changed 11 years ago by
Owner: | ibboard deleted |
---|
comment:4 Changed 10 years ago by
Blocking: | 104 added |
---|
comment:5 Changed 10 years ago by
Milestone: | WarFoundry 0.1 → WarFoundry 0.2 |
---|
Move some tickets to v0.2 milestone
comment:6 Changed 10 years ago by
Status: | new → confirmed |
---|
Move tickets to new "confirmed" status to show that they've been checked
comment:7 Changed 9 years ago by
Milestone: | WarFoundry 0.2 → WarFoundry API 0.2 |
---|
Separate API milestone from UI milestone
comment:8 Changed 9 years ago by
Description: | modified (diff) |
---|---|
Summary: | Add centralised requirement handler → Add centralised requirement checker |
Version: | → Unknown or N/A |
comment:11 Changed 9 years ago by
Owner: | set to ibboard |
---|---|
Resolution: | → fixed |
Status: | confirmed → closed |
In [927]:
Note: See
TracTickets for help on using
tickets.
Remove owner so that the team can more easily see bugs. Using default owners seems good at first but is bad practice when a team can be working on any part of the project.