search

PennyDreadfulMTG / modo-bugs

Issue Tracker for Magic Online bugs
6 stars 1 forks source link

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

Open MagicalHacker opened 1 year ago

MagicalHacker commented 1 year ago

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

image

https://user-images.githubusercontent.com/40921657/218572342-dda5b04d-2106-44c0-99b3-b54b86c570a1.mp4

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

Card Images

MagicalHacker commented 1 year ago

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

silasary commented 1 year ago

Oh, hmm. That's very not good

MagicalHacker commented 1 year ago

I've added the screenshot now

MagicalHacker commented 1 year ago

This issue is still unresolved.

silasary commented 1 year ago

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 commented 1 year ago

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 commented 1 year ago

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

MagicalHacker commented 1 year ago

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.