Timeline for How can I prevent small numerical advantages from dominating the balance of an encounter?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:18 | history | edited | CommunityBot |
replaced http://gamedev.stackexchange.com/ with https://gamedev.stackexchange.com/
|
|
| Jul 20, 2016 at 21:11 | history | edited | Stormwind | CC BY-SA 3.0 |
addition re. rand() fn's num type
|
| Jul 20, 2016 at 21:09 | comment | added | Stormwind | Yes, that's part of the intended message, to just point out the varying behaviour of numerical spaces, eg. small-value integers (rough granularity) vs. large-value integer (and indeed also floats) with fine granularity. I'll insert "integer" somewhere, thx for pinpointing. I actually do point out that negligibility: "(in this case it is irrelevant whether it is > or ≥ as they are so close"). Often numbers find surprising values (for the hman mind) if the system isn't encouraged to seek balance. Generically speaking, ofc, not necessarily in this case. | |
| Jul 20, 2016 at 7:54 | comment | added | Philipp |
Are you using a random number generator which generates integers? My answer uses a RNG which generates double-precision floating point numbers between 0.0 and 1.0. In that case the difference between > and >= is negligible. You might want to point that out.
|
|
| Jul 19, 2016 at 23:51 | history | answered | Stormwind | CC BY-SA 3.0 |