RoR is likely turning off some of the functionality but the EOS SDK is still used in the binary. I’m assuming here, I don’t know the specific implementation, but if there’s a check box and you don’t need to restart the whole game after checking it, there’s no way it’s somehow removing EOS from the program. It likely just disables various functionality, but I bet it’s still making a couple calls to verify the existence of the EOS network, just like Satisfactory does.
Games (and programs in general) have to be built with support for any environments they want to run on. If you want to release your game on multiple storefronts and take advantage of their built in social functions, you need to build in support for those functions, even if they won’t be used in some cases.
Not if you delete the dll file, unless it’s both inthe dll and the exe…?
I think it requires a restart but it’s off by default, it asks when you first run it (first install? Each install?) And you can disable it but after deleting the .dll file, the game runs perfectly fine
I guess? But some people aren’t really happy with these changes, especially old games where it gets added or the fact is required in a single-player only game
DLLs are libraries that get called by the binary. So deleting the DLL stops any calls from executing, but the code still contains calls to the SDK.
Go ahead and boycott any game that uses EOS, but it’s a weird hill to die on.
But if it’s deleting it stops any call then it’s like not having it in the first place
Nah, don’t care. Devs are learning where is better to release games (aka not exclusively) soo🤷♂️ it’s a matter of time and we’ll either see it die or adapt and make something worth using and not trying to be a monopoly