Npc/pc tracking system.
Npc/pc = A1
A1 is comprised of fields. These fields modify and
support other fields for final attributes.
Fields include race, class, sex, classlvl, stats, skills,
feats, and equipment.
Each field modifies certain subcategories such as height,
as well as other Fields (skills)
I am thinking that to simplify the end process for
managing this enormous task is to allow the admin to
input fields/attributes with backwards modification.
Example:
In original release version called testA1.1 we only put in
one race, one sex,one class, one skill, and one feat,
and one piece of equipment.
Now suppose the Admin wants to add in another piece
of equipment which we will call E2that can modify the
final skill value.
add new equipment
E2
now the program should either have fields to be put in
or have a series of prompts to be answered such as
weight?
1.0
volume?
3 ft. cube
container?
n
(if yes, then ask carrying capacity in volume and wt.)
armor?
n
(again ask the pertinant questions concerning armor)
weapon?
n
(same for weapon)
[weapon questions would include such stuff and
melee, ranged, and circumstances either both or one
could be used]
skill modifier
+2 to skill one
(check off skills and input either positive or negative
value)///This should allow for modification at future
dates
feat modifier
allows for feat number 2.///which would need to be
implemented as well
stat modifier
+3 str but cap at str of 14
class modifier
lowers current class by one, and adds 2 lvls
mage//unless you were mage and then you gain 3 levels
sex modifier
you become opposite sex
race modifier
you become kobold which would be race2///also need to
be added
The final list of attributes or fields that something can
change may be longer than this but I hope this covers
essentially what I would like the character/npc
(including monsters) to look like in the end picture
Tell me what you think, and if I need to get specific on
anything
