Prevent changing roll results

[GoogleCodeExporter]

It is easy to fake a roll result.  If you type out your roll, allow Dicy to 
expand it, and then backspace over the result and add your own, there is no 
record that it has been changed unless somebody is watching at the exact 
moment the edit occurs.  Ideally, you wouldn't have to worry about people 
changing their results after they roll.  However, some people on the internet 
are jerks.  I prefer wave-dice-robot to Wave Dice Gadget (http://wave-
samples-gallery.appspot.com/about_app?app_id=53001), but perhaps locking the 
rolled results in an un-editable box similar to WDG’s would make sense.  
Alternatively, (and I may be entirely wrong about this) perhaps you could 
throw up a "wave edited" event whenever wave-dice-robot parses and rolls a 
set, so that any changes past the true roll will be visible in the Playback?

I appreciate the project.  Thank you for making it.

Original issue reported on code.google.com by garth...@gmail.com on 10 Nov 2009 at 8:37

[GoogleCodeExporter]

Thank you for the report! :)

I've just checked - the changes made to the roll after it's made are visible in 
playback for me. Could you invite me to a wave so that I can better understand 
the 
issue?

Original comment by shooshpa...@gmail.com on 10 Nov 2009 at 8:43

[GoogleCodeExporter]

Original comment by shooshpa...@gmail.com on 10 Nov 2009 at 8:55

• Changed title: Prevent changing roll results
• Changed state: Accepted

[GoogleCodeExporter]

Original comment by shooshpa...@gmail.com on 10 Nov 2009 at 8:55

[GoogleCodeExporter]

Well, maybe I can implement this using dynamic images, not gadgets?

Original comment by shooshpa...@gmail.com on 11 Nov 2009 at 9:08

[GoogleCodeExporter]

imo images cause more problems than they solve.

* no ability to make bold/change color/change background/italicise etc
* does image have to be hosted somewhere?

perhaps wait for guidance from Google?

Original comment by trent.ba...@gmail.com on 16 Nov 2009 at 10:02

[GoogleCodeExporter]

Well, I can generate image with roll results already made bold/colored/etc. The 
problem 
is that you can delete the whole roll and re-make it and it would not display 
on 
replay. So the solution I'm currently investigating is "signing" each roll with 
an 
annotation and recording which signatures each blip contains. This would allow 
checking 
on each edit whether the signatures were violated and notifying participants in 
the 
wave about it.

It's not easy to implement, though, so it would require some time :)

Original comment by shooshpa...@gmail.com on 16 Nov 2009 at 10:07

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Thanks for your comments, I came on here with the same situation. I am setting 
up a
Gurps game in April, and I am taking the time from now until then to A) learn 
the
system better (I'm more used to D20), but also to get myself and my players up 
to
speed on Google Wave, and finding the best tools for us to play. Your Die 
roller is
the best out there that I've seen, but this is the one problem we noticed. The
ability to fudge rolls. Thankfully my group are a pretty honest bunch, and I 
don't
really see it as a problem, but it would be nice to have the assurance that they
aren't really re-editing or deleting and re-rolling rolls.

Original comment by pdf...@gmail.com on 24 Jan 2010 at 6:25