Allow me to rejoin my own local coop game after exiting.

If I host a local coop game and I quit to windows, I am unable to rejoin the game without having to shut down the "server" as well.

There are times I have been forced to quit due to internal error issues, this has been especially bad after Alpha 12.3, and other times when I quit manually or had to quit for other reasons.
If I quit to the menu I can rejoin no problem, its when I exit to windows I cannot do so.

Apparently windows or Steam or whatever think the game is still running and just maximises the "server" window if I try to restart the game.

So I would suggest that it be possible to restart the game again after having quit to windows and not need to ask people to leave the "server" because I have to close it just to be able to rejoin the session I'm hosting myself.

 

Have you tried connecting to:
127.0.0.1:30000

 

And how am I supposed to do that from Windows?
The problem is not rejoining from the main menu ingame.
The problem is starting up the game again from windows after closing it while still having the local coop "server" running.

 

How is that behaviour working when not hosting a local coop game? -> playing SP - well, quiting the game from SP?
If you get the same issue, then the issue is 'there'.

Try to verify the game files via steam, but first, do a proper restart of your computer -> so no applications are resident in memory while doing so.
Log out and re-log to Windows is NOT enough.
Maybe you had still some EAC-threads running in background (allthough you had it to disable to host, I know).

If it still bugs around afterwards, your best hope is the next EGS update, because in such cases, that is usualy what fixes the issue for me.
Not what you want to hear, but how it (probably) is.

Good luck

 

I appreciate you trying to help, but you don't seem to understand the problem here.
This has nothing to do with SP and it's not a bug, it's a game design thing

If I host a local coop game and I am for some reason forced to exit to windows(crash, interal errors, etc)
I can not restart the game if I do not shut down the "server" first.
If I try to restart the game while the local coop server is still running, then it will show me that window as if to tell me "look the game is already running".

 

I have to agree with the original post. I started a local coop game in order to design a new ship with my son. He wanted to keep playing while I had things to do. I quit the game(not the server as it runs as a separate entity) and he could keep playing, while I quit to desktop and I could see the server still running.

Now in Steam there is no "Play" button. It only says "Stop" as if the game is running. This is because I started the coop server from within the game rather than installing the dedicated server on this machine. Therefore I am unable to even start the Empyrion game at all while the server is running. The end result is I cannot rejoin my own server if it's started from within the game. Steam thinks the game is already running and will not allow you to start up the game.

It sounds like an odd description, but this is only because the coop server was started from within the game rather than a dedicated server and setting up the dedicated server in order to just build a ship seemed like a big pain so we did it this way. Now we have to shut down the server and restart the game, then restart the coop server from within the game again. Seems a bit silly, but yes this is the game design or at the very least how Steam handles the launching of the game/servers.

 

Looks like a bug in the EmpyrionLauncher.exe program. During exit of coop it presents this dialog...



...which gives instructions on how to rejoin but as you say, doing a simple launch pulls up the server and doesn't give you the option of starting the client.

You can work around the issue by manually double clicking the Empyrion.exe located in the /client subdirectory. Once there you can use the JOIN option with the IP address 127.0.0.1 (this is the loopback IP address for the local host) as @Sephrajin describes above.

You may want to drop a bug report in the bugs forum- the local coop option is simple approach to starting a LAN-visible server process without the overhead of manually creating config files but otherwise it's using the same bits as dedicated. The problem you've encountered doesn't appear to be intentional.

 

I have same issue and tried imlarry425 solution, but thing is that when I open game not via steam/epic laucher there is no multiplayer option and without multiplayer option there is nowhere to type ip address. I tried using console "JOIN 127.0.0.1" or "connect 127.0.0.1" I get error that there is no such command