Yes, but then you would not use local scripting unless it was for the driver, but still I would avoid it if other players are riding. Because using a local script would be giving the driver ownership of the script. So the whole bus and controls would be running on that players headset. If that player has terrible internet connection, then everyone has a bad time. Leave it on default and let the server handle the work.
ah, i think this is one of those great examples for local/default
so if it is a bus, if one player is controlling it, leave it default?
but if it is a single race car, then local?
to me this is still confusing since somehow i had assumed anything involving movement is supposed to be local
The way I like to think about it is: if it's a single player interaction, local. If it's a shared interaction, server side.
for the tutorial world mobile, when you rotate the cylinder in Room B, would another player see you rotate it or just yourself?
Everyone will see it. There's an API that allows you to control who can see what (setVisibilityForPlayers), but you would have to script it to be so. Otherwise, all objects are visible to all players by default, local or not.
