The die roller utilises Perl and the /dev/urandom device on RPoL's Debian server.

It is seeded once, automatically, by Perl.

I hope this is the correct place to post this.  If not, I have my flame-retardant clothes on so flame away with where I should have posted if I had any sense. ;)

I was wondering if the dice roller had a feature either now or will have one in the next version, where past rolls can be seen.  I know the dice roller shows a large number of the most recent rolls, but is there a way for a GM to view all rolls that have been made in their games?

No, it's a cyclic log of 100 lines.  This is because storage space isn't infinite.

*sigh*  Well, it was worth a try.  Thanks Jase!

Is there a way to roll severall dies at once, and show the dies separately?

The DSA system (which we use for the german Borbarad campaign) uses 3 rolls of w20 for skills. But the rolls ain't added together. Each roll is equivalent to an attribute test. If you fail the roll, you can use your skill points to make up for the miss. If you have still 0 or more skill points left over after the 3 rolls, you succeeded.

Now we could always make 3 rolls with 1W20, but this will clutter the log rather fast.

So any way to do the whole roll at once?

Yes.  :)

Set it to 3d20, then select "One Roll Engine" from the pop-up menu of game systems.  This will give you a total, but will record the individual rolls too.

eg: Admin rolled 24 using 3d20 with rolls of 16, 5 & 3.

Note that, AFIK, the rolls are listed in descending order, so if the order is important then you're better rolling seperately.

Hope this helps.

Yes, it does help. Means we have to roll spearately :(.

just out of curiousity, how would ascending/descending order make a difference? either you read it left to right, r right to the left? either you have a # above which the task fails (so you ignore all numbers above that point) or a task at which only a above a # does it succeed, so you ignore everything below that...

i'm confused as to how it would matter really

I can see it mattering, I can't see why you don't... you want randomness in the results. Period, not a sequence.

Uh... the results are random, or as near as you can get.  They're just sorted into a sequence.

Yes, they could be kept in the order they were rolled, but the One Roll Engine was originally implemented for GMs who want to roll up to 20 dice, and see how many of those dice were higher than a specific number.
Having them sorted makes it easier to see that.

Well, putting it that way, I can see some use to it...

I'll try to explain it.

Lets take my char Mara (a very nice, but rather small witch) and a climbing roll as example:

Climbing is rolled vs:courage/dexterity/strength. Mara has a climbing skill of 2(very low), a courage of 14(high), a dexterity of 15(very high), and a strength of 7(extremely low).

Now I throw the dices: 14, 17, 6.

OK, my courage roll is a bare success (14/14). My dexterity roll would be a miss, but I can use 2 of my climbing points to "make up" for it (17/15+2). The strength roll is a sucess (6/7). All together I barely made this climb, with 0 skill points left. The GM would describe how I reach the top, needing severall minutes to recover my senses.

Now what happens if the dice are sorted?

17, 14, 6

OK, my courage roll is a miss, and I can't make up for it (17/14+2). My dexterity roll would be a success (14/15). The strength roll is a sucess (6/7). All together I miss the climb by 1 point, so a failure. The GM would describe that I start to climb, but lose courage halfway and now sit a few steps below the top of that ravine, afraid to move further.

6, 14, 17

Now I would have no courage problem (6/14), and also would be dexterious enough (14/15). But halfway up the ravine my strength gives way, and I sit there, totally exhausted (17/7).

As you see, there is a major difference if the rolls are sorted or not.