Reason // Believe causes screen freeze (related to Naru Meha and Aftermath spells) [Fixed in 2.7.1]

Beclas

Twice this HoD event I've had the Nicol Bolas node freeze suddenly. Both times I've just cast Reason, drawn cards and then nothing. Aftermath activation doesn't appear and nothing else in the game responds but the menu and battle log. I have played Reason often, but this is probably the first time when Naru Meha is in the mix. I'm not sure if she filled the Reasons before I cast them or if they are copies created by her, but it is a possibility. Also, this seems related to two other bug reports from May. To get more attention for the bug, I'm raising this as a new discussion and merely mentioning the two other discussions:

https://forums.d3go.com/discussion/comment/806968

https://forums.d3go.com/discussion/comment/806037

I've attached the two battle log screenshots from both freezes. After studying them and those other bug posts, I think this is the interaction between Naru Meha copies and Aftermath spells. I'll try to test it more in Training Grounds, but this should be fixed asap.

//Edited Title -Brigby

gogol666

I've also seen strange behaviors with tetzimoc: its ability is like a kicker and cause freeze on different occasions for me

Beclas

Tested this in Training Grounds and I have four losses to prove it. Here's my conclusion:

When the effects that copy spells (at least Naru Meha and The Mirari Conjecture third chapter) happen to copy a spell with Aftermath, the copy is flawed. When the copy with Aftermath goes to graveyard, be it by casting it or by discard, it causes the game to freeze. I tried it with three different Aftermath spells and both Naru Meha and The Mirari Conjecture. Every game the copy hitting graveyard caused the game to freeze.

@Brigby this title should be edited to something like "Copied Aftermath spells going to graveyard causes the game freeze" and you should bring this to the dev team's attention. This affects so many spell combinations (with Reason being the commonest, I think) that it should be fixed quickly.

Brigby

Update: This issue should be fixed in the upcoming 2.7.1 build