Siblings and other dual numbers

[Hannu]

Let's imagine that I have something like this - will share full version of that soon as Mythras initiated generator
{
"name": "Siblings",
"entries": [
{
"m": 10,
"v": "None"
},
{
"m": 20,
"v": "{dice:1d4} siblings"
},
{
"m": 40,
"v": "{dice:1d6} siblings"
},
{
"m": 20,
"v": "{dice:1d8} siblings"
},
{
"m": 10,
"v": "{dice:1d10} siblings"
}
]
},

What would be a reasonable way of making the output be

3 sisters and 4 brothers instead of seven siblings

I have done this for grandparents by using multiple tables connected but it is a bit awkward way...

I have similar generators coming up later.

 

[ELF]

As there currently is no comparison or math functionality available, decision trees are pretty much the way to go.

If it's not important to first know the number of siblings, could you just randomize sisters and brother separately, like "{sisters} and {brothers} (with 0 being displayed as "no")? You could even store the numbers in variables for later use, if necessary.

But if you already know the number of siblings and want just to determine the gender distribution, you _could_ achieve that with layers of generator calls redirecting to the next generator based on the selected entry, so that all the potential sibling combinations are covered, but that's not very convenient. (Was this what you used for the grandparents?)

 

[Hannu]

Yep the layering is what I did - it worked (awkwardly) for grandparents. May have to turn to the route you were pointing out as I suspected

 

[ELF]

Yeah, numeric variables and arithmetic functions would be oh so convenient. But at least we now have global variables - think of what kind of decisions trees were required before variables...

Yep the layering is what I did - it worked (awkwardly) for grandparents. May have to turn to the route you were pointing out as I suspected

When designing the logic for the sibling permutations, just remember that the parents could also have neuter and hermaphrodite offspring...

 

[Hannu]

I solved it this way:

{
"name": "Siblings",
"entries": [
{
"m": 10,
"v": "None"
},
{
"m": 20,
"v": "{BrothersSistersFour}"
},
{
"m": 40,
"v": "{BrothersSistersSix}"
},
{
"m": 20,
"v": "{BrothersSistersEight}"
},
{
"m": 10,
"v": "{BrothersSistersTen}"
}
]
},
{
"name": "BrothersSistersFour",
"entries": [

"{dice:1d4} brothers",
"{dice:1d3} brothers, one sister",
"{dice:1d2} brothers, {dice:1d2} sisters",
"Brother, {dice:1d3} sisters",
"{dice:1d4} sisters"
]
},
{
"name": "BrothersSistersSix",
"entries": [
{
"m": 6,
"v": "{BrothersSistersFour}"
},
"{dice:1d6} brothers",
"{dice:1d5} brothers, one sister",
"Brother, {dice:1d5} sisters",
"{dice:1d6} sisters"
]
},
{
"name": "BrothersSistersEight",
"entries": [
{
"m": 8,
"v": "{BrothersSistersSix}"
},
"{dice:1d8} brothers",
"{dice:1d7} brothers, one sister",
"Brother, {dice:1d7} sisters",
"{dice:1d7} sisters"
]
},

{
"name": "BrothersSistersTen",
"entries": [
{
"m": 20,
"v": "{BrothersSistersEight}"
},
"{dice:1d10} brothers",
"{dice:1d9} brothers, one sister",
"Brother, {dice:1d9} sisters",
"{dice:1d10} sisters"
]
},

 

[Hannu]

When designing the logic for the sibling permutations, just remember that the parents could also have neuter and hermaphrodite offspring...

I will let that to be circumstance decision...

 

[Hannu]

How have you handled the single/multiple thing. one sister, two sisters - in above using that with additional tables might be awkward

 

[ELF]

I don’t have an exactly similar case, but in the final node of gender and age based decision trees I set variables for the correct substantive, as well as subjective, objective, possessive etc. forms.

Bit of a chore to set them up, but when you call already existing generators as often as possible, you only have to do it once. (And can also set everything ready also for corner cases like hermaphrodites.)