Do not force Console to front when errors occur

[Roescoe]

The console should not obstruct interaction with the game, even in a broken game state. This prevents further interaction with the game for errors which the player may not care about and renders further testing impossible for errors the player does care about.

 

[Riamus]

The console should not obstruct interaction with the game, even in a broken game state. This prevents further interaction with the game for errors which the player may not care about and renders further testing impossible for errors the player does care about.

Errors are important to know about. If you don't deal with correcting the problem, you have a high chance of a corrupted save. It is a good thing that they appear the way they do. You should not be getting any errors if you have your have properly set up.

 

[Roescoe]

" You should not be getting any errors if you have your have properly set up." Agree, however if the application is still running, why does the console block interaction with the application other than the console? Additionally if the errors could result in a corrupted save why don't they crash the game? or take you to the main menu? Consoles are expected to show errors, not prevent them.

Also when the console spams with errors it doesn't allow you to exit the game, so you are unable to leave if you wanted to prevent "a corrupted save" due to the esc button only temporarily closing the console. a console with an infinite loop itself is an error which can be prevented by leaving it in the background like consoles in every other app I've ever used.

 

[Riamus]

" You should not be getting any errors if you have your have properly set up." Agree, however if the application is still running, why does the console block interaction with the application other than the console? Additionally if the errors could result in a corrupted save why don't they crash the game? or take you to the main menu? Consoles are expected to show errors, not prevent them.

You can close the console unless you are getting non-stop errors, in which case, the game isn't going to work anyhow.

Not all errors cause an immediate inability to play the game. Not all will corrupt a save. If the game closed every time you got an error, most people wouldn't know what was going on. Apps should not crash to desktop...ever. They should properly handle errors by displaying them and then let the user close the app. That is how a properly programmed app should function.

The console DOES show the error and doesn't prevent the errors. Not sure why you said otherwise.

 

[Roescoe]

The console blocking the user from interacting with the app doesn't allow the user to do anything about the error the user is receiving. Many threads have complained about how the console error spam forced them to kill the process as the only valid way to continue, despite the game functioning, albeit partially.

See:

https://www.reddit.com/r/7daystodie/comments/re4lej/anyone_having_issues_getting_to_the_menu_with

https://steamcommunity.com/app/251570/discussions/1/618458030670556259/
https://digistatement.com/7-days-to-die-error-log-keeps-popping-up-how-to-fix-it/
https://steamcommunity.com/app/251570/discussions/1/1742231705671142705/

All "Solutions" say, "just stop making it spam." That's not the underlying issue of the poorly designed console though. Just because the user is improperly using the game doesn't mean the console has an excuse for being badly designed.

 

[Roescoe]

To rephrase:
I say: that if the game encounters an exception that should be printed to console, but the console itself should not force focus away from what the user mouse is doing in-app, or from interacting with the pause menu.
You say: "They should properly handle errors by displaying them and then let the user close the app." Which is maybe the same thing? I'm not sure. Note this is not the current behavior.