Order of Operations / Restrictions Using

Greetings all,

I've been making some progress on my simple puzzle game using colored blocks, but I've hit a snag.

[color:#FF0000]The game is simple enough:[/color]
- clear the array of colored blocks from the play area.
- The player uses a sequence of colored cursors to perform actions on the array of blocks (each cursor contains 2 equal parts like a Dr. Mario pill).
- If the colored cursor is the same color as the block, destroy the block.
- If the colored cursor is a different color than the block, change the color of the block to the color of the cursor.
+ Here's the fun (and complicated) bit:
- Whenever a block is destroyed or changes color, perform the same action on the adjacent 4 blocks if they are/were the same color as the block being destroyed/changed.

[color:#FF9900]Currently,[/color]
I've managed to get the destruction event working fine, and I've been trying to adapt a similar code for the color change, but have realized there are some issues.
Such as the order the operations execute in, and overlapping loops (like placing a cursor with 2 different color halves on the same chunk of one color).

[color:#999900]So my question is:[/color]
Any information on how I can structure the order of operations in MMF2D while not within FastLoops? Should I be using FastLoops for all of these actions? What would be the best way to deal with the overlapping issue of changing colors?

Here's a link to the current version of the MMF file and a simple readme to go along with this post:

alexg_mmf2d_issue.rar

I'd greatly appreciate it if you would take a quick look at it and see if there is anything I can change to fix any of these issues.

[color:#CC33CC]The Forum has been a great resource for me thus far, thanks very much![/color]

Sincerely,
~ Alex G.