>>714199623
>only literal children care about this
Cool, so let’s just nuke competitive integrity because you personally don’t care. Great mindset. Who gives a shit if your RPG’s PvP turns into a festival of packet tampering and infinite HP? It’s not like that would ruin the experience or anything. God forbid people want a game that isn’t a playground for script kiddies and sociopaths.
>Documentation would be simple
That’s not how reality works, my sweet summer dumbfuck. Even basic server kits need setup instructions, port info, dependency lists, version compatibility notes, etc. And when some dildo runs it wrong and screams “devs lazy!!1!”, guess who gets blamed?
>Leave it runnable only on Linux or Windows”
Fantastic idea. Also, ever tried distributing binaries and managing environment quirks across even just one OS version? Of course you haven’t.
>No further work needs to be done
Right, because totally unmaintained software with known exploits just works fine forever. Definitely no issues there. Definitely no legal risk. Definitely no bad press when someone spins up a server, injects malware, and it turns into your game’s problem.
>Nobody is asking for open-sourcing unless it’s a last resort
And yet, you’re still demanding handover of working server logic, clean enough for randos to run. So either it’s bundled into the game (and can be cracked), or it’s shipped separately and still vulnerable to reverse engineering.
>>714199696
>It used to be the standard 20 years ago
Yeah. And you also used to install drivers off floppy disks and get viruses from LimeWire. Standards evolve. Tools change. Expectations change. You wanna live in 2004? Boot up Quake 3 and cry into your Pepsi Blue you retarded dickhead.
You want what SKG is proposing like it’s a human right, but what you’re really asking is for broke devs to take extra hits on labor, risk, and support post-launch just to satisfy your fantasy of being a game archivist.
