Argh! I can't believe it's the middle of 2019 and I'm writing about something so ridiculous. Pathea Games, developer of Planet Explorers and My Time At Portia have lost the multiplayer code for Planet Explorers.
As a little reminder, Planet Explorers was funded on Kickstarter way back in 2013 with the help of over four thousand backers providing them well over one hundred thousand dollars. When it released in 2016 it was…rough. It had a lot of promise, some elements of it were interesting but it also had a lot of bugs.
In early May this year, Pathea Games wrote on Steam about their server being down, then in early June they wrote about there being "more loss than we anticipated" and then late June where they announced "our lobby server had an issue where all the code base got deleted from its server" and "it's a lost cause unless we completely rewrite the code from scratch".
Backups, Backups—Backups!
They don't seem to have any kind of backup of their working version, which is completely crazy considering the masses of free storage you can find online. It's also very easy to start using version control systems, with plenty of free storage for that also available in numerous of places, so I'm struggling to understand how they could lose everything like this.
Pathea Games have now made the game free and they said they will be looking to "make the game code available online" hopefully under a decent license allowing others to hack away at it, perhaps giving it a new life.
On top of that, they also said they're working on Planet Explorers 2 and they've "matured as a studio", but I don't really know how they could write that with a straight face in these circumstances.
You can find Planet Explorers on Steam.
QuoteWe used a software called U-link for PE, and that software is now defunct. Even if we had the original U-link code, we still don't have the configurations and additional code we wrote back in 2013.
If they coded against this platform, then their code would be useless even if they had it. That can easily happen to anyone relying too much on proprietary cloud service.
Last edited by Linas on 3 July 2019 at 11:19 am UTC
Their decision to release the game for free strikes me as sincere mea culpa and is appreciated. I'd absolutely love to see them release the source code as I can imagine the Community transforming this game into something quite spectacular.
Last edited by Nanobang on 3 July 2019 at 11:56 am UTC
Quoting: PsychojauIt's always complicated nowadays when you are a small indie : free storage is nice but... is anything free ? Versioning systems for closed sources have a cost and there is always the bandwidth problem : game projects are HUGE. Not only you have all the game content and it's sources, but you also have a lot of garb** *erm* a lot of things that won't always be useful in the near future lol.
In this case we're talking about server code, so it's probably a 100% text files. You don't need such huge amount of disc space for that, not to mention that if you use a version control system like git (with a remote in a local server of your own) you will have your repository replicated on the computer of each developer for no cost.
I can accept that a game code from the 90s is lost for ever due to "reasons", but something developed in the last 10 years cannot be excused unless I think that this devs are a bunch of novices/inepts.
Quoting: Guestzede05 [developer] 26 Jun @ 3:58am
@The sap is rising! We have all of our available code backed up on our SVN server. But the programmer that wrote the lobby code back in 2014 wrote some of the code directly to the lobby server. So we don't have these, and since this programmer isn't here anymore, and probably wouldn't remember what he wrote even if he were, the entire thing doesn't work unless we rewrite.
The old trick of writing code in production... nice! Still, they should have something at least. Either case, hope they finally move to git for their next project.
Quoting: GuestJust going to copy & paste from a developer replying to the issue. Basically this is less a backup issue, more a development process enforcement issue (if they'd forced proper development processes on all developers, then the code would have gone into the backups properly).Well, to counter-argue here. That's still a backup issue, they clearly do not have all their available code backed up. If someone writes code directly and you don't have a copy of it, you don't have a backup.
But I can see how this could have happened, and it's a good example of why rigid code submission structures exist in some organisations, even if they can be annoying sometimes.
Bear in mind that lobby server itself was taken out. Quote is:
zede05 [developer] 26 Jun @ 3:58am
@The sap is rising! We have all of our available code backed up on our SVN server. But the programmer that wrote the lobby code back in 2014 wrote some of the code directly to the lobby server. So we don't have these, and since this programmer isn't here anymore, and probably wouldn't remember what he wrote even if he were, the entire thing doesn't work unless we rewrite.
Quoting: g000hEven if their source control server went down, it is usual for developer workstations to retain much of the working code. (True of git, perforce, subversion anyway.)
Exactly this. Where I work all the developers have each a complete copy of all our source code (myself I do a "svn up *" every morning) on our work computers, many of us have it on our home computers as well. Then the subversion server is backed up to a remote server in a different country. And we are a small 8-person company.
See more from me