Port forwarding, and why it sometimes cannot work
Most guides assume the rule will work once you get it right. For a lot of home connections it cannot, and no amount of fiddling will change that.
Our story
SaveSync started with a simple frustration. AG and KB used to play Schedule 1 together. KB was the host. One day, AG was sick at home while KB was stuck at work. AG wanted to play, but couldn’t. The save lived on the host’s machine, and without the host, the game simply couldn’t continue.
As we started working on a solution, we realized we weren’t alone. Players across many different co-op games were asking the same question: “How do we keep playing when the host is offline?” That’s how SaveSync was born.
Save sharing solved half of it. Plenty of co-op games really want a dedicated server, so that nobody has to be the host at all, but that means downloading executables, hand-editing config files and forwarding ports on a router you may not even control. Most groups give up and rent one instead. ServerSync is the other half: pick a game, name your server, and it runs on a machine you already own.
We’re both game developers, working on SaveSync part-time, building the low-level systems, the UI, the guides, and the community, because we genuinely care about co-op games. Our goal is simple: to make co-op gaming better, with no file juggling, no forced subscriptions, and no barriers. Just play.
