# .font: font.text_2
2020-10-06 20:23 dustin  
# .font: font.text_1
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.text_2
2020-10-06 20:26 dustin  
# .font: font.text_1
shit, my comment somehow got cut off?!?! continuation:  
  
so how to continue this pattern best? just looking for the next random seed

# .font: font.text_2
2020-10-06 20:26 dustin  
# .font: font.text_1
something's wrong with the comments... :(

# .font: font.text_2
2020-10-06 20:28 dustin  
# .font: font.text_1
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.text_2
2020-10-06 20:29 dustin  
# .font: font.text_1
ok, i'm giving up. i cannot post my full comment somehow :(

# .font: font.text_2
2020-10-06 20:30 DarkStoorM  
# .font: font.text_1
 dustin , what comes up next after the last cut word?  
Gonna test some characters:  
: ; ' " &lt; &gt; / ? [ ] { }

# .font: font.text_2
2020-10-06 20:35 dustin  
# .font: font.text_1
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaah  
that's probably it!  
ONE MOMENT:

# .font: font.text_2
2020-10-06 20:41 dustin  
# .font: font.text_1
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.text_2
2020-10-06 20:42 dustin  
# .font: font.text_1
finally! thx  darkstoorm , it was a "greater than" symbol that got cut off :D

# .font: font.text_2
2020-10-06 20:47 DarkStoorM  
# .font: font.text_1
It's weird, but it went through in my comment :D  
/&gt; :&gt; test&gt;52  
  
Hmmm

# .font: font.text_2
2020-10-06 20:48 DarkStoorM  
# .font: font.text_1
Doesn't matter, great result for a speedrun strategy planning anyway! :D

# .font: font.text_2
2020-10-06 20:50 nesdori  
# .font: font.text_1
 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.text_2
2020-10-06 20:54 dustin  
# .font: font.text_1
 nesdori , yeah i also had the same problem earlier, but just forgot the fact that comments get cut off after posting a

# .font: font.text_2
2020-10-06 21:05 nesdori  
# .font: font.text_1
 Firefox  test:  
  
2 &gt; 1

# .font: font.text_2
2020-10-06 21:06 nesdori  
# .font: font.text_1
chrome test:  
  
2 &gt; 1

# .font: font.text_2
2020-10-06 21:08 nesdori  
# .font: font.text_1
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.text_2
2020-10-06 22:39 dustin  
# .font: font.text_1
hmm... i use  Firefox .