# .font: font.text_2
2021-08-10 23:20 altermaven  
# .font: font.text_1
i'm sure there's some shenenigans about liberating one of the boulders and not needing the magic wall but .... ;)

# .font: font.text_2
2021-08-11 14:42 dustin  
# .font: font.text_1
ah, you mean you wanna throw the liberated | through the magic wall and convert the amoeba this way? but you'd still need at least one piece of magic wall then ;)  
could be an interesting idea for a remake, though :d

# .font: font.text_2
2021-08-11 16:08 altermaven  
# .font: font.text_1
I have found doing that is actually worse than just letting the amoeba overflow, considering there's already a gap for the resulting diamonds to go through the wall and turn into boulders. Which is bad!

# .font: font.text_2
2021-08-11 17:53 dustin  
# .font: font.text_1
hmm... maybe it's still possible to get more \\\ that way. after all, with the intended method you also won't convert every |||.

# .font: font.text_2
2021-08-11 20:29 DarkStoorM  
# .font: font.text_1
;)

# .font: font.text_2
2021-08-12 12:55 DarkStoorM  
# .font: font.text_1
I like how it's possible to exceed amoeba growth limit :D

# .font: font.text_2
2021-08-13 09:48 dustin  
# .font: font.text_1
oh, very interesting! now i'm wondering if this is also possible with other bd engines :d  
  
but thinking of it, it's quite logical: if an amoeba overgrows, the "convert into |||" checkmark is activated only at the end of the cavescan. so the magic wall still had the chance to set the "convert into \\\" checkmark" during the cavescan :d

# .font: font.text_2
2021-08-13 10:27 nesdori  
# .font: font.text_1
it's not possible to get "over amoeba limit" number of \:s with the original bd1 bug. all amoebas which are scanned before the | which falls into the magic wall triggering the bug must be enclosed or otherwise conversion won't happen. and because scanning is restarted after scanning the falling | free amoebas which would be normally scanned after it never get a change to grow during that frame. conversion to \:s will occur during the next frame so there again amoebas don't get a chance to grow anymore.

# .font: font.text_2
2021-08-13 10:50 nesdori  
# .font: font.text_1
there's one interesting bd1 bug case: what if amoeba reaches the limit and all amoebas are below the magic wall and immediately during the next frame | falls into the magic wall and bug occurs. amoeba is not yet converted into | during that frame because of scanning restart. in that case both amoeba statuses are true during the next frame; limit have been reached and amoeba was fully enclosed during the last frame (or at least the engine thinks so because of the bug). then it's a matter of ruling order and i actually checked bd1 assembly code to find out which rule is stronger. the limit check is done first so converting to | is stronger rule than converting to \. so it indeed is not possible to pass the limit even in this special case :)