Describe the Bug:Tinder Wall always tries to charge you when activated; whether that's paid or cancelled, it sacrifices itself and adds to your mana pool. Also, it has no combat settings, so the AI will happily attack into it with creatures with toughness 2 or less as if they'd survive.

Which update are you using? (date, name)Which type? (duel, gauntlet, sealed deck)Dev master from about two weeks ago, 8865b7c.

What exactly should be the correct behavior/interaction?Charge only when activating to deal damage; add mana only when not charging it; cancel means cancel; and the AI is at least as reluctant to attack into it as into a Hurloon Minotaur. Though I guess anything that makes the AI less reluctant to attack into blockers isn't all bad.

Are any other cards possibly affected by this bug?The actual bug I was trying to test for, and couldn't, was whether it allows you to pay for its damage-dealing ability with itself despite the shared sacrifice cost. Looking at its implementation after the fact, it looks very much like, yes, it'll let you do that.

Also apparent from looking its implementation, but untested because the primary bug here interferes:

it never prompts for a target, even when more than one are legal;

it won't work properly when blocking banded creatures;

it can only damage the first creature it's blocking if it can block more than one, for example via Echo Circlet; and

Fixed only activation issues + A & D bugs in commit 13ca9a60. Also still no damage on resolution. For AI combat, I kind of disagree with

Korath wrote:so the AI will happily attack into it with creatures with toughness 2 or less as if they'd survive.

as it is a good way to get rid of Tinder Wall (as it has sacrifice cost for the activation) instead of AI not attacking because it fears it will lose a creature. Probably a hint not to attack ( or some negative AI value )with creatures with AI base_value above an X value unless it will win the game?