Comment by JumpCrisscross
1 day ago
> Providing an offline mode doesn’t imply continued maintenance
There should be a liability cap for developers under a revenue ceiling and an exemption for free games. An indie developer shouldn't be worried about getting sued because a component of their game wasn't properly audited for offline use.
Indie developers don't build online games in general so you're making up strawman scenarios to defend multi-million corporations.
> Indie developers don't build online games in general so you're making up strawman scenarios to defend multi-million corporations
How does a revenue cap “defend multi-million corporations”?
Also, your premise seems wrong [1]. And plenty of offline games have online PVP functionality that I can absolutely see a small developer forgetting to configure in a way that has zero external dependencies.
[1] https://steamdb.info/charts/?tagid=492
Release the server code, job done.
> Release the server code, job done
Sure. Let's say you bungle that. Should it cost you your home? What if you die before you finish that work. Should your family lose its estate?
More trivially, what if you were a muppet and put a bunch of critical stuff in your environment, forgot to export that, and then shut everything down to deal with, idk, an illness or a child or any of the other stuff that might cause someone just making stuff for fun to change directions.
Bungle it how? If you release the code you are dropping all liability for it working or continuing to work after that point. You have no requirement to make it easier to use or set up. The only reason you would have to do any work at all is so you don't have to release your server code.
1 reply →
Release it open source in the first place
1 reply →