I'm countering your argument that it's "not that bad". If that wasn't your point with mentioning the three person team, what was?
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.
Ah, I see. Well, the post I was responding to reads to me like a denial of the existence of games like Among Us when it says it wouldn't affect three person dev teams making games on a shoestring budget, and gives off the weird implication that it would only affect big budget games.
That said, I don't mind a tangent, and I have built services for large multiplayer games and it really is not that bad.
I've also worked on MMOs and the architectures there can get quite hairy, particularly when they're deeply plumbed into shared services and infrastructure that they couldn't operate without. Those layers occasionally have closed-source licensed tech mixed in there.
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.
I'm countering your argument that it's "not that bad". If that wasn't your point with mentioning the three person team, what was?
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.
Ah, I see. Well, the post I was responding to reads to me like a denial of the existence of games like Among Us when it says it wouldn't affect three person dev teams making games on a shoestring budget, and gives off the weird implication that it would only affect big budget games.
That said, I don't mind a tangent, and I have built services for large multiplayer games and it really is not that bad.
I've also worked on MMOs and the architectures there can get quite hairy, particularly when they're deeply plumbed into shared services and infrastructure that they couldn't operate without. Those layers occasionally have closed-source licensed tech mixed in there.
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.
2 replies →