The Aurora RPG Engine – Part 12 Redux

So… when I first posted this Part 12 about further probabilities and the “amazing niftiness” of Aurora being bidirectional… I goofed.  Embarrassingly so, and doubly embarrassing for someone who has rolled many a D&D character under good ol’ 4d6 drop lowest.  I very much led myself astray, and I think it was because I became heavily enamoured with the idea/hope that the system was bidirectional, which led me to not examine my probability assumptions.  Mea culpa.

Having finally realized my error, I’ve gone back and crunched the numbers.  Here are the proper, actual, honest, expanding probabilities tables, hidden rolls, and discoveries.

Postscript 2 – Further Probabilities

First, the possibilities for each MoS:

Then the chances of getting at least MoS of X:

Here’s the average MoS expected on a success (if you succeed, this is the average MoS you can expect):

Postscript 3 – Hidden Rolls and Discoveries

Unfortunately, as the above shows, the system is not, in fact, bidirectional.  But some number crunching can get us a little bit of the way there, at least in equivalency.  Here’s a re-written version:

Typically, the difficulty of a task is handled by adjusting the base dice pool.  This allows the player to viscerally feel their chances and properly size up the situation, thus letting them make appropriate choices (and fully RP it out).  However, there are certain instances where it might be more desirable to not “give away” the difficulty of a task to the player and to have them roll blind.  In certain campaign and genre styles – such as one where the characters are expected to be over their heads or one where it is a grim and failure-heavy milieu – this may apply to most of the tests/rolls.  For others, this may be saved for more uncommon circumstances where the level of tension is heightened by explicitly being uncertain and not in the know.

Blind rolling can also be useful for areas like perception, discerning realities, intuition, investigations, and similar, where the GM may not want to tip their hand that something is there (by specifying there is a penalty).  It can be used such that the overall margin of success determines the amount or exactness of the information gained or discovered.  Star Trek Adventures does a version of this for many types of searching, sensor, and similar tests, giving a basic amount of information on a success and allowing the player to spend Momentum (their version of MoS) to give additional and more exacting details and information.  Under Aurora terms, an MoS of 0 would give the base level of information, while an MoS of 1 would reveal something more obscure and an MoS of 3 might divulge everything.

To set an equivalent MoS for a Blind Test, use the following equivalency table:

(Note that these equivalency values change and drop if a character’s dice pool is very high when compared to the MoS required.  For example, a character who has a pool of 7½d and needs an MoS of 3 only actually suffers an equivalent difficulty of -1d instead of the -2d indicated on the chart above.  This is unlikely to have a major impact in most scenarios, but if a character’s pool is large and gauging against a low MoS equivalency, consider stepping up the required MoS by one if you’re finding characters succeeding more often than expected and appropriate for the campaign.)

Postscript – Breaking the Core Mechanic | Index | Postscript – MoS Counting

2 thoughts on “The Aurora RPG Engine – Part 12 Redux

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s