Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×

Order of Operations

1398187807

Edited 1398188004
hey, a Dice Engine Scientist here with another observation. previously i mentioned that the greater/Less than check fails if there isn't an actual dice roll (2&gt;1=Error instead of 2, 1 Successes) <a href="https://app.roll20.net/forum/post/372747/selected-" rel="nofollow">https://app.roll20.net/forum/post/372747/selected-</a>... , but now i'm back with something else i noticed. i was trying to create a macro for a character that uses summons by using the ?{} command to ask for the name of the summon, and the @{} command to look up it's attributes. IE: Leggy is a huge monsterious fiendish centipede which is a level 6 magical beast with d8 health, and 1 con bonus. Macro, please roll it's health [[ @{Leggy|Level} d @{Leggy|HitDie} + @{Leggy|Con} * @{Leggy|Level} ]] (This command works perfectly as intended just so you know, when there isn't spaces obviously). However the problem occurs when i replace the specific name of the character with a ?{} command to generalize it to make this macro work for ALL the summons, so i can use 1 button instead of 30. i get returned the error, "No character named "?{NAME|Leggy}" exists" before the roller has a chance to ask me what i wanted to put in that box. on a scale from easy, to impossibru, how hard would it be to give the ?{} command top priority in the calculator's order of operations? or would that just end up causing more problems? I'm just a simple engine tester with too much time in my hands. i don't actually know how the dice engine works, thought i'd at least let you know anyway, with my noob opinion of how to fix it, with no idea of how difficult the solution would actually be to pull off.
Unfortunately it would not be easy to change. Also I would hesitate to change it since the order as it is currently is already documented: <a href="https://wiki.roll20.net/Dice_Reference#Order_of_Operations" rel="nofollow">https://wiki.roll20.net/Dice_Reference#Order_of_Operations</a>
1398191245

Edited 1398191311
yeah, i figured it wouldn't be easy, but it should really buff it's practicality if the query was performed and substituted... after maco expansion.it's a really powerful tool that i love a lot. however i do understand the difficulty in changing the game's engine, especially when it's this complex. not to mention, as the old song goes. <a href="http://img3.fotos-hochladen.net/uploads/bugsbx84k3iv6u.jpg" rel="nofollow">http://img3.fotos-hochladen.net/uploads/bugsbx84k3iv6u.jpg</a> i didn't expect any results, just wanted to let you guys know anyway. cause i love to see roll20 get better [/topic]
I'll definitely keep it in mind if I see a way to do it in the future without breaking the way it works currently :-)
Use @{selected|Attribute} instead.