Computing Traits

Computing Traits

Posted by Thorin Tabor on Nov. 9, 2012, 1:18 a.m.

In preparing development for the next generation of Saga Machine games we've got a lot of mechanical bits and bobs to get a handle on. Between the core rulebook, companion and all the setting books we've got hundreds of traits and stat blocks. All these mechanical bits can make altering the game system a complicated process, as changing one trait can mean resulting changes in scores of stat blocks; and altering a core game mechanic can mean changes in every such block.

To better handle these sorts of changes, and to prevent errors in consistency from cropping up, I've been working on a computer program to handle much of the book work in the process. Basically this computer program will read in the current text of all our traits and stat blocks, and be able to parse them so it knows much of what they mean and which depend on which. In this way when we alter the cost of name or a trait or something, it can automatically go through and make all of the necessary resulting changes. Naturally, this may require some work and still require some manual nudging, but in the end it should pay off.

Having all this information in a format a computer can understand also buys us a number of other interesting benefits. For example, if we want to know the creatures with the 10 highest strengths in the entire bestiary, it's as easy as running a simple query. Or if we want to know the average stat of a creature of a particular level, it's just another couple queries. This allows for a variety of different ways to run quick "sanity checks" to make sure the spread of abilities adds up.

It also has the benefit of helping other potential projects in the future. For example, if we ever wanted to write a Character Creator program, having a database of traits and their requirements gets us half-way there already. Most of what we would need at that point is just to write the interface.

Look the announcement of a basic version of this trait database later when we announce the public Beta for our upcoming game based on Indian Mythology.

Share Post

0 Comments on Computing Traits

There are currently no comments

New Comment

required

required (not published)

optional

required

Other News from the TabBlog

Rethinking Encumbrance

Many RPGs have a system for dealing with encumbrance and how much a character can carry. On the surface, the purpose of encumbrance is pretty straight-forward: It's a mater of simulation and verisimilitude: A person can only carry so much without being burdened by it all. Underneath, however, encumbrance rules play a variety of more subtle game roles. It's these games roles that I'm going to take a closer look at in this post, and then I'm going to look at a new encumbrance variant that may see use in future Saga Machine games.

About Facing and the Grid

One element of the Saga Machine system that I've been debating the utility of is that of facing in combat. Currently, when using tactical positioning in combat, the system tracks which space the character is facing. The idea behind this is that tracking facing is both a nod to realism and allows for the GM to easily determine when to apply modifiers based on where a character might be facing. Facing also, in theory, makes it easier to have an easy mechanical hook to apply the Sneak Attack trait, as well as to handle situations where staring at an object has a significant consequence (such as seeing Medusa or the gaze of a basilisk). It also can tie into systems such as for vehicles, where a moving object has a clear direction and limited ability to turn.