| Valegrim |
test
2d10
hmm; thanks to Triomegazero
(dice)XdY(/dice) is the proper code
test 2
(dice)2d10(/dice)
sheesh I dont get it.
oh; brackets
test 3
2d10 ⇒ (4, 5) = 9
Test variation
2d10 ⇒ (3, 10) = 13
2d10 ⇒ (8, 1) = 9
2d10 ⇒ (9, 6) = 15
2d10 ⇒ (9, 6) = 15
2d10 ⇒ (2, 4) = 6
2d10 ⇒ (3, 9) = 12
2d10 ⇒ (8, 6) = 14
2d10 ⇒ (7, 6) = 13
2d10 ⇒ (9, 6) = 15
2d10 ⇒ (8, 2) = 10
2d10 ⇒ (4, 8) = 12
2d10 ⇒ (3, 2) = 5
2d10 ⇒ (5, 2) = 7
2d10 ⇒ (8, 2) = 10
2d10 ⇒ (10, 10) = 20
2d10 ⇒ (9, 3) = 12
2d10 ⇒ (2, 7) = 9
hmm
Tordek Rumnaheim
|
Test
Rolls for initiatives
Init 1d20 + 3 ⇒ (20) + 3 = 231d20 + 3 ⇒ (14) + 3 = 171d20 + 3 ⇒ (19) + 3 = 221d20 + 3 ⇒ (14) + 3 = 171d20 + 3 ⇒ (6) + 3 = 91d20 + 3 ⇒ (10) + 3 = 131d20 + 3 ⇒ (18) + 3 = 211d20 + 3 ⇒ (4) + 3 = 71d20 + 3 ⇒ (8) + 3 = 111d20 + 3 ⇒ (12) + 3 = 151d20 + 3 ⇒ (12) + 3 = 151d20 + 3 ⇒ (12) + 3 = 151d20 + 3 ⇒ (8) + 3 = 11
It figures...
| Joesi |
As far as I know it should be quite possible to make this generally uncheatable. I don't know if anyone has stated this before, but here's a simple solution:
Use the time the message was POSTED (not edit) as the source of the seed for the random number generator. Currently it's calling a new seed every time the message is previewed or edited, which is a problem.
Aside from that, there's also the required step of leaving a small placeholder to indicate when a user has deleted their own post. One would have to enure there were no deleted posts made by the user before or after their diceroll post if they were suspicious of cheating.
It makes good sense to have [deleted] placeholders anyway in messageboards, so that user's don't get confused about what's going on (ex. "I SWEAR there used to be a guy saying 'X' but now I can't find it!").
| Thanael |
Why no advanced dice expressions?
Like for example:
4d6 keep highest 3 dice: 4d6k3
3d6, reroll 1: 3d6r2
Vic Wertz
Chief Technical Officer
|
Why no advanced dice expressions?
I'm not sure anyone ever asked for them before!
Is it opensource or limited only to this website?
It's all custom code.
Vic Wertz
Chief Technical Officer
|
It took longer than you might think. The person who did it, Ross Byers, is no longer with Paizo, but from what I recall, the biggest challenges were largely tied to preventing cheating, and making sure rolls wouldn't change between previewing your post, submitting it, and potentially editing it later. Basically, he had to imagine every possible way that somebody might cheat and then come up with solutions that stopped all of them—ideally, without that solution introducing new ways to cheat!
| kmal2t |
The preview thing wouldn't be that hard, but I hadn't considered editing. That would be a bit of a challenge. Then again all you'd have to do is when they go to edit it would check to see if there was dice code already in..save the results..and not let it reset.
You could still cheat when using results from this forum in a in-person game by using multiple accounts. A DM would have to prevent this by creating a thread and asking his people to give their SN before posting in the thread.
| Thanael |
Thanael wrote:Why no advanced dice expressions?I'm not sure anyone ever asked for them before!
kmal2t wrote:Is it opensource or limited only to this website?It's all custom code.
If the programming is modular enough with what's there it should be easier to just add some of the advanced dice expressions. Ross did already solve the big problem and lay the groundwork.
What kind of code is it? Maybe there are snippets available...
Jeff Morse
|
1d20 ⇒ 9100d1d20 ⇒ (12, 18, 13, 14, 5, 5, 9, 1, 6, 11, 2, 15, 15, 16, 12, 10, 12, 6, 5, 16, 7, 15, 16, 1, 4, 14, 11, 15, 17, 17, 14, 9, 20, 11, 9, 6, 7, 7, 4, 1, 6, 5, 2, 14, 15, 1, 7, 4, 15, 1, 14, 19, 17, 1, 12, 10, 17, 7, 15, 9, 16, 2, 12, 9, 7, 18, 16, 8, 18, 5, 6, 12, 6, 17, 18, 20, 6, 19, 17, 2, 3, 5, 1, 9, 3, 16, 12, 7, 6, 9, 14, 20, 16, 12, 3, 13, 2, 20, 4, 15) = 1023ice]ice]