Difference between revisions of "Thread:Talk:Random Movement/mersenne twister/reply (4)"
Jump to navigation
Jump to search
m (Reply to mersenne twister) |
m |
||
| Line 3: | Line 3: | ||
# Battles have other confounding factors (i.e. walls) which may hide what random number a bot chose. | # Battles have other confounding factors (i.e. walls) which may hide what random number a bot chose. | ||
| − | As an aside, that mersenne twister implementation is not a suitable replacement for Math.random() even if PRNG quality mattered, because it's not really more secure | + | As an aside, that mersenne twister implementation is not a suitable replacement for Math.random() even if PRNG quality mattered, because it's not really more notably secure. If that was an issue, you'd want a cryptographically secure pseudorandom number generator, not a mersenne twister. |
Also, an out-of-the-blue link to a mersenne twister page isn't really a useful post. | Also, an out-of-the-blue link to a mersenne twister page isn't really a useful post. | ||
Latest revision as of 04:18, 21 December 2013
Because:
- So few random numbers are generated that even a pretty mediocre pseudorandom number generator would be pretty much impossible to predict. You need to capture a decent chunk of data to crack even a bad PRNG's state.
- Battles have other confounding factors (i.e. walls) which may hide what random number a bot chose.
As an aside, that mersenne twister implementation is not a suitable replacement for Math.random() even if PRNG quality mattered, because it's not really more notably secure. If that was an issue, you'd want a cryptographically secure pseudorandom number generator, not a mersenne twister.
Also, an out-of-the-blue link to a mersenne twister page isn't really a useful post.
