@Altrean

I think what it should be for Bone Fortress is that BF always get to heal first because otherwise it is quite too weak.

And I just curious about how you program the checking if figures will die.
I guess you must check it at the beginning of each round(evidence = emerald spring).
and you seems to always check some special case first?(evidence = putrid zombie).

We check it after end of round actions.We recheck death if any perm died.

Here's example for you: two Bone Fortress with 0 and Awaken the Stones in play - what to do in such case according to your rule?

ugh ... I like that example.

I think that case need more players' opinion.
I'll try to give some choices first:

1) If I follow what I suggested last post - checking creatures' death for first iteration then buildings' death for second iteration with each iteration goes in order of creation - the result should be that the awakened BF which was created later survives.
-> In my opinion that isn't fair.

2) So if I have to change what I suggested last post, another solution comes which might as well oppose the concept that "events in the same round happen simultaneously". The other solution is: to have a list of dying figures for each round ordered by the time when figures' HP reach <= 0 then process the death check by this list.
This will also encourage the strategy to attack first. In addition, if figures like the 2 awakened BFs die from the same event, just let them both die.

I like what Billiska says.
First to be on 0 lifes, first to be checked and everything according to it's death counted..
Supports thinking

Well, all this looks good at first look, but it breaks similarity of events: why some events should happen in one order and other events in another order.
This order matters not only in after end of round events that we discussing right now. Here's another weird example: Two Emerald Springs in water, with Awaken the Stones in play.

While symmetry is nice, I'd rather have the common case be something sensible (order of deaths and on death effects) than have it be consistent with rarer/more pathological situations. In particular, I don't even know what would happen *now* in your stones / spring example. Does it depend on the relative order of casting the springs and awaken the stones? Its not clear why this should be.

Result depends only on order of springs creation: both heal and loosing HP in water happens at end of round, so first one spring heal everything around and loose 2hp, then second heal everything around (1st spring healed) and loose 2hp.

Some kind of visual change to bone fortress would be great. For example, make it transparent if it's going to die, leave it if it's not.

Or another thing that would be nice, is if there was some sort of number on each entity, to mark it's order of creation?

Just a reminder.
There's another card that needs detailed explanation - Draknor's chain.
I noticed that it works differently from the beacon.
This detail will be necessary for anyone who is trying to drawn opponent's creatures with the chain.