# .font: font.text_2
# .autowrap: false
# .centered: true
boulderdash 2 c/6
# .font: font.text_1
by
# .font: font.text_2
dustin
# .centered: false

# .font: font.value_1
# .autowrap: false
DUSTIN                            2020-10-06 20:23
# .font: font.value_2
# .autowrap: true
RANDOM SEED: (24 45 52 30 40) 80  
THE FIVE ORIGINAL VALUES LOOK CHAOTIC, BUT SHOW A PATTERN IF ANALYSED DEEPLY. IT TURNS OUT THAT WITHIN THE RANGE OF 24-52, THESE SEEDS ARE THE ONLY ONES WHICH SATISFY THE FOLLOWING CONDITION:   
  
THERE'S NO STATIONARY FIREFLY WHICH HAS TO BE RELEASED BY SNAPPING OR ADVANCED TRICKS TO FINISH THE CAVE.   
  
AFTER PETER LIEPA CHOSE HIS SEEDS WITH THESE CRITERIA, HE ORDERED THEM IN TERMS OF DIFFICULTY. WHILE I THINK L1 IS CLEARLY EASIEST AND L5 CLEARLY HARDEST, L2-4 SEEM TO BE RELATIVELY CLOSE TOGETHER.   
SO HOW TO CONTINUE THIS PATTERN BEST? JUST LOOKING FOR THE NEXT RANDOM SEED

# .font: font.value_1
# .autowrap: false
DUSTIN                            2020-10-06 20:26
# .font: font.value_2
# .autowrap: true
SHIT, MY COMMENT SOMEHOW GOT CUT OFF?!?! CONTINUATION:  
  
SO HOW TO CONTINUE THIS PATTERN BEST? JUST LOOKING FOR THE NEXT RANDOM SEED

# .font: font.value_1
# .autowrap: false
DUSTIN                            2020-10-06 20:26
# .font: font.value_2
# .autowrap: true
SOMETHING'S WRONG WITH THE COMMENTS... :(

# .font: font.value_1
# .autowrap: false
DUSTIN                            2020-10-06 20:28
# .font: font.value_2
# .autowrap: true
RANDOM SEED: (24 45 52 30 40) 80  
THE FIVE ORIGINAL VALUES LOOK CHAOTIC, BUT SHOW A PATTERN IF ANALYSED DEEPLY. IT TURNS OUT THAT WITHIN THE RANGE OF 24-52, THESE SEEDS ARE THE ONLY ONES WHICH SATISFY THE FOLLOWING CONDITION: THERE'S NO STATIONARY FIREFLY WHICH HAS TO BE RELEASED TO FINISH THE CAVE. AFTER PETER LIEPA CHOSE HIS SEEDS WITH THESE CRITERIA, HE ORDERED THEM IN TERMS OF DIFFICULTY. WHILE I THINK L1 IS CLEARLY EASIEST AND L5 CLEARLY HARDEST, L2-4 SEEM TO BE RELATIVELY CLOSE TOGETHER.   
SO HOW TO CONTINUE THIS PATTERN BEST? JUST LOOKING FOR THE NEXT RANDOM SEED

# .font: font.value_1
# .autowrap: false
DUSTIN                            2020-10-06 20:29
# .font: font.value_2
# .autowrap: true
OK, I'M GIVING UP. I CANNOT POST MY FULL COMMENT SOMEHOW :(

# .font: font.value_1
# .autowrap: false
DARKSTOORM                        2020-10-06 20:30
# .font: font.value_2
# .autowrap: true
dustin, WHAT COMES UP NEXT AFTER THE LAST CUT WORD?  
GONNA TEST SOME CHARACTERS:  
: ; ' " &LT; &GT; / ? [ ] { }

# .font: font.value_1
# .autowrap: false
DUSTIN                            2020-10-06 20:35
# .font: font.value_2
# .autowrap: true
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAH  
THAT'S PROBABLY IT!  
ONE MOMENT:

# .font: font.value_1
# .autowrap: false
DUSTIN                            2020-10-06 20:41
# .font: font.value_2
# .autowrap: true
RANDOM SEED: (24 45 52 30 40) 80  
THE FIVE ORIGINAL VALUES LOOK CHAOTIC, BUT SHOW A PATTERN IF ANALYSED DEEPLY. IT TURNS OUT THAT WITHIN THE RANGE OF 24-52, THESE SEEDS ARE THE ONLY ONES WHICH SATISFY THE FOLLOWING CONDITION:   
  
THERE'S NO STATIONARY FIREFLY WHICH HAS TO BE RELEASED BY SNAPPING OR ADVANCED TRICKS TO FINISH THE CAVE.   
  
AFTER PETER LIEPA CHOSE HIS SEEDS WITH THESE CRITERIA, HE ORDERED THEM IN TERMS OF DIFFICULTY. WHILE I THINK L1 IS CLEARLY EASIEST AND L5 CLEARLY HARDEST, L2-4 SEEM TO BE RELATIVELY CLOSE TOGETHER.   
SO HOW TO CONTINUE THIS PATTERN BEST? JUST LOOKING FOR THE NEXT RANDOM SEED ABOVE 52 WHICH SATISFIES THE ABOVE CONDITION LOOKS OBVIOUS BUT HAS ONE CLEAR DISADVANTAGE: IT'S VERY UNLIKELY THAT THIS RANDOM SEED WOULD INDEED HAVE BEEN A GOOD L6 8I.E. HARDER THAN THE ORIGINAL L5). SO I MADE A COMPROMISE AND CHOSE MY RANDOM SEED ACCORDING TO THE FOLLOWING CRITERIA:  
  
1. IT SATISFIES THE ABOVE CONDITION - NO STATIONARY FIREFLIES THAT HAVE TO BE RELEASED BY SNAPPING OR ADVANCED TRICKS TO CLEAR THE CAVE.  
  
2. ITS DIFFICULTY CAN AT LEAST COMPARE WITH THE ORIGINAL L5. ON L5, THERE ARE 9 FIREFLIES THAT MUST BE RELEASED, SO I LOOKED FOR A SEED WITH 9 OR MORE FIREFLIES TO RELEASE.  
  
3. THE FIRST SEED ABOVE 52 WITH BOTH CRITERIA WOULD BE MY L6.  
  
I HAD TO SEARCH UP TO 80 TO FIND MY SEED. HERE, THERE ARE ALSO 9 FIREFLIES THAT MUST BE RELEASED, AND AS 3 OF THEM ARE ALREADY IN THE STARTING AREA, THE START IS QUITE TRICKY, SO I THINK IT'S FAIR TO SAY THAT MY L6 IS ALL IN ALL SLIGHTLY HARDER THAN PETER LIEPA'S L5!  
THAT WAS A TRICKY ONE TO FIGURE OUT! :D  
  
\REQUIRED: (16/17 12/13 18/21 15/17 15/16) 10/12  
LEVELS 1-5 HAVE 1.6 BONUS\ ON AVERAGE, SO I THINK 2 BONUS\ ARE THE BEST THING TO DO.  
  
CAVE TIME: (150 150 150 150 200) 200

# .font: font.value_1
# .autowrap: false
DUSTIN                            2020-10-06 20:42
# .font: font.value_2
# .autowrap: true
FINALLY! THX darkstoorm, IT WAS A "GREATER THAN" SYMBOL THAT GOT CUT OFF :D

# .font: font.value_1
# .autowrap: false
DARKSTOORM                        2020-10-06 20:47
# .font: font.value_2
# .autowrap: true
IT'S WEIRD, BUT IT WENT THROUGH IN MY COMMENT :D  
/&GT; :&GT; TEST&GT;52  
  
HMMM

# .font: font.value_1
# .autowrap: false
DARKSTOORM                        2020-10-06 20:48
# .font: font.value_2
# .autowrap: true
DOESN'T MATTER, GREAT RESULT FOR A SPEEDRUN STRATEGY PLANNING ANYWAY! :D

# .font: font.value_1
# .autowrap: false
NESDORI                           2020-10-06 20:50
# .font: font.value_2
# .autowrap: true
dustin, I HAD SIMILAR PROBLEMS WITH "GREATER THAN" SYMBOL SOMETIMES. MAYBE BECAUSE IT'S CLOSING A HTML-TAG SO THE COMMENT GETS CLIPPED. krissz NEEDS TO DO COMMENT CONTENT VERIFICATION AND ENCODING IF NEEDED I GUESS.. :)

# .font: font.value_1
# .autowrap: false
DUSTIN                            2020-10-06 20:54
# .font: font.value_2
# .autowrap: true
nesdori, YEAH I ALSO HAD THE SAME PROBLEM EARLIER, BUT JUST FORGOT THE FACT THAT COMMENTS GET CUT OFF AFTER POSTING A

# .font: font.value_1
# .autowrap: false
NESDORI                           2020-10-06 21:05
# .font: font.value_2
# .autowrap: true
firefox TEST:  
  
2 &GT; 1

# .font: font.value_1
# .autowrap: false
NESDORI                           2020-10-06 21:06
# .font: font.value_2
# .autowrap: true
CHROME TEST:  
  
2 &GT; 1

# .font: font.value_1
# .autowrap: false
NESDORI                           2020-10-06 21:08
# .font: font.value_2
# .autowrap: true
STRANGE.. NOW I WAS ABLE TO INCLUDE "GREATER THAN" SYMBOL IN THE COMMENT WITHOUT ANY PROBLEMS WITH BOTH firefox AND CHROME. SO THE PROBLEM IS RELATED TO "GREATER THAN" SYMBOL BUT THERE ARE ALSO SOME OTHER CONDITIONS WHY IT HAPPENS SOMETIMES AND SOMETIMES NOT..

# .font: font.value_1
# .autowrap: false
DUSTIN                            2020-10-06 22:39
# .font: font.value_2
# .autowrap: true
HMM... I USE firefox.