Personally, I have no problem with the vassal die roller. But I have played with and am playing with
people who insist on a 3rd party die roller. And that adds additional bookeeping overhead I don’t really like.
It would be much, much easier if the vassal engine would support use of a 3rd party die roller; there are plenty
of them around …
In what way? What are the arguments? Hamete provides no information whatsoever on the mechanism it uses for generating random numbers, how can you make any comparison?
Interestingly, the RNG used by Vassal has been completely replaced 3 times over the years with unrelated RNG’s and each time, the ‘detractors’ have raised EXACTLY the same arguments as to what is ‘wrong’ with Vassal’s RNG.
The main issue is that most Game Players don’t actually want, or understand random numbers. Rolling the same numbers multiple times in a row (‘Streakiness’) is perfectly valid in any random sequence. Since this tends to have a significant effect on game play in many games, players are more likely to remember this than all the all the times when the dice weren’t ‘streaky’. Random numbers are only random when looked at statistically in very large numbers, short extracts (e.g. a game’s worth of rolls) from a random number sequence can look completely un-random.
What most Game Players actually want is some sort of short-term balancing of roll probabilities across the length of a game, but random numbers do not give you this.
We have had integration with external dice rollers before (the base code is still in Vassal), but those currently available that I am aware of do not provide an external API to allow us to interact with them effectively, or do not provide the necessarily services like email verification.
I will happily add the ‘Internet Die Roller’ component back in to Vassal id you can find a suitable candidate.