Responding "!notbugged" or "!stillbugged" during a 4-player Commander game in the open play room causes the game to restart

[MagicalHacker]

After responding "!notbugged" or "!stillbugged", PDBot should reply something.

No response from PDBot and the game restarts.

Support Forum Thread

Forum Post:

Screenshot
https://i.ibb.co/HXN8mZM/clipimage.jpg

video1414031601.mp4

Please provide a list of affected cards
Affects: None/All

Card Images

[MagicalHacker]

My current workaround is only hosting games with no watchers to prevent PDBot from causing the game to restart.

[silasary]

Oh, hmm. That's very not good

[MagicalHacker]

I've added the screenshot now

[MagicalHacker]

This issue is still unresolved.

[silasary]

I've removed the Call to Action, but there's not really much else I can do, because this is an MTGO bug, not a PDBot one

[MagicalHacker]

I would say that it might be a wise decision to change what PDBot requests as a response to workaround this current response triggering a mtgo crash. Possibly requesting "to pdbot: still bugged" instead of "!stillbugged". Just a thought I suppose.

[Rowsol]

How is it even possible for a spectator to reset a game?

[MagicalHacker]

How is it even possible for a spectator to reset a game?

I don't think it is. I think that typing that response somehow breaks MTGO, so I am suggesting that the response requested from PDBot be changed to prevent that from happening. People wouldn't be typing the thing that breaks the game if PDBot wasn't asking them to.