Some continual sound loops would benefit from using client-side MovingSound (smoother sounds & fewer packets being sent from server):

• Minigun firing (player, drone and turret) done
• Air leak
• Elevator moving done
• Pressure chamber interface door

For this to work, the client needs the appropriate state information (whether in TE, entity or item) to know to stop the effect loop.

Going to close this here. Interface door doesn't really need a MovingSound, and has already been addressed. Air leaks aren't really practical to do as MovingSound since they'd need a lot of server->client traffic to keep the pressure information updated.