Board reshuffled in the middle of IM40 Recharge

Marvel Puzzle Quest MPQ Bugs and Technical Issues
1

I was playing one of the nodes in the Venom Bomb PVE today (sorry, can’t remember which one right now) and I placed the CD tiles for IM40’s Recharge. Two turns later, the first tile fired.

Now, I can’t remember exactly what happened, but it was either one tile resolved, the board reshuffled and a second tile resolved then IM40 went into his stun before resolving the third tile; or two tiles resolved, the board reshuffled and IM40 went into his stun before resolving the third tile.

At any rate, the board reshuffle happened mid-resolve and IM40 went into the stun before resolving the third tile which held at 1 for two turns. As soon as IM40 came out of his stun, the third tile resolved and IM40 stunned for two turns again.

I think it was either an easy or trivial node (might have been the one with Ares, I think) and I wasn’t really at risk of losing the match because of this. It was just annoying, more than anything, and another issue with board reshuffle you may want to look into.

2

I believe it happens when there are no matches, board resuffles. Here is topic for it already:

https://forums.505go.com/discussion/47480

3

This was the first time I saw it happen in the middle of IM40 resolving his CD tiles though. I figured if the board was going to shuffle, it would at least wait until all the CD tiles resolved, because perhaps the final one resolving would result in a match or at least a possible match.

And as I said before it didn’t cause me to lose the match or anything, but it was annoying to have IM40 out of commission for essentially 4 turns because he was stunned for 2 turns after the first two CD tiles resolved, then as soon as he came out of the stun the final CD tile resolved, stunning him for 2 more turns. Not a game changer in this instance since I was on a trivial or easy node, but at a higher level it definitely could have been the difference between a win and a loss.

4

This happened to me once too. It’s just one of many aspects of the board reshuffling bug. Supposedly the next patch (due today!) will fix this error.