Difference between revisions of "Ability Object TODO List"
(New page: {| align="right" | __TOC__ |} =Introduction= The original list of tasks required to implement the Ability object, as listed by Devon Jones, and their current statuses are: # We take...) |
(No difference)
|
Latest revision as of 16:13, 3 September 2008
Contents |
Introduction
The original list of tasks required to implement the Ability object, as listed by Devon Jones, and their current statuses are:
- We take the feat object, rename it "Ability" (Done)
- Add a tag to it called category. (FREQ 1262306 - Done)
- Add a new file type to pcc that does "ABILITY:" while we alter the "FEAT:" loader to automatically set the category to "FEAT" if it's loaded in the feat file. (FREQ 1262309 - Done)
- Then, we alter the interface for feats to only display Ability objects with the FEAT category. (FREQ 1262311 - Done)
- Alter ADD:FEAT, and FEATAUTO and such so that they can only add objects of category feat. (FREQ 1262313 - Done)
- Create a new set of tags, that are all exactly like the FEAT tags (ADD:ABILITY, ABILITYAUTO, etc) except instead of just the name, it will need to take in category|name so that we are able to have separate name spaces for ability objects. (FREQ 1262317 - Done)
- Alter output of Feats, the feat tags should only output ability objects of category feat. (FREQ 1262324 - Done)
- A new output token tag should be written that takes in the category name for iterating through ability objects. (FREQ 1262322 - Done)
- Document new Ability tag. (Docs FREQ 1617919 - Done)
- Add PREABILITY prerequisite tag. (FREQ 1617923 - Done)
Once these are done we are then in a position to tackle
- Ability Object: Removing fighter bonus feats (Docs FREQ 1081066 - Done)
Devon's original Ability proposal can be found in the Developer's List Archive