Any method to debug long "Waiting for opponent..." delays?

[elricod]

It doesn't happen with all decks or board states. But several turns into a reasonably complicated 4-player EDH game, the computer may stay on "Waiting for opponent" for 15-20 seconds per resolution, which gets rough when there are 30 triggers on the stack.

Not asking for a debug from developers. I am more looking for additional switches or parameters to pass Forge when I launch, to increase the verbosity of the forge.log or a similar location.

I am hoping if I can find which decision tree the AI is getting stuck on, I can avoid decks with those cards entirely.

[resonantmadly]

You can increase verbosity by launching Forge with the -debug flag, which may provide more detailed logs. Additionally, check the forge.log file, typically located in the Forge installation directory. This can give you insights into where the AI is getting stuck, especially around complex triggers. To troubleshoot specific deck issues, you might try isolating cards or mechanics that trigger delays by testing the decks in smaller games or using a simplified board state.

[mariahcarey]

You can increase verbosity by launching Forge with the -debug flag, which may provide more detailed logs. Additionally, check the forge.log file, typically located in the Forge installation directory. This can give you insights into where the AI is getting stuck, Clashdleespecially around complex triggers. To troubleshoot specific deck issues, you might try isolating cards or mechanics that trigger delays by testing the decks in smaller games or using a simplified board state.

When launching with the -debug flag, do I need to add it right after the .jar command (like java -jar forge-gui-desktop.jar -debug), or is there a specific syntax or launcher option for it?