Not to mention, vehicles in HF would meet one critical issue: a design flaw that High Fidelity has is that physical operations are managed by the client. They ‘can’ be managed by the server to some degree, as done with an entity server script test, but the moment a client walks in, it claims ownership away and that caused absolute chaos with some projects I tried.
I know that Fluffy has made some projects and that they 100% do not use Hifi’s built in physics system for this very reason. After doing some personal testing, sadly the only way is to rewrite the wheel. What we need is the option to OWN physical operations, as in deny others from having them based on some rules.
As for combat and all… I can tell you that there’s a reason RPO is just a book and movie: good story telling, bad in actual use. I can see combat domains being a thing, but as Argent mentioned, it’d be up to the domain operator’s choice to use such systems. In a similar way, a vehicle API could also be operated by a domain operator, allowing the server to managed ‘physics’ even in the system’s current state.