Difference between revisions of "New Features Requested for Release Cycle"
LegacyKing (talk | contribs) (Created page with ''''This is for Data Team to consolidate wish list items for certain release cycles''' 6.0 - None [Major Core Code Overhaul] '''6.2''' Andrew's Draft List: (Tir Requested a List...') |
LegacyKing (talk | contribs) m |
||
Line 1: | Line 1: | ||
'''This is for Data Team to consolidate wish list items for certain release cycles''' | '''This is for Data Team to consolidate wish list items for certain release cycles''' | ||
− | 6.0 - None [Major Core Code Overhaul] | + | ===6.0 - None [Major Core Code Overhaul]=== |
− | '''6.2''' | + | |
+ | |||
+ | ==='''6.2'''=== | ||
Andrew's Draft List: (Tir Requested a List) | Andrew's Draft List: (Tir Requested a List) | ||
Line 28: | Line 30: | ||
example: Eclipse has certain abilities as part of a group | example: Eclipse has certain abilities as part of a group | ||
− | Acrobatic | + | |
− | + | * Acrobatic | |
− | Action Hero | + | ** Light Foot |
− | + | ||
− | Deep Sleep | + | * Action Hero |
− | + | ** Action Hero Stunts | |
− | + | ||
− | + | * Deep Sleep | |
+ | ** Prophecy | ||
+ | ** Angst | ||
+ | ** Foo | ||
+ | |||
* 10c) We need to group things together without needing to add more OS Blocks | * 10c) We need to group things together without needing to add more OS Blocks | ||
Line 45: | Line 51: | ||
SORTORDER:x|y|z | SORTORDER:x|y|z | ||
− | x = Alphabetical (A-Z,Z-A) | + | * x = Alphabetical (A-Z,Z-A) |
− | x = List (How it's listed in the data set) | + | * x = List (How it's listed in the data set) |
− | x = GROUP | + | * x = GROUP |
− | x = SUBGROUP= | + | * x = SUBGROUP= |
− | y = Ability Name to follow | + | * y = Ability Name to follow |
− | y = Group Name (Used with Group (x)) | + | * y = Group Name (Used with Group (x)) |
− | z = optional sort numbering system | + | * z = optional sort numbering system |
LIST is debatable as that could cause issues, especially if .MODs are | LIST is debatable as that could cause issues, especially if .MODs are | ||
Line 58: | Line 64: | ||
Examples of usage: | Examples of usage: | ||
− | Dairy Strings <> SORTORDER:Group|Punk Rock|1 | + | * Dairy Strings <> SORTORDER:Group|Punk Rock|1 |
Will apply the Ability Dairy Strings as part of Punk Rock 'Group' and it | Will apply the Ability Dairy Strings as part of Punk Rock 'Group' and it | ||
will be the first item | will be the first item | ||
− | Funky Town <> SORTORDER:A-Z|Dairy Strings | + | * Funky Town <> SORTORDER:A-Z|Dairy Strings |
Funky Town will be listed in Alphabetical Order after the Ability Called | Funky Town will be listed in Alphabetical Order after the Ability Called | ||
'Dairy Strings' | 'Dairy Strings' | ||
− | Loves Rock <> SORTORDER:GROUP|Punk Rock|2 | + | * Loves Rock <> SORTORDER:GROUP|Punk Rock|2 |
− | Hates Rock <> SORTORDER:SUBGROUP=Punk Rock|Classical|1 | + | * Hates Rock <> SORTORDER:SUBGROUP=Punk Rock|Classical|1 |
There are several ways it can display with those four examples. We do need | There are several ways it can display with those four examples. We do need | ||
to establish order of operation. | to establish order of operation. | ||
− | Example 1 | + | * Example 1 |
− | Dairy Strings | + | |
− | - Funky Town | + | * Dairy Strings |
− | Loves Rock | + | ** - Funky Town |
− | - Hates Rock | + | * Loves Rock |
+ | ** - Hates Rock | ||
− | Example 2 | + | * Example 2 |
− | Dairy Strings | + | * Dairy Strings |
− | Loves Rock | + | * Loves Rock |
− | - Hates Rock | + | ** - Hates Rock |
− | Funky Town | + | * Funky Town |
This came about because of how PCGen sorts items by Type or Name. It'd be | This came about because of how PCGen sorts items by Type or Name. It'd be | ||
Line 90: | Line 97: | ||
NAME - What I'm thinking the Sort Order would be set | NAME - What I'm thinking the Sort Order would be set | ||
− | Acrobatics <> SORTORDER:GROUP|General (Defaults to A-Z sorting inside | + | |
+ | * Acrobatics <> SORTORDER:GROUP|General (Defaults to A-Z sorting inside | ||
the group) | the group) | ||
− | - Light Foot <> SORTORDER:ABILITY|Acrobatics | + | ** - Light Foot <> SORTORDER:ABILITY|Acrobatics |
− | Companion <> SORTORDER:GROUP|General | + | * Companion <> SORTORDER:GROUP|General |
− | - Template <> SORTORDER:ABILITY|Companion|1 | + | ** - Template <> SORTORDER:ABILITY|Companion|1 |
− | - Transference <> SORTORDER:ABILITY|Companion|2 | + | ** - Transference <> SORTORDER:ABILITY|Companion|2 |
− | - Might <> SORTORDER:ABILITY|Companion|3 | + | ** - Might <> SORTORDER:ABILITY|Companion|3 |
− | - Additional <> SORTORDER:ABILITY|Companion|4 | + | ** - Additional <> SORTORDER:ABILITY|Companion|4 |
− | Augment Attack <> SORTORDER:GROUP|Combat Enhancement | + | * Augment Attack <> SORTORDER:GROUP|Combat Enhancement |
− | - Increase to Hit (+1) <> SORTORDER:ABILITY|Augment Attack|1 | + | ** - Increase to Hit (+1) <> SORTORDER:ABILITY|Augment Attack|1 |
− | - Increase Damage (+1) <> SORTORDER:ABILITY|Augment Attack|1 | + | ** - Increase Damage (+1) <> SORTORDER:ABILITY|Augment Attack|1 |
Now I realize using Ability is probably a fallacy, as CATEGORIES can be | Now I realize using Ability is probably a fallacy, as CATEGORIES can be | ||
different for different Abilities; ergo we might need to be more verbose | different for different Abilities; ergo we might need to be more verbose | ||
+ | |||
"CATEGORY=Special Ability,Ability Name" | "CATEGORY=Special Ability,Ability Name" | ||
SORTORDER:CATEGORY=Special Ability,Augment Attack|1 | SORTORDER:CATEGORY=Special Ability,Augment Attack|1 |
Revision as of 06:00, 27 November 2009
This is for Data Team to consolidate wish list items for certain release cycles
6.0 - None [Major Core Code Overhaul]
6.2
Andrew's Draft List: (Tir Requested a List)
Most of these tie directly to the "Eclipse: The Codex Persona" set I'm working on.
- 1) Ability to change HP per level in a single class
- 2) Ability to assign skill points for a certain level dynamically
- 3) Link a Variable from a Master to a "Companion" or vice versa
- 4) CHOOSE:SPELL w/ other tag to Assign Spell to a Class
- 5) Ability to Change "COST" of Ability
- 6) Add SUBRACE= to COMPANIONLIST tag
- 7) Extra Choice for selected abilities - Apply Ability -> Choose from x selections (Apply Selection Choice) add ability to add text to Ability.
Reasoning: I take "Warcraft" normally it would grant a +1 to BAB and has a COST of 6. However, if I take Corrupted and Specialized the COST is reduced to 2.
- 8) Ability to create an Ability... Can be accomplished in LST Editor. Need better interface.
- Need for certain Applications to work
- 9) Allow CHOICE/CHOOSE to have a selection when the COST is 0 and the POOL has 0
- 10a) Sort by 'group'.
- 10b) Sort by Ability Grouping and not necessarily by Alphabetical order
example: Eclipse has certain abilities as part of a group
- Acrobatic
- Light Foot
- Action Hero
- Action Hero Stunts
- Deep Sleep
- Prophecy
- Angst
- Foo
- 10c) We need to group things together without needing to add more OS Blocks
10 can be accomplished a few ways... Introduction of a new tag SORTORDER:
This is a proposal in progress -
SORTORDER:x|y|z
- x = Alphabetical (A-Z,Z-A)
- x = List (How it's listed in the data set)
- x = GROUP
- x = SUBGROUP=
- y = Ability Name to follow
- y = Group Name (Used with Group (x))
- z = optional sort numbering system
LIST is debatable as that could cause issues, especially if .MODs are followed.
Examples of usage:
- Dairy Strings <> SORTORDER:Group|Punk Rock|1
Will apply the Ability Dairy Strings as part of Punk Rock 'Group' and it will be the first item
- Funky Town <> SORTORDER:A-Z|Dairy Strings
Funky Town will be listed in Alphabetical Order after the Ability Called 'Dairy Strings'
- Loves Rock <> SORTORDER:GROUP|Punk Rock|2
- Hates Rock <> SORTORDER:SUBGROUP=Punk Rock|Classical|1
There are several ways it can display with those four examples. We do need to establish order of operation.
- Example 1
- Dairy Strings
- - Funky Town
- Loves Rock
- - Hates Rock
- Example 2
- Dairy Strings
- Loves Rock
- - Hates Rock
- Funky Town
This came about because of how PCGen sorts items by Type or Name. It'd be nice to add Groups.
NAME - What I'm thinking the Sort Order would be set
- Acrobatics <> SORTORDER:GROUP|General (Defaults to A-Z sorting inside
the group)
- - Light Foot <> SORTORDER:ABILITY|Acrobatics
- Companion <> SORTORDER:GROUP|General
- - Template <> SORTORDER:ABILITY|Companion|1
- - Transference <> SORTORDER:ABILITY|Companion|2
- - Might <> SORTORDER:ABILITY|Companion|3
- - Additional <> SORTORDER:ABILITY|Companion|4
- Augment Attack <> SORTORDER:GROUP|Combat Enhancement
- - Increase to Hit (+1) <> SORTORDER:ABILITY|Augment Attack|1
- - Increase Damage (+1) <> SORTORDER:ABILITY|Augment Attack|1
Now I realize using Ability is probably a fallacy, as CATEGORIES can be different for different Abilities; ergo we might need to be more verbose
"CATEGORY=Special Ability,Ability Name"
SORTORDER:CATEGORY=Special Ability,Augment Attack|1