Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Categories
- 1.9K All Categories
- 194 Site Announcements
- 65 News and Announcements
- 129 General Discussion
- 790 Fractal Mapper
- 197 Fractal Mapper General
- 587 Maps and Symbols
- 30 Skwyre Virtual Table Top
- 27 Skwyre General Discussion
- 3 Skwyre How-To
- 333 AstroSynthesis
- 250 AstroSynthesis General
- 83 AstroSynthesis Plug-ins and Scripts
- 103 The Keep
- 103 The Keep General
- 59 ScreenMonkey General
- 18 ScreenMonkey Setup and Configuration
- 283 Inspiration Pad Pro
- 283 Inspiration Pad Pro General
- 128 NBOS Character Sheet Designer
- 128 Character Sheet Designer General
Open Ended dice rolls
Hi, I use Rolemaster for my RPGing and they use percentile dice (1d100) and if you roll a 96 or above, you get to roll again and add the 2 results.
Actually, it goes on with dice roll after dice roll until you roll less than 96 and they're all added together.
How would I be able to simulate these types of rolls? 
Thanks. 
Comments
Without actually creating the code (which I'll probably try to do in the next few days), I'd structure it along these lines:
Set base_roll={1d100}
Set result = base_roll
Set next_roll={1d100} ... then create a loop
When base_roll >95 then Do
... result = result + next_roll
... set base_roll = next_roll
... set next_roll = {1d100}
Else end loop
Now that's not the IPP syntax, and I'm not even sure the loop is really possible (I haven't done much with When - Do statements). There should be a way to output each {1d100} to check what it's really adding. Please post if get some code to work.
I've more or less got it now. Here's the output for 10 tries, with rerolling on a 70 or higher:
Here's the code. Looks simple now, but there was a lot of trial and error getting it to run:
And, of course, the user is prompted to enter the threshold for when to add dice together and reroll.
Now that it works, could streamline the output to be silent on "Total Score is..." So it really just lists raw dice scores sequentially, then provides the Final Score. And yes, it does always roll one time too many the way I wrote it, but never adds in more rolls than intended.
Here's the streamlined output:
And the code:
Excellent - thanks. I can see it goes on beautifully.
Now, how do I apply this result to a Lookup Table?
Well, I'd start by replacing the prompt input with a straight "96". Just dump the prompt, dump the "Define", and replace {CRIT} with a 96. And, "==" all the other stuff, if you want to suppress all output of any rolls or Total_Score.
Then, just try [#{@Total_Score} NewTable] to use the value of Total_Score in your new lookup table.
By removing the prompt, this could also be as standalone dice roll, located in the "Common" folder, and you could call it in a different generator using a "Use" command. Then it just creates the Total_Score and brings it into your new generator.
A few ways to make it happen, depending on the overall application.
The crit is set to 96 always, but I'm not sure what you mean by '==' all the other stuff.
Sorry, I'm not so good at this - Your code works but I have no idea why,
When you use:
{Bonusnumber=1d100}It outputs the rolled number - visibly on the generator results screen. If you want the roll silent (not output on the generator) then use:
{Bonusnumber==1d100}That will set the variable "Bonusnumber" to whatever the d100 result is, but not output it to the screen.
The code in Table: Total_Score was kinda crazy. Not surprised if it's hard to follow. But in the end, it creates that variable {@Total} which is the final die roll result. Put double equal signs "==" everywhere there is a single equal sign, and the value will be silently calculated and saved in {@Total}
Then just use it when calling your lookup table. The code should be something like:
[#{@Total} NewTable](I think I said {@Total_Score} earlier, which was wrong)If the die roll result was, say, 214, then that table call would in effect be saying, "Lookup a die roll of 214 on table NewTable".
And take it slow and don't lose hope - I've only been at this for a few months now. There are some limitations in IPP, but what it can do is pretty amazing.
This outputs just the final die roll value, {@Total}
This uses that value in a lookup table:
Wow - thanks for your help with this, I still can't work out how it works; I understand the 'When/Else' commands but not how the variables work (which is the major part of the code).
Fortunately, the Treasure generator is just lots and lots of tables and subtables. It's not hard, just time-consuming copying and pasting and then I'll have to add the refs to the other tables instead of 'roll on table 14.47'.
However, I do see one problem - the Open-Ended dice roll code referenced your 'NewTable'. There is an option to add this code again and again but changing the Variable code names (as I know that Variables are set until you hit 'generate' again).
I'm still a long way off completing it and I've only pasted a few tables to show how there's a table referenced in a table in a table (and it goes deeper still). Not all tables go above 100 (so I can keep the 'Roll: 1d100' for those) but there are a lot of them still.
As you may notice, I'd used a 'Roll: 1d400' but this gives an equal possibility of getting something awesome when the difficulty should be so much harder in reality.
So this may not be to hard... You have:
76–80: [@T-14-16_RND_Master_Magic_Items]
Which says go roll on table T-14-16_RND_Master_Magic_Items. Once there, the table says to roll a d400.
Instead, insert the "open rolls" code. Then make your call look like:
76–80: [#{@Total} T-14-16_RND_Master_Magic_Items]Which says, go to table T-14-16_RND_Master_Magic_Items and find me the item that matches up to number 214 (if 214 is the value saved in @Total when it is calculated). The "Roll:1d400" line should be removed from T-14-16_RND_Master_Magic_Items as well.
It might even work to ONLY change the Roll:1d400 to:
Roll:{@Total}But in table T-14-16_RND_Master_Magic_Items, you always need a default statement, in the incredibly rare event that the "Open roll" returns a value greater than 400. So something like:
That way if @Total exceeds 400, you get item 400 rather than an error or blank.
This seems pretty sound, blending the "opens rolls" code with part of your tables. I'd certainly do the prompt1, prompt2 thing from the other thread rather than using 26 letters to determine quality of items and quality of wealth. Then, I think you're well on your way!
Here's the logic behind the open roll...
Initial (primary) die roll is Basenumber. It's a 1d100 in the opening SET commands.
Bonusnumber is the next d100, in case the first die roll is high enough to need a next die roll.
We also set Result equal to Basenumber (equal to the first d100 roll; this will be our Total if the first die roll does not exceed 95).
Now table Total_Score is called from Main with those variables above already set.
The first When-Do says... make the value of @Total = 1st die roll + 2nd die roll if the first roll is greater than 95, otherwise set @Total to just the first die roll. Simple enough if there is only ever 2 die rolls at most.
The second When-Do is where things get fun. If @Total is greater than Result (this is only ever the case if we were able to add the first two die rolls together, otherwise they would be equal - both equal to Basenumber) then...
Rerun (loop back again to the start of) Total_Score, but first before you do:
1. make Basenumber (the first die) equal to Bonusnumber (the second die value). We're shifting the dies up in priority, because if we're looping back, then we're ready to see if die two is greater than 95.
2. We set Bonusnumber equal to a new d100 roll. Here we're creating a third die roll, and placing it in the second position - the value that we will add if the new Basenumber (which was/is Roll_2) exceeds 95.
3. Set Result equal to @Total. Result is our running total. Remember, if Roll_2 exceeds 95, then we want to add Roll_3 to the sum of (Roll_1+Roll_2), not just add Roll_3 to Roll_2.
4. Now we can loop back with a [@Total_Score] table call.
We keep doing this to keep our running total increasing as long as the next die roll exceeds 95, always storing the running total in the variable @Total.
When we fail the check @Total>;Result (i.e. the new Total is the same as Result... we didn't add to it, because the latest die roll failed to exceed 95), then we END the loop and return to from Total_Score to Main with an accumulated dice roll value stored in @Total.
In all likelihood, Result could be eliminated completely and it could all be done with Basenumber, Bonusnumber, and Total. But, the code is working, so why bother messing with it.
Back in the day (and I mean seriously ancient times) we always had to use a line that went something like "set N = N +1" to increment our counter before looping back to the start of a routine. The second When-Do is just accomplishing something similar by incrementing the die rolls to the next higher priority (Roll_2 becomes primary, Roll_3 becomes bonus; if the rolls continue to exceed 95, then Roll_3 becomes primary and Roll_4 is made as the bonus, etc.) . It's a hack of creating a WHILE-Do or an UNTIL-Do statement.
Thanks for the huge reply and explanation - I've not managed to read it yet, I suffer from chronic migraine and things have been bad but I didn't want you to think I'm ignoring you on purpose.