RNG not my friend or I should code this in a different way?

[American2050]

So I have a code that runs 2 loops, one to move on the X axis and other to move on the Z axis.

 

The idea is to check a 3x3 area around the block that triggers the call.

 

Once I do that, I generator a random number, and if that number is 1, then I cause block updates for the 3 blocks on the Y axis at that coordinates.

 

Problem is that for some reason that I don't understand, than random number is 1 most time when the X axis is -1 in relation to the time it's 1 when the X axis is 1. And kinda the same on the Z axis.

 

Code:

 

			for(int xAxis=-1;xAxis<=1;xAxis++){

			for(int zAxis=-1;zAxis<=1;zAxis++){

					int chance = Stuff.randInt(1, chances);

					if (chance==1){

						if(xAxis == -1){ menosUnoX++; }
						if(xAxis == 0){ ceroX++; }
						if(xAxis == 1){ masUnoX++; }
						if(zAxis == -1){ menosUnoZ++; }
						if(zAxis == 0){ ceroZ++; }
						if(zAxis == 1){ masUnoZ++; }

						System.out.println("xAxis is -1: " + menosUnoX + " times - 0: " + ceroX + " times - 1: " + masUnoX + " times");
						System.out.println("zAxis is -1: " + menosUnoZ + " times - 0: " + ceroZ + " times - 1: " + masUnoZ + " times");

					for(int yAxis=-1;yAxis<=1;yAxis++){

					Block checkBlock =  world.getBlockState(pos.add(xAxis, yAxis, zAxis)).getBlock();
					world.scheduleBlockUpdate(pos.add(xAxis, yAxis, zAxis), checkBlock, 0, 1);

					}

					return EnumActionResult.SUCCESS;

					}

			}

		}

 

 

Log after 200 times been the random number 1 when the xAxis was -1:

 

xAxis is -1: 200 times - 0: 89 times - 1: 53 times
zAxis is -1: 148 times - 0: 100 times - 1: 94 times

[coolAlias]

That's only 342 iterations, and while 200 / 342 may seem skewed, it is also entirely within the realm of possibility for an RNG. If you want to see a more even distribution, you'd probably have to run 1000s of iterations.

 

What kinds of values does 'chances' have? Why not check the chance before you loop to avoid the loop entirely if the chance != 1? And if chance == 1, why not get more random numbers for the axis? E.g.

int chance = Stuff.randInt(1, chances);
if (chance == 1) {
    int xAxis = Stuff.randInt(1, 3) - 2; // gives value between -1 and 1, inclusive
    int zAxis = Stuff.randInt(1, 3) - 2; // gives value between -1 and 1, inclusive
    // now iterate over the yAxis as you like using xAxis and zAxis
    return EnumActionResult.SUCCESS;
}

That way you only have one single loop all on its own instead of nested inside of 2 other loops, and far fewer random number generations, all with effectively the same result.

[American2050]

The chance is running at that step on the loops because, when the chance is 1, I don't need to update the 3x3x3 blocks in the area, but only the 3 on the Y level that are in X/Z coordinates where chance came as "true" (=1)

 

chances is random between 1 and 2 in this example. But I run this code, because I noticed since the day I made this code, that the crops on the west were always growing faster than the ones on the east, so I knew something was wrong.

 

However what I did now, is kinda what you suggested, only run the loop and update the 3x3x3 area at once when chance = 1. It makes crops grow faster and I wont have this "unevenness" problem. The only problem I have now is that when causing updates around cactus and sugarcanes, they all grow at once, but I can live with that

 

 

 

[Draco18s]

Rather than randomly determine if a location gets an update, randomly determine a location to update.