The game launcher incorrectly reported a game error as a crash

[Thc128ai]

After installing the "RuSureQuit" (confirmation before quitting the game) mod, triggering the Minecraft shutdown operation did not close the game promptly, which caused a watchdog error (not closing or staying too long on the "Confirm quitting the game?" interface, since this interface does not freeze other processes and is also considered as "the game not closing"). The launcher supporting many practical features (hereinafter referred to as the "LazyDog Launcher") incorrectly displayed a game crash and popped up again.

Error type: java.lang.Error: Watchdog
Description: Client shutdown
Thread: Client shutdown watchdog
This is part of the normal game shutdown process but was reported as an exception by the monitoring thread. The game did not crash; it merely triggered the monitoring mechanism during the shutdown process.

The launcher hides after starting the game. It monitors the game process exit code. If the exit code is non-zero, it assumes the game exited abnormally. The launcher then reappears and reports an error.

Reason: The mod "intervenes" when the "shutdown" logic starts running, at which point the game is in the "shutting down" state. For example, if the shutdown process gets stuck halfway, such as during the "memory cleanup" phase, it cannot be forced to close—where would the cleaned-up memory go?

Solution: Decide "whether to start the shutdown process" before the "shutdown game" process runs or before the watchdog is activated.

Annoyance: This LazyDog Launcher is not very "smart." It cannot manually bind to the game process or hide the taskbar. As a technical survival player, I need to use other programs during gameplay, so the game must be displayed in windowed mode. This launcher's program interface can only be minimized or closed, which is very annoying for me.

Machine translation may lead to errors.