# .font: font.text_2
# .autowrap: false
# .centered: true
boulderdash 3 n/6
# .font: font.text_1
by
# .font: font.text_2
dustin
# .centered: false

# .font: font.value_1
# .autowrap: false
DUSTIN                            2021-09-28 21:56
# .font: font.value_2
# .autowrap: true
RANDOM SEED: (170 102 87 198 86) 256  
YES, ACTUALLY A NUMBER OUT OF THE 0-255 RANGE! AS THERE'S NO PATTERN IN THE ORIGINAL FIVE SEEDS, I ABUSED IT FOR A LITTLE EXPERIMENT: IN GDASH, IT'S POSSIBLE TO CHOSE ANY RANDOM SEED, ALSO BEYOND 255. I THOUGHT THAT 256 WOULD GIVE THE SAME RESULT AS 0 BECAUSE EVERYTHING IS CALCULATED MODULO 256 ANYWAY. INDEED THE SEEDS 0 AND 256 ARE VERY SIMILAR BUT NOT IDENTIC! THERE ARE THREE BOULDERS WHICH WOULD NOT BE THERE WITH SEED 0 (I MARKED THEM AS HEAVY BOULDERS; IT'S EASY TO COMPARE WITH MY M/6 VERSION WHERE SEED IS 0. ALTHOUGH M/6 HAS A HIGHER BOULDER DENSITY, THOSE THREE BOULDERS ARE MISSING!) ALSO, THERE ARE FIVE MISSING ROCKS WHICH WOULD BE THERE WITH SEED 0.INTERESTING!  
  
\REQUIRED: (85) 95  
  
CAVE TIME: (150 150 110 110 110) 86  
  
BTW, THIS CAVE IS CLOSE TO INSANE WITH THE BOULDERS CLOSE TO THE BUTTERFLY-ENTRANCE AND THE LOW TIMER. I THINK IT FITS WELL WITH GENERAL BD3-HIGHER LEVEL-MADNESS! :D

# .font: font.value_1
# .autowrap: false
NESDORI                           2021-09-28 22:10
# .font: font.value_2
# .autowrap: true
dustin, IT SEEMS THAT IF IN GDASH THE SEED IS OVER 255, IT SETS SEED_1 (WHICH USUALLY IS INITIALLY 0) WITH THE UPPER BITS. SO THE EFFECT YOU ARE GETTING IS EQUIVALENT STARTING WITH SEED_1 = 1 AND SEED_2 = 0. IF THE GDASH SEED IS 512, THEN IT WOULD BE EQUAL TO SEED_1 = 2, SEED_2 = 0 AND SO ON.

# .font: font.value_1
# .autowrap: false
ALTERMAVEN                        2021-09-28 22:57
# .font: font.value_2
# .autowrap: true
INTERESTING, CONSIDERING THAT IN TYPICAL C64 RESTRAINTS, IF YOU DID SOMEHOW GO ABOVE 255, YOU'D NOT ONLY COMMIT A WRAP AND CONFLICT WITH THE NEAREST BYTE, YOU WOULD ALSO WIND UP WITH AN RNG THAT IS A MODULUS OF WHAT IS LISTED (AS THE RNG SEED IS UINT!). SO IF YOU HAD A SEED OF 384, YOU'D WIND UP WITH 01:80 WHICH WOULD JUST READ 0X80 FOR THE SEED (128!)

# .font: font.value_1
# .autowrap: false
NESDORI                           2021-09-28 23:04
# .font: font.value_2
# .autowrap: true
altermaven, THAT'S RIGHT. BUT C64 RNG HAS TWO 8-BIT SEEDS (SEED_2 IS THE ONE WHICH IS CHOSEN IN CAVE DATA AND SEED_1 IS JUST 0 INITIALLY) AND GDASH JUST COMBINES THOSE TWO INTO ONE 16-BIT VALUE. A LITTLE CONFUSING WAY TO ENTER SEEDS FOR OTHER THAN CODERS :)

# .font: font.value_1
# .autowrap: false
DUSTIN                            2021-09-28 23:41
# .font: font.value_2
# .autowrap: true
AH, INTERESTING! BUT THEN I STILL WONDER WHY THE WHOLE RESULTS ARE SO SIMILAR WITH INITIAL SEED PAIRS (0,0) AND (1,0). WHEN WE HAD AN INTENSE DISCUSSION OF THE RNG IN arno'S FORUM, arno MENTIONED A CASE WHERE SEED PAIRS OF THE FORM (X, Y) AND (X+2, Y) STAYED CLOSE TOGETHER FOR A LONG TIME, BUT I WOULD NOT INTUITIVELY EXPECT THE SAME BEHAVIOUR HERE BECAUSE I REMEMBER THERE WERE QUITE SOME NUANCES IN THE FORMULAS THAT MADE A HUGE DIFFERENCE BETWEEN EVENNESS AND ODDNESS...

# .font: font.value_1
# .autowrap: false
NESDORI                           2021-09-28 23:55
# .font: font.value_2
# .autowrap: true
dustin, SURPRISING SIMILAR INDEED. WITH SEED_1 SET TO 1 I TRIED ALSO OTHER SEED_2:S. WITH SEED_2=1 THERE'S ALSO JUST 3-BOULDER DIFFERENCE. WITH SEED_2=2 THERE'S NO DIFFERENCE AT ALL! :O WITH SEED2=3 THERE ARE SEVERAL DIFFERENT BOULDERS AND IN FACT THERE ARE JUST FEW SIMILAR REGIONS. INTERESTING.. :)