For various reasons, some legacy games should not have internet access. (Dead online servers, legacy systems, modded games phoning home, etc).
This is typically done easily on the client by blocking outbound egress from an OS level firewall, or sandboxing the application. The issue is for other users this requirement is not known to them, and they will attempt to launch the game without doing this prerequisite. In many cases, this will "brick" their game, requiring a full uninstall and reinstall of the game.
Proposed Solution:
Implement a service-side per-game configuration value which will state to the clients that this application should not have internet access.
Initially considering a simple boolean, however I could see potential in a "flagging"/tagging system which could extend this sort of functionality, similar to emulators. (Another example could be a companion app should run in parallel to this app, or it should have specific OS settings).
Clients then would receive this signal and assign the appropriate OS level controls/gates to prevent internet access.
-
In Linux, this could be wrapping the command in unshare --user or firejail --net=none -- (both of which are incompatible with Drop's templating).
-
In Windows, this could be adding a Firewall rule for egress traffic for the executable.
This addition would allow server admins to configure games and cause less confusion for their users.
For various reasons, some legacy games should not have internet access. (Dead online servers, legacy systems, modded games phoning home, etc).
This is typically done easily on the client by blocking outbound egress from an OS level firewall, or sandboxing the application. The issue is for other users this requirement is not known to them, and they will attempt to launch the game without doing this prerequisite. In many cases, this will "brick" their game, requiring a full uninstall and reinstall of the game.
Proposed Solution:
Implement a service-side per-game configuration value which will state to the clients that this application should not have internet access.
Initially considering a simple boolean, however I could see potential in a "flagging"/tagging system which could extend this sort of functionality, similar to emulators. (Another example could be a companion app should run in parallel to this app, or it should have specific OS settings).
Clients then would receive this signal and assign the appropriate OS level controls/gates to prevent internet access.
In Linux, this could be wrapping the command in
unshare --userorfirejail --net=none --(both of which are incompatible with Drop's templating).In Windows, this could be adding a Firewall rule for egress traffic for the executable.
This addition would allow server admins to configure games and cause less confusion for their users.