[Unstable] iLoveBacons Server [11/04 Build]

It doesn't. Me and a friend are having the same issue with your server.

 

This issue only happens in the server. I tested it in singleplayer, and my ship's loading perfectly fine.

 

It's one client-server related bug on latest build. For now wiping the client files fixed the black screens, not sure if they return, if so, poke me.

 

Weeelp, server was slain again. ;< Seems it was just an ordinary crash this time.

.. Do you think we went a bit overboard with the music? ;D

 

I tried to connect and it says the server doesn't exist.

 

@Son0fgrim @Cirom We eat Bacon, therefore we are.

And server is back up, not worrying much waiting for unstable branch, then unstable server.

 

Isn't the server already unstable?
Zing!

 

aw, but it's back still. Reporting the crash logs to devs, already collected 7 different types of crashes!

 

Is the server updated to the newest nightly build? because I still can't connect.

 

I'm getting the same error as Son0fgrim is.

 

@Son0fgrim @Pitaden @Heartstrings
The server is updated and back up. The recent build as well, the nightly / unstable are incredible hard to update because steamcmd doesn't work (this is a dedicated server).
That was why the odd crashes!

 

So, I kept trying to connect to your server, i tried and tried, and it error'd every time. Then, I go and I try other servers, then come back here. I got onto it from starbound servers eventually, and make a party (Having minor lag spikes, I attributed to me having lags + many people by me) so off me and my new friend go, and the ship doesn't stop, Ever. Eventually, I leave the game, come back here, and it hit me. This is Nightly build, I was on Stable. *MegaFacepalm*

 

I keep getting the same error over and over.

 

The main IP without the port, runs stable! But lol. Still the ship travel loop is a starbound issue on higher concurrency servers, to be fixed!

What Error? Server should be up now.

 

Same one I screenshotted.

 

It's broken again, hooray!

 

It was being updated, it's now on latest build again.

 

Wait, your running two servers off the same IP, one stable, one nightly... What...? Um. Well then. That's good to know. Now.

 

Yes, stable is the main one, but it doesn't uses all the resources of the server, so nightly is also able to run on it, the instability comes from nightly itself, many times requiring more than a restart.