I can confirm this, there is an electron process still running after closing the game. (fallout-0.6.0 electron) or something like that, guess it has to do with java. There's also a crash if you look into the Handbook about Khans Hideout. Apart from that, the game is well made.
Actually no, java has nothing to do with it. We are quite embarrassed to talk about this, but it is interesting.
According to the electron documentation, setting a directory for application data should create the directory if it does not exist, in a synchronous manner. In that version of the electron, this happened in asynchronous mode. At the launch stage in the latest versions of the game, a custom configuration file is written there, used to store user pre-launch electron settings. When launching the game on a new machine, trying to access a folder that does not yet exist to write a file, an error appeared and was successfully caught by our error handler. But since it is impossible to create warning windows about problems at this narrow stage of electron startup, the error handler itself crashed with an error! As a result, after all the errors have been caught, the game remains running but does nothing, because all the following initialization stages were not completed due to an error, and the electron process itself believed that this was how it should be. As a result, all new users launching the game for the first time could start the game only after the second launch, and the process of the first launch remained hanging.
