I've tried to launch the game three five times now, and each time it hangs on a black screen that does that awful "go fullscreen while hijacking the user's WM so they can't escape"♥♥♥♥♥♥ forcing me to get creative to force-kill the game via a terminal that exists outside of my X server.

To fix it, and this is annoying as hell and not something I imagine an average user would figure out, I had to navigate to `~/.config/unity3d/Konstructors/WayOut` (which you'll only find via update-db + locate, or by starting the game from .local/share/Steam/steamapps/common/WayOut and navigating to the directory where it mentions a log is at), and look for a config file, which I found and it's called `prefs`, in the insane and inefficiently self-repeating plain text format that we call XML. Lo and behold, changing a 1 to a 0 mysteriously gets the game to work, unlike a certain television show where it destroyed an economy.

The issue is that I shouldn't have to do this. I'm launching the game from a GUI that handles all of that, so having to go around Steam to investigate the problem using the OS, while right up my alley, is not something the user should have to do, because it defeats the purpose of having a client designed to streamline the process of owning, installing and running a game. The moment the user has to open up a terminal to fix something, somebody on the upstream has failed their task, and it ain't Valve. The game should have sane defaults out-of-the-box. And fullscreen is not a sane default, no matter how you cook it, because it involves too many assumptions about the graphical setup of a given user's machine, which in my experience, almost always results in a broken startup (despite having a 1920x1080 display driven by an NVIDIA card) that forces the user to force-kill the game and manually dig into the game's config to repair something that is broken in a fresh install. Case in point, I had to disable fullscreen via a text file to get the game to actually start up. The user should have the option of setting the resolution and other options correctly BEFORE activating fullscreen, so that it actually has a chance of working, and has a fallback if it doesn't. They should NOT have to chvt into a TTY and force-kill the game from outside of the X server because the game hijacked their window manager rendering them completely unable to use their desktop until the stupid window-manager-hijacking black screen of death goes away. When your program undermines the Window Manager, you are doing something very wrong. Let the WM do its job, so the user can do their job, like escaping when a game enters a broken fullscreen mode. Better yet, program your game right so the user doesn't have to escape in the first place.

The Linux support is appreciated, but, umm, how about you guys test your games before you charge money for them? Crazy idea.

Unless you did test it and it just happened to work for you. In which case, consider this an unofficial bug report.