If you’re selfhosting, the cloud is your someone else’s computer ;)

I didn’t mean to get caught up in exceptions or exaggerations. I’m no developer either, so I have zero background-knowledge about game-development or game-engines.

Though as I work in IT (again, no developer) and live within a zero-IT-knowledge friend circle, I tend to try and shine a little light on some things that, to the outside, might seem simple but maybe aren’t. I guess sometimes I’m trying to err on the side of caution a little too much.

I definitely think there are a few of those one-line, true/false settings that could just be toggled, especially things that are handled by the engine instead of the game-logic itself, though I cannot speak of experience here.

I’m talking about ones that are like one line of code being set to true instead of false etc

I don’t know how many, if any, settings matching the true/false + 1 line of code restraints even exist.

If you can change a setting, even if it’s a binary choice, someone had to think about, implement and test everything pertaining to these choices.

Depending on what kind of mechanic we’re talking about and how deeply integrated into the rest of the game this mechanic is, that could be a big task.

I did not run OPNSense, but I have a direct comparison for pfSense as VM on Proxmox VE vs pfSense on a ~400€ official pfSense physical appliance.

I do not feel any internet-speed or LAN-speed differences in the 2 setups, I did not measure it though. The change VM -> physical appliance was not planned.

Running a VM-firewall just got tiring fast, as I realized that Proxmox VE needs a lot more reboot-updates than pfsense does. And every time you reboot your pfSense-VM-Hypervisor, your internet’s gone for a short time. Yes, you’re not forced to reboot. I like to do it anyway, if it’s been advised by the people creating the software I use.

Though I gotta say, the pfSense webinterface is actually really snappy and fast when running on an x86 VM. Now that I have a Netgate 2100 physical pfSense appliance, the webinterface takes a looooong time to respond in comparison.

I guess the most important thing is to test it for yourself and to always keep an easy migration-path open, like exporting firewall-settings to a file so you can migrate easily, if the need arises.

[EDIT] - Like others, I also would advice heavily against using the the same hypervisor for your firewall and other VMs. Bare-Metal is the most “uncomplicated” in terms of extra workload just to have your firewall up and running, but if you want to virtualize your firewall, put that VM on its own hypervisor.