I’m not a smart nor good developer so maybe I’m looking at this wrong, but if you’re a game Dev and you’re using Unreal Engine or Unity, aren’t you already bound to whatever license they have?
I believe if you’re following say Unreal’s structure, you’re using their server/client netcode, and while you can release whatever you’ve made you can’t use or share any of Epic’s code. That would still require users to agree to Epic’s EULA to get the full engine to compile your server setup.
Add in server handling for VoIP, audio middleware like FMOD, proprietary stuff like Xbox/PS crossplay, Steam’s SDK, etc and I feel like that’s a tangled web.
I’m also very tired and am probably not fully registering here.
RedFrank24@lemmy.world 22 hours ago
I’ve never worked with Unreal’s server setup, but I imagine it doesn’t absolutely require to use their code, right? You can still make an Unreal game on the client and use something else for your server, meaning there must be some sort of common interface between them.
The point is yes, there is going to be code you can’t legally release, libraries you can’t use, but you can release what code you can, and then leave the interfaces for code you can’t, leaving hobbyist devs to pick up the slack. You can even make servers from scratch that way, as with stuff like AzerothCore, where all of the code was figured out from scratch based on packets from client to server and studying hex code for hours.
Even if you strip out the code you can’t legally release, that’s a hell of a boost to development that you wouldn’t otherwise get.
Justdaveisfine@midwest.social 16 hours ago
Taking a cursory glance through the solutions that already exist for this (which are largely standalone MMO style servers):
You lose out on many network troubleshooting tools unreal has built-in, as well as some of Unreal’s play-in-editor testing tools. Its also common to add roughly 1.25-2x netcode development time as you’re going to be coding things in on the Unreal client side as well as the server side.
I can see why this is feasible but rare to see in the wild. I think anything you pitch to an exec with a note that it may add 6 months to a year of extra development time (and QA time) is going to cause people to start swinging.
RedFrank24@lemmy.world 14 hours ago
Ideally though, if this became law, you would be accounting for the fact you might have to swap out the server implementation into your initial development of the game.
Also, some of those tools you might not need for production client code. Yes it’s gonna be a pain in the arse to develop server code without those tools, but not necessarily impossible. You could release server code with those tools stripped out, or able to be configured to work with those tools if someone else has the license for them.
In essence, you could modify the client to include configuration points that can point to specific servers, and then release documentation to say “Hey, this is what tool was originally used, these are the kinds of packets the client is sending (and whether they are expecting a response), and these are the kinds of packets the server is sending to the clients”. You then leave the actual server development to whoever wants to build one. That is, effectively, how private MMO servers are made, but regardless of the type of game, you’re still sending UDP packets to a server and receiving UDP packets from the server. You just need to know the purpose of those packets.