# .font: font.text_2
2020-06-13 12:51 dustin  
# .font: font.text_1
wow, congrat! i have problems with this even with 2 frames/second ;d

# .font: font.text_2
2020-06-13 13:31 DarkStoorM  
# .font: font.text_1
Timing the movement is my favorite thing :D  
  
For me it's almost like memorizing a specific set of rhythmic patterns or short paths, mostly repeated.  
  
Like in your rotator amoeba cave, if you "deconstruct" the demo, there are specific steps which helped me memorizing the cave in a way that I can make an identical run every time, like:  
  
1) position to the correct starting tile  (upper Space tile above the right boulder)  
2) move to the top-right of the FFly  
3) repeat L, U, L, U, U three times (DIRECTIONS)  
4) free the FFLY to not disrupt the blockage  
5) Drop the diamond  
6) roll the three double-vertical boulders down  
7) Block the remaining hole  
8) Drop the T-Shaped boulders and snap down+left(Step 3 created a path just for that)  
9) Slope up the boulders  
10) remove one boulder from the firefly and push it to cover the hole  
11) Explode the FFly to not disrupt the blockage again  
12) Block the rest  
  
After a few tries, all of that creates a pretty straightforward connected path, easily repeatable.  
  
That's just one of the techniques!  
There's also delaying the movement with snapping (reference to the Rocky and the Rock cave)

# .font: font.text_2
2020-06-13 18:17 dustin  
# .font: font.text_1
 darkstoorm , that's very interesting! actually i work a lot with such repetitions when playing new caves or levels in other games, too. i noted that, when i play a new cave and have my first, intuitive solution strategy, i tend to stick with this strategy for many many tries before even thinking over it and trying to find a better one ;d

# .font: font.text_2
2020-06-14 20:37 dustin  
# .font: font.text_1
oh, i just noted an interesting detail. shouldn't rockford explode when he exits in  Arno 's solution? or does this site's engine not finish the final frame?

# .font: font.text_2
2020-06-14 21:11 DarkStoorM  
# .font: font.text_1
I actually tested it with outboxes on all sides of the firefly, delaying.  
  
It happens in GDash in many different conditions.

# .font: font.text_2
2020-06-14 21:15 DarkStoorM  
# .font: font.text_1
I started wondering if that's only the outbox thing. I don't have that much knowledge to analyze it :D

# .font: font.text_2
2020-06-14 23:42 dustin  
# .font: font.text_1
 darkstoorm , in gdash - and i think also in the original bd - it's possible to explode when hitting the outbox. i think it's just because the engine finishes the cavescanning for the frame even if rockford exits.  
  
for example, the situation in this cave when rockford exits:  
  
ro  
bf  
r=rocky, o=outbox, b=boulder, f=firefly.  
the last frame starts and r is scanned first - he moves right, into the outbox, thus completing the cave.  
but the cavescanning isn't over yet - it's still the firefly's turn, which sees rockford above it and explodes. at least, that's what happens in the gdash/ original engines. this effect always occurs if rockford exits and at the same time touches a fly from left or above. if rockford touches a fly from right or below, he survives the actual frame. he would then explode next frame, but as there is no next frame, it's not visible.  
  
this site's engine, however, seems to give rockford an "invincible state" the moment he reaches the outbox, so the firefly can't harm him anymore. of course, it's just an optical effect without any technical relevance, but i still find it funny ;d

# .font: font.text_2
2020-06-15 00:11 DarkStoorM  
# .font: font.text_1
 dustin , I just checked the GDash source, because I was not sure anymore. It actually does not interrupt the cave scanning routine, so it behaves just like you explained.