# .font: font.text_2
2020-06-22 18:52 DarkStoorM  
# .font: font.text_1
Free :d/

# .font: font.text_2
2020-06-23 09:42 dustin  
# .font: font.text_1
wow... ;D ;D

# .font: font.text_2
2020-06-23 10:34 nesdori  
# .font: font.text_1
this might be an unique feature to  krissz 's engine that it's possible to step out and step back under a boulder when the boulder is on the border. i wonder if this is possible in gdash?

# .font: font.text_2
2020-06-23 11:02 DarkStoorM  
# .font: font.text_1
nOT SURE YET,  nesdori , i WILL CHECK SOME STUFF WHEN i GET BACK FROM WORK.  
  
iF THIS IS UNIQUE TO THIS ENGINE, WE SHOULD USE IT!  
tHERE ARE DEFINITELY SOME INTERESTING BEHAVIORS, ESPECIALLY WITH FLIES, AND  Arno  SHOULD DEFINITELY TAKE A CLOSER LOOK AT IT ;)

# .font: font.text_2
2020-06-23 12:34 nesdori  
# .font: font.text_1
now that i thought about this more there's a good reason for this behaviour. without this it would be impossible to rockford to move down safely when vertical border is open, rockford is on the top row and there's a boulder on bottom row. gdash does this differently; it impossible to step out and step back but it's also impossible to rockford to survive when he's on the top row and boulder on bottom and rockford moves down. the boulder will immediately follow rockford and during the next frame rockford will be killed because the boulder gets scanned first.  krissz  did this fix on purpose and i like  krissz 's engine behaviour more than gdash implementation. this is not rockford related fix but it works for any moving object under a border boulder.