PlayerCommandService is using a "syncObject" now.
All access to 'playerStatus' will be synchronized against this syncObject.
It is assumed that a PlayerManager will do likewise manipulate the 'playerStatus' on its own thread based on the actual playerstate.
By using the syncObject it can be guaranteed that remote calls and internal state changes don't get into each others way.