RedFrank24

RedFrank24, 4 godziny temu

I think you’re allowed to be selfish when it’s your game. I paid £80 for that game, I should have the right to play it for as long as I have the hardware to run it, even if I have to do some fiddling and modding to get it to work.

RedFrank24, 2 dni temu

Every time I see the argument that “Oooh no you can’t release server code, there’s proprietary code there!”, I question my software development skills.

You mean to tell me when you have licensed code, you don’t wrap it with your own interfaces? I was always under the impression that it was best practice to never rely on one single concrete implementation of your interface, hence the Dependency Inversion Principle.

If you have a proprietary library you use for determining the positioning of players on a map, you wouldn’t be directly instantiating BinglyBooCharacterPositionWhatsit, you’d be using ICharacterPositioner and then using BinglyBooCharacterPositionWhatsit as the implementation of that interface, surely?

RedFrank24, wczoraj

I mean if you are required to release a server dev kit, or at least make best efforts to release one, you can release what code you have and go “Here are the interfaces, but I can’t legally release this code because I don’t own it, so someone else is going to have to create an alternative”.

It’s about making it easier for other devs to make up for the gaps, rather than going “Nope! Proprietary code, can’t do anything!”

RedFrank24, wczoraj

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. Technically AzerothCore was just building on top of MaNGOS but that was created using packets.

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.

RedFrank24, wczoraj

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.

RedFrank24, 2 miesiące temu

I’m still waiting for a reliable way to pirate games with micro transactions and lootboxes.

Like, I know Assassin’s Creed Odyssey has daily quests and a rotating cash shop, and that must be talking to some sort of server that isn’t guaranteed to be there. Surely there’s a way to mock that server?