Collectible Card Game Headquarters

I played a lot with forge and something told me that the shuffling was always a little bit weird, e.g. much periodic behaviour.

As I looked at the source code of Cockatrice, I saw that they use a SIMD-oriented Fast Mersenne Twister for random numbers (http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/SFMT/) and asked me why... then I dug deeper and found that several languages use Mersenne-Twister as RNG, like Python, Ruby, R, PHP, MATLAB and C++11 but Java does not... multiple sources told me that the java.util.Random class is not very state of the art, see http://www.alife.co.uk/nonrandom/ and http://www.qbrundage.com/michaelb/pubs/ ... ation.html
The second source has Mersenne Twister and R250/521 implementations for Java under public domain and shortly describes them.

Could you improve the forge.util.MyRandom wrapper code by copying the MT class over and use it instead of using java.util.Random? It's only copy-paste with three lines of changes.

ok, it looks like there are more changes needed (102 occurences in 77 files) for this because the code directly uses random-instances everywhere which are used to generate int or float numbers.
The wrapper class basically only saves a 'new Random()'-statement instead of capsulating this and returning an int or float.

Do you plan to do this? It's cleaner, smaller, better
You could create the methods public static int getRandomInt() and getRandomFloat() for the MyRandom wrapper class, which directly return the random() value from the MT class as int or float and start using it when new code needs random numbers.
The usage of the old getRandom method can be rooted out step by step everywhere (please begin with card shuffling ).

You won't be able to completelly root out java.util.Random usages.

Code: Select all

        final List<CardPrinted> shuffled = deck.toFlatList();
        Collections.shuffle(shuffled, MyRandom.getRandom());


But you can always create a derived class from java.util.Random that would feature a better algorithm.

Given such a class it can be attached to Forge in no time.

http://stackoverflow.com/questions/2249 ... doing-what shows Java's source code for Collection shuffling, I guess it should be possible to create a new Collection class that inherits everything but overrides shuffling.

Edit: yeah, overriding the Random class should be better

mark wrote:I guess it should be possible to create a new Collection class that inherits everything but overrides shuffling.

This just won't happen.

mark wrote:Edit: yeah, overriding the Random class should be better

By the way there's an implementation alredy done in Java 6
http://docs.oracle.com/javase/6/docs/ap ... andom.html

The SecureRandom class is much better, but up to 60 times slower [1]. Nevertheless, it simply works by applying the following patch to forge without noticeable performance impacts:

Code: Select all

Index: src/main/java/forge/util/MyRandom.java
===================================================================
--- src/main/java/forge/util/MyRandom.java      (Revision 21526)
+++ src/main/java/forge/util/MyRandom.java      (Arbeitskopie)
@@ -18,6 +18,7 @@
 package forge.util;
 
 import java.util.Random;
+import java.security.SecureRandom;
 
 /**
  * <p>
@@ -30,7 +31,7 @@
  */
 public class MyRandom {
     /** Constant <code>random</code>. */
-    private static Random random = new Random();
+    private static Random random = new SecureRandom();
 
     /**
      * <p>


If this slows down too much, there is always the option to change to MT.