Timeline for Roll and Keep in Anydice
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 25, 2020 at 21:27 | vote | accept | Trish | ||
| Jun 16, 2020 at 10:23 | history | edited | CommunityBot | Commonmark migration | |
| Mar 23, 2020 at 12:59 | comment | added | Ilmari Karonen | @Trish: With the default explode depth of 2, [explode d10] is exactly equivalent to {{1..9}:900, {11..19}:90, {21..30}:9}. The only difference to your "truncated" die is that your last range ends at 29 instead of 30. (Effectively, you're conditioning on three consecutive 10s never happening, instead of counting it as 30.) While having 27 instead of 28 possible results for the custom die will surely have some effect on the runtime, It doesn't seem to make any practical difference. (In particular, it seems either way AnyDice can handle XkY for up to X=6 but not for X=7, regardless of Y.) | |
| Mar 23, 2020 at 12:00 | history | edited | Someone_Evil♦ | CC BY-SA 4.0 | added 315 characters in body |
| Mar 22, 2020 at 15:27 | vote | accept | Trish | ||
| Mar 22, 2020 at 15:28 | |||||
| Mar 22, 2020 at 15:27 | comment | added | Trish | Taking this as a base, you get a much smaller margin of error by adding a 2nd. explosion and modeling it like this: anydice.com/program/1a8be - to cope with the larger rolls, you need to remove the last line. | |
| Mar 20, 2020 at 18:06 | comment | added | Carcer | FYI, you can already change the explosion depth by set "explode depth" to 1, and defining a custom die rather than using the built in explosion function doesn't seem to be any more efficient in terms of how large a pool it allows you to consider. | |
| Mar 20, 2020 at 17:30 | history | edited | Someone_Evil♦ | CC BY-SA 4.0 | added 400 characters in body |
| Mar 20, 2020 at 17:22 | history | answered | Someone_Evil♦ | CC BY-SA 4.0 |