Just a heads up: An upcoming build is likely to break this mod in a pretty harsh way if you expected your planets to be movable. It's looking like they will be adding a slider in the system editor to control how many halleys you need, which may or may not cause all planets in existing systems to be impossible to move. I don't expect it to break the mod beyond that, though.
Hi guys I update my systems quite frequently and everytime I share a new version (with or without the same name) it pop ups in shared system list. First I don't wanna spam the server with the same system over and over again so will there be any feature to delete systems from the server (hoster only?). And even more importend we need a feature to allocate a certain system name to a hoster and make it possible for the hoster to update it (overwriting the existing one). Last question: Is there a way to vote for systems? Thanks for the answers!
I could make a delete option, but then it would be very easy to hack and delete all of the systems because there isn't actually any authentication being done (shhh don't tell anybody!) The same thing is true for editing systems, unfortunately. So for now just spam the server as little as possible, but don't be too afraid of duplicates. The reason for the restricted servers was to make a place where people can find good systems without having to deal with the chaos of the main server, so it's pretty much a problem I tried to solve by ignoring it. There is no way to vote for systems because I'm lazy.
You could stop beeing lazy .. Nah, I was just kidding. The game isn't done yet so take you time implement those stuff
Uber will be replacing it with their own version evenually anyway. This is just something we can use until hey get around to doing it the right way.
Updated to v1.2.0 eXodus eSports now has their own server on System Sharing. I have also decided to just require the Enhanced System Preview mod, because you really should be using that anyway and this also fixes a minor visual bug.
Updated to v1.4.0 I cleaned up the server list, added a Realm server, and changed the way the server list works. Now instead of needing to push an update every time I want to change the list, I can just change the server list json that it looks for on Github.
Probably because the date-field didn't change. PAMM for Windows uses the date to compare versions, rather than the version number itself. So if the date-field between two updates stays the same, you'll get no notification of an update being available. I usually put the date to tomorrow if I have to release two updates on the same day. (PAMM for Linux/Mac compares version numbers, so this issue doesn't occur there.)