# .font: font.text_2
2020-09-30 15:54 dustin  
# .font: font.text_1
hi  shredder ! it's been a while :)

# .font: font.text_2
2020-09-30 23:27 shredder  
# .font: font.text_1
hi  dustin ! :) nah, i just did one single shot ;) see ya soon ;) btw. grats - 77th cso :O

# .font: font.text_2
2020-10-01 00:55 dustin  
# .font: font.text_1
thx :D it's still a lot of fun! :D

# .font: font.text_2
2020-10-01 14:45 Arno  
# .font: font.text_1
which solution do you like more? the one with rockford disappearing or with rockford snapping the exit?

# .font: font.text_2
2020-10-01 17:37 dustin  
# .font: font.text_1
 Arno , i think that only both possibilities together make this mini cave interesting! :D a funny side effect is that if rockford disappears, the cave does not freeze. usually, we have two rules:  
1. if rockford disappears (=gets crushed), the cave does not freeze.  
2. if the cave is beaten, it freezes.  
obviously rule 1 dominates rule 2 with this engine!   
funnily, when i tested this cave, i did not even know whether it counted as success if rockford disappears. on one hand, the timer was added to my score, but on the other hand, the cave did not freeze and also i could restart the cave with the fire button, which is usually only the case after failure attempts! so for a short time, i had a slight hope that i found a way to strictly force the player to snap the exit instead of moving into it!   
but then i uploaded the cave for a minute to check what happens if i moved into the exit, and found that it did count as a success. so finally, the difference is only visual, but i still find it very funny :D