Battle log record lifegain

Delnai

As it is currently implemented, the Battle Log makes it difficult to track Planeswalker life totals accurately. Here are two confusing things:

1) In the turn heading in the battle log, the life total listed is the life total of the planeswalker at the -end- of the given turn. This is confusing, as the Battle Log otherwise keeps tracks of things in a linear order. I would expect that the life total listed in the heading for a turn would be the -initial- life total of the Walker in that turn.

For example, here Nahiri is listed as being at full life in the Turn 6 header even though she just took 5 damage from a Bushwhacker:
https://imgur.com/a/0NzSi

2) Life gain is not tracked in the Battle Log at all, even though damage is. This asymmetry is unexpected; if damage is explicitly written, then life gain should be too. Not recording life gain makes it hard to track bugs with lifelink etc.

For example, here the life gained from the lifelinking War Oracle is not recorded, even though the damage from Chandra's ability is. https://imgur.com/a/2dWI9

(Incidentally, can someone tell me how to embed photos in a post directly from an iPhone? I'm bad at technology apparently.)

Alve

Delnai wrote:

(Incidentally, can someone tell me how to embed photos in a post directly from an iPhone? I'm bad at technology apparently.)

IMG tag () + the image's url. You need a direct link to your image - one that ends in .jpg, .png and such. On mobile it might be difficult to find, or even impossible, depending on your browser. In Mercury you need to long-press the image and choose Copy Link. Haven't found a good way to do that in Safari. Perhaps use other websites, like postimage.org (a random Google example), which provide you with a direct link straight away.

Remember to resize your image to fit the forum guidelines (1200 px), otherwise you won't be able to embed the images in your post.

It's generally easier to do it on a PC than iPhone

Delnai

Thanks, Alve. Sure does seem easier to do on PC. With the resizing needed, it's at least one step too many to be worth it on an iPhone...