Dice roller question
 

hi, I'm making a data file for Dark Heresy and have run into a _Potential_ challenge. I need to call the dice roller multiple times throughout the character generation process. A List seems to be in order.
i need to roll a

D5 for Wounds.
D10 for Fate
D100 for Divination

and in the future will need 2D10 for characteristic generation (this will only happen AFTER i get the data files in a workable form)

i am assuming that you can call the function from outside the Tac-con, my question is whether you can change what type of dice it rolls on the fly and if so, how?

Thanks for any help,

Regards,

Protector152

Let the user enter the results of those rolls, rather than generating the rolls yourself - many people will prefer to roll physical dice for character generation - those who don't can use the dice roller themselves.

I'll implement that as an option. However the group i play with doesn't know much about rolling up characters and we play over the net, hence i want to have the option of semi-/hidden rolls to speed up the process.

There aren't any good ways to lock down random number generation in the code, and prevent the user from rolling it again - or prevent the program from rolling it again just because you changed something else and your lockdown code wasn't perfect.

tags can do a lot of things, however most of the stuff i "need" to randomize, (other then starting money, and stat generation) will not be needed until start of play. I appreciate that you want to make this whole process easier for me.

I still want to know how to call the dice roller from within the code, change the type of dice it's rolling on the fly and keep the user from interfering with the process unless they have chosen to roll a semi-random character/use real dice.

There is no way to call the diceroller.

The only way to get a random number is to call a random number function - which means that every time you run that script, you will get a new random number.

If you called the script from a button, and then disabled the button after the roll, wouldn't that prevent the player from re-rolling?

You can call it from an action script and then store it in a persistant user field with each button press. Here is an example of a button we use in PF.