Recap:
> Client-server architecture does make things more complicated to implement but it's not THAT bad. Among Us was literally a three-person team.
The scope of the discussion extends beyond simple games like Among Us and some games require highly complex networked architectures that would be non-trivial to open up.
That said, I don't mind a tangent, and I have built services for large multiplayer games and it really is not that bad.
Untangling the entire lot to make the game available upon closure would be a nightmare in some cases.
I've also contributed to game server emulation (pre-professionally) to keep them alive, so preserving games is a cause I support, even if I don't think it's necessarily always going to be trivial.
This is only true if the game wasn't architected with open-sourcing in mind. Which affects how this kind of law should be structured.
For example, it makes sense to require the server code to be submitted to an escrow service from the beginning. Part of that process would be a license evaluation, which acts as a forcing function already during the development process.
Yes there was. It was a 3 person team. That's a good enough reason to not have almost any feature that requires any amount of work, including UI work, because there is always a whole mountain of stuff that you're not doing that you'd like to do as a 3-person dev team.