Sounds cool, i'd be interested what you'll come up with. Just don't underestimate how complex your data structure has to be. In many systems single points in traits can represent a whole lot of information. In Shadowrun the is a trait called connections, where every point represents a NPC which should at least be given a name an a few sentences of background. In the WoD-Games you have traits like language, where you have to decide what actual languages you buy when buying new points for that skill. These kinds of additional information are especially helpful for the storyteller/gamemaster when planing a story.
Also it seems to me like a good idea to make information like character classes hierarchic. A good example would be prestige classes you get on top of you character class in D&D 3 but also things like Breed=>Auspice=>Tribe in Werewolf could be represented that way.
If it would be helpful to you, i could try to describe my Demon: The Fallen character in a perl data structure.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
