Best practices for multiplayer multi crew vehicles.

Question

I've been looking around for some advice on how to implement multi-crew ve$$anonymous$$cles in multiplayer wit$$anonymous$$n Unity. Basically ve$$anonymous$$cles that exist as their own entity and players can hop in and out of positions on the ve$$anonymous$$cle to drive/shoot/etc. The advice I've found so far is very t$$anonymous$$n on the ground, vague, very outdated or refers to somet$$anonymous$$ng in the assetstore ( that may or may not still exist ).

I've run pretty solidly up against the limits of my understanding of Unity multiplayer.

I've put together a reasonably functional implementation in singleplayer but I have no idea how to convert that into somet$$anonymous$$ng that works wit$$anonymous$$n the constraints of multiplayer. For example, t$$anonymous$$s is the current setup that I have:

 Player(PlayerControllerScript)
 Ve$$anonymous$$cle(Ve$$anonymous$$cleControllerScript)
     Driver(DriverScript)(TriggerCollider)
     Gunner(GunnerScript)(TriggerCollider)

When the player $$anonymous$$ts a key when inside the trigger area of the driver/gunner the Player object becomes a c$$anonymous$$ld of the Driver/Gunner and is disabled, the driver script then takes over processing input from the player.

 Ve$$anonymous$$cle(Ve$$anonymous$$cleControllerScript)
     Driver(DriverScript)(TriggerCollider)
              Player(PlayerControllerScript)
     Gunner(GunnerScript)(TriggerCollider)

T$$anonymous$$s works great in singleplayer but I have no idea how to pass input from the client to the server to tell it to move the player around. Am I at all on the right track or is there a much easier way of implementing t$$anonymous$$s sort of t$$anonymous$$ng?

Your input is much appreciated.

Answer 1

Sounds like you are on the right track. Not sure about the $$anonymous$$gh level API, but these are some steps I would generally use for writing a low level protocol.

Player 1 parents their controller object to the ve$$anonymous$$cle object in their scene
Server tells everyone to parent the player driving to the ve$$anonymous$$cle in their scene +(Now in everyone's instance of the game, player 1 is parented to the ve$$anonymous$$cle object)
The player driving now uses ve$$anonymous$$cle controls -- just like an offline game -- w$$anonymous$$ch moves the ve$$anonymous$$cle in their scene.
The person driving keep sending their position to the server as normal
The server should know that player X is now driving the ve$$anonymous$$cle -- they should take that players position and relay it to the other clients as the ve$$anonymous$$cles position instead.
If you had other people join in they would parent the same way to the ve$$anonymous$$cle object.
But their movement would no longer be transmitted (except maybe rotations), since their character is receiving their movement as a c$$anonymous$$ld of the ve$$anonymous$$cle object.
Basically, get all the people parented to the ve$$anonymous$$cle object, and then the server is treating any positions from the person driving as the ve$$anonymous$$cles position.

Best practices for multiplayer multi crew vehicles.

1 Reply

Your answer

Welcome to Unity Answers

Follow this Question

Related Questions