# .font: font.text_2
2022-10-03 21:06 Arno  
# .font: font.text_1
just another |\-traffic-control idea! ;-D

# .font: font.text_2
2022-10-03 23:13 dustin  
# .font: font.text_1
this time, i mixed paperwork with trial-and-erroring because i was too lazy to calculate all firefly positions :d

# .font: font.text_2
2022-10-03 23:21 dustin  
# .font: font.text_1
great cave btw again! another time you took a cso trick and used it as a tool to make a bigger puzzle :d

# .font: font.text_2
2022-10-04 00:14 nesdori  
# .font: font.text_1
there are two different fly impact solutions (sync fly top or bottom). the |/\ column must be different in each case. but this is probably intended feature :)

# .font: font.text_2
2022-10-04 00:25 dustin  
# .font: font.text_1
funnily i had one right timing on my first random attempt :d then i made 3 test runs to find out which |/\ lands where in the end.

# .font: font.text_2
2022-10-04 08:00 Arno  
# .font: font.text_1
thanks! :-D  
  
i would expect 4 different solutions with different |/\ combinations, for the 4 timings of the stack release such that the items fill all 8 gaps. :-)

# .font: font.text_2
2022-10-04 10:39 nesdori  
# .font: font.text_1
 Arno , hmm, i could find only 2 timings that successfully filled the gaps so that the cave is solvable :)

# .font: font.text_2
2022-10-04 22:30 Arno  
# .font: font.text_1
my run visible! :-D  
  
hmmm... i tested again and out of the 16 timings from the cycle i see 4 timings which fill all 8 gaps at the bottom (with different composition of the |\ mix from the stack). timingwise there is always a gap of 3 frames between two successful timings. :-)

# .font: font.text_2
2022-10-04 23:02 nesdori  
# .font: font.text_1
 Arno , now i also checked it more carefully and you are right; there are indeed 4 timings. i must have been hallucinating.. :)

# .font: font.text_2
2022-10-04 23:05 nesdori  
# .font: font.text_1
 Arno , ..and it seems that we picked the same timing for our runS :D

# .font: font.text_2
2022-10-05 21:45 dustin  
# .font: font.text_1
i have the "opposite" timing :d