McDie

I'm taking the pool span of 2d6 and plugging it into a histogram and getting an output of 100% zero. Is this a bug or am I misunderstanding how some of the nodes work? I would expect a distribution of values between 0 and 5.

It seems that if you try to connect multiple pools to something taking a pool as input, it just silently ignores one of the pools.  I was wondering for a long time what was going wrong for a more complicated setup.  I can't seem to be post a picture.

Hoping some intrepid McDie master can help me with this. I've tried, but I'm really stuck with a few aspects of this. I can write it out logically, but I can't figure out how to spit out the histogram I want and don't know where else to ask.

The basic idea for the combat system I'm working on is that an attack die pool is rolled against the highest die of the defense pool aiming to meet or exceed it, the color of the attack die (green / yellow / red) determines how many successes the attack die scores (1 / 2 / 3 respectively), and doubles / triples / quads rolled that are successes add 2 / 4 / 6 hits respectively. In detail:

1. An attack die pool is made of xd6 + xd8 + xd10 (each die can be green, yellow, or red)
2. A defense die pool is made of 1-3 d6's
3. Both pools are rolled. The defense value is the highest defense die rolled.
4. Each [green / yellow / red] attack die scores [1 / 2 / 3] hits if it is equal to or greater than the defense value.
5. Additionally, each set of [doubles / triples / quads] among attack die that hit score an additional [2 / 4 / 6] hits.
6. Histogram: average hits scored by a given attack / defense dice pool.

This is the .mcd file for what I have so far, I have no clue how to incorporate the different die types, nor the additional hits for rolling sets. Any help at all would be hugely appreciated!

Great program, thank you! I'm less than an hour into it, but it seems like just what I need for some board game design analysis. I was going to create my own simulation in Google Sheets, but this is definitely more fun! I haven't donated yet, but I will.

One minor request - "A > B" and "A < B" would be useful nodes. I know I can simulate "A > B" with "A <= B"-->"Not", but it's a little clunky.

Hey Geoff, I love this program and have been using it a lot recently! Super intuitive and well put together. Thank you for making it :)

One feature request I have is the ability to lock the scale on histograms so that they match each other. I want to compare bell curves with quite different ranges but keep them to scale with each other to help visualise the difference.

I see a lot of value in this. Is there any way to do an `If T/F then #P1\X2 else #P2\X2`? I feel like this would simplify some processes I'm trying to model. A case switch would be even better!

This is an amazing tool!

However, I'm having a little problem.

I'm trying to model a sort of an inverted bell curve distribution by using a die pool and a coin flip (basically, I want to set up a die pool, separately roll a single die, and if it comes out even, send the highest roll from the pool to the histogram, otherwise send the lowest roll from the pool). I think I need to use a "Switch Integers" node for this, but while this node is mentiones in the user manual, I can't find it in the actual program. I've tried using the search function and no nodes with the name "switch" come up. 

Hi Geoff.  Nice tool, I'm enjoying some discovery sessions with it.  Couple of requests:

1. The A modulo B node always comues up as A multiply B instead.  Bug? I was trying to explore some digital root probability - can't get anywhere without a working Modulo, I think.

2. Can you add a general loop function so we can do non-pool stuff?  Not sure exactly how you'd indicate which nodes are to be repeated though...

just downloaded, thanks for making this. Heads up that the first thing I did was create an integer node and hit f4 to duplicated it, and the program crashes. This is reproducible. Win 10.

SUGGESTION (UX): the App should prompt to save if the file is dirty. Currently, I can add a Node, quit the App and I don't get prompted to save. (Yikes!)

Build 310: Cut/Copy/Paste only pastes one time. I can't copy a Node and paste it 5 times so that I have 6 copies.

(On the plus side, SPLIT looks cool, though I don't have a Use Case for it just yet, and the undo/redo works as expected, though without a visible history it gets a little "hit and miss" 😉)

Careful for users: ctrl+s does not save anything. Also if you select "save as" to overwrite a previous file it does not work either.

Both of the above happen with no error messages so you think you saved something you spent the last 20 minutes creating but no!

If you do "save as" and then create a new file it works by the way. It just doesn't allow itself to overwrite.

My D&D stat rolling involves dropping low but if there's a tie for the lowest die and the lows are below 3, drop one and reroll the others until they're any higher number on the die. (so a 4d6 roll of 6,1,1,1 would drop a single 1 and reroll the other two 1s until they're anything higher, such as 2,4) Is it possible to model that in McDie?  It sounds like I'd need to break apart the "remove lowest" node in McDie into its separate logic and reconstruct it to work in a different way.

One simple thing that's missing is double-clicking .mcd files should open in the program. Right now I could associate the file to the .exe and it'll open the program but I'm then forced to ctrl+O to the .mcd file anyway.

Is there a wiki/documentation for this anywhere? Some of the node types are not entirely clear what they are for and what they do.

Impressive! :)

On a side note out of curiosity since I am also a VS C# developer. What control are you using for the flowchart? DLL snooping suggests this: https://www.codeproject.com/Articles/182683/NetworkView-A-WPF-custom-control-for...

FEATURE REQUEST: any chance that the stats (average etc) can be added to the CSV export of the histograms?

FEATURE REQUEST: I have a need to exclude a specific value from my Pool results. In my case, I want to filter out the 0 results from a pool (they are results that equate to FAIL/MISS) so that I can report the average result of SUCCEED/HIT, rather than the average result across all HIT/MISS outcomes. 

This is similar, but not the same as, a model that allows rerolls of "result X", which also might prove useful to some models.

exploding pool doesn't appear to work with custom dice. The sum looks to be the face number instead of the face value.

Thanks for making this.

Any chance of a Linux version?

Quick question and note:
1. Any plans for making the code available? 

2. The discord link in the readme gave an "expired invite note"

Thanks!

Hmmm... I was just working on a model for use with Oathsworn: Into the Deepwood and I hit a problem. The game uses 4 types of die

White: 0,0,1,1,2,2*

Yellow: 0,0,1,2,3,3*

Red: 0,0,2,3,3,4*

Black: 0,0,3,3,4,5*

The "*" results explode. One may roll a mixture of any number of any combination of colours of dice. So the Black and Red dice are easier to model, because they explode on a single, non-duplicated value. But the White and Yellow dice are a bit of a problem because they have two faces with the maximum value, but only one face "explodes". To complicate matters, any time two or more dice roll a 0, the result is a "fail" (call it 0). Any suggestions on how to model this? Frankly, I'm stumped (though I'm not very smart either 😉

Awesome tool! I was wondering whether it would be possible to have a Explosion Depth limiter. I know the point of exploding dice is the fun of having them explode to the infinite degree, but sometimes it might be useful to be able to limit the number of times a die can explode.