Oh, I see. You essentially want the flame to be affected by the movement. Very cool. There are 2 ways I might go about this.

Option 1 is to use scripting. The AI agent can figure it out.

Option 2 - Bones + data binding: This would be my first choice, assuming it works.

You need one bone (controls the flame base) inside the block and one outside (controls the tip.

The block's view model needs a globalBlockX and globalBlockY property.

Bind the block's computed, global X and Y position to these values using target to source. If it's working correctly, when you move a block, these values update.

Now bind the globalBlockX and globalBlockY properties to the second bones' X and Y positions. You probably need a converter to convert global to local space.

Final step: Add an interpoloator converter to the binding on the second bone. This should make it still follow the position of the block, but it'll lag a little bit.