Can someone explain what particular scripting events require a client to have a copy of a mission script, instead of just the server having it?
Asked another way: Is there something in custom scripts we avoid using to reduce the chance of confusing a client which doesn't have access to the entire mission script? (iOS, Android, remote PC joining over the Internet, etc).
I suspect that anything which brings up a VIS (3d external) view is going to need any custom ship bits; not sure on sounds though.
Login below to reply: