Unfortunately the Phys step runs at a fixed rate and there's nothing you can do to influence it, call it for specific objects etc. So the only way would be to replicate required phys at the accessible Lua level which is messy and probably wouldn't perform at scale
Yeah, it's really limiting. If Heartlight does well I'll invest some time in more lua-based tests, but if I could call the phys and network steps I could do so much more interesting stuff
