Adjacent minions sometimes not being counted as adjacent

[thoughthouse]

Some examples: https://www.reddit.com/r/hearthstone/comments/ecnl8z/bug_my_explosive_shot_didnt_do_damage_to_adjacent/ https://www.reddit.com/r/ArenaHS/comments/ecvl54/just_had_explosive_shot_fail_to_deal_2_damage_to/?ref=share&ref_source=link https://www.reddit.com/r/ArenaHS/comments/eaksju/bug_with_silvermoon_portal/ https://www.reddit.com/r/ArenaHS/comments/ebxiqb/new_bug_with_dire_wolf_not_buffing/?ref=share&ref_source=link

hsreplay links: https://hsreplay.net/replay/xbj5nJMpW4hffadeSqYhTD https://hsreplay.net/replay/mxnU9BomfErbDT36nchy3o

[Jetz72]

This post on the bug forums offers a pretty convincing explanation - https://us.forums.blizzard.com/en/hearthstone/t/explosive-shot-bug/21013/4

It seems that new cards, Grizzled Wizard and Kobold Stickyfinger cause this bug.

When you steal a weapon via Kobold Stickyfinger[ resp. swap hero powers via Grizzled Wizard], just like when you steal a minion, the weapon[ resp. hero power] you steal takes place in rightmost of battlefield. To be more specific, it doesn’t occupy the board(doesn’t affect on 7 minion limit) but it affects on the order(position) of minions.

https://imgur.com/a/viGDO4R

In the above two videos, the postion of cards are

1. leftmost minion A - (2. weapon) - (3. hero power) - 4. rightmost minion B To make this arrangement, steal weapon and swap hero power first and then (after you get your hero power back,) summon B via any effect that summon minion on the rightmost of board. If you play a new minion C on the right of B, since there are two minions on the left of C, C’s position become a 3rd. So, the order is,

2. leftmost minion A - (2. weapon) - 3. minion C - (4. hero power) - 5. rightmost minion B since the adjacent of minion C is ‘2. weapon’ and ‘4. hero power’, C’s ability that buffs adjacent minion doesn’t affect on A and B.(even if it looks like A and B are adjacent to C)

When you destroy a weapon[ resp. replace hero power], minion A[ resp. minion B] is adjacent to C and succecfully get the adjacent buff.(Can check it in the second video.)

They also claim it was apparently fixed by 16.0.5, but the patch notes failed to mention it.