Skip to main content
Version: Next

Multiplay using Messaging

What for?

When implementing multiplayer feature, it is necessary to synchronize player states (e.g., location and movement).

Netcode for GameObjects, on which the NGO wrapper is based, centralizes player state within a single server process. Such a design makes scale-out difficult.

This module uses Messaging to enable multi-group multiplayer on a single server, or to scale out to multiple servers to increase the number of players in multiplayer. This allows for easier scale-out, resulting in lower operating costs.


  • Multiplayer in groups.
  • You can send and receive messages within a group.
  • You can add synchronized object movements.
  • You can add processing triggered by client state.


classDiagram MultiplayClient ..> PlayerInput MultiplayClient ..> MultiplayJoiningConfig QueuingMessagingClient <-- MultiplayClient NetworkClient <-- MultiplayClient MessagingJoiningConfig <-- MultiplayJoiningConfig INetworkObjectsProvider <|.. MultiplayClient PlayerInput --> PlayerInputValues class MultiplayClient { +LocalClient NetworkClient +JoinedClients IReadOnlyDictionary +OnJoined IObservable +OnLeaving IObservable +OnUnexpectedLeft IObservable +OnJoiningApprovalRejected IObservable +OnClientJoined IObservable +OnClientLeaving IObservable +OnObjectSpawned IObservable +OnMessageReceived IObservable +MultiplayClient(messagingClient, networkObjectsProvider) +ListGroupsAsync() UniTask +JoinAsync(joiningConfig) void +LeaveAsync() void +SpawnObject(objectPrefab, position, rotation, parent, message) GameObject +SendMessage(message, to) void } class NetworkClient { +ClientId string +NetworkObjects IReadOnlyList +NetworkClient(clientId) } class INetworkObjectsProvider { <<interface>> } class QueuingMessagingClient { <<extreal>> } class PlayerInput { +Values PlayerInputValues +SetMove(newMoveDirection) void +ApplyValues(synchronizedValues) void } class PlayerInputValues { +Move Vector2 +SetMove(move) Vector2 +CheckWhetherToSendData() bool } class MultiplayJoiningConfig { +MessagingJoiningConfig MessagingJoiningConfig } class MessagingJoiningConfig { <<interface>> }





This module uses the following packages.


Please refer to Release for the correspondence between module version and each package version.


This module uses Messaging to realize multiplayer. Therefore, Messaging Settings is required.

public class ClientControlScope : LifetimeScope
private MultiplayClient multiplayClient;

protected override void Configure(IContainerBuilder builder)
// After initializing QueuingMessagingClient and NetworkObjectsProvider
multiplayClient = new MultiplayClient(queuingMessagingClient, networkObjectsProvider)


Multiplayer in groups

MultiplayClient provides the feature to play multiplayer in a group.

Joining/Leaving a group is used in the same way as in Messaging. See Exchanging messages in a group.

// Join a group
var messagingJoiningConfig = new MessagingJoiningConfig("groupName");
var multiplayJoiningConfig = new MultiplayJoiningConfig(messagingJoiningConfig);
await multiplayClient.JoinAsync(multiplayJoiningConfig);

// Leave the group

Once you join a group, spawn a player and join the multiplayer.


You can also spawn objects other than the player.


Send and receive messages within a group

You may want to send and receive messages within a group, such as synchronizing reactions. Sending and receiving messages is used in the same way as Messaging. See Exchanging messages in a group.

// Send message to entire group
await messagingClient.SendMessageAsync("message");

Add synchronized object movements

The position and rotation of objects spawned by the SpawnObject method are synchronized in the default implementation.

Depending on your requirements, you may want to synchronize other movements besides object position and rotation, such as animation. This module allows you to add additional object movements to be synchronized according to your requirements by adding an implementation.

This module synchronizes object movements by sending a player's input to other players. Which player input is used for synchronization is indicated by PlayerInput and PlayerInputValues.

If you want to synchronize movements other than position and rotation, create a class that inherits PlayerInput and PlayerInputValues.

For example, here is a case where the input Jump is to be synchronized.

public class HolidayPlayerInput : PlayerInput
public override PlayerInputValues Values => HolidayValues;
public HolidayPlayerInputValues HolidayValues { get; } = new HolidayPlayerInputValues();

public void SetJump(bool newJump)
=> HolidayValues.SetJump(newJump);

public override void ApplyValues(PlayerInputValues synchronizedValues)
var synchronizedHolidayValues = synchronizedValues as HolidayPlayerInputValues;

public class HolidayPlayerInputValues : PlayerInputValues
[SuppressMessage("Usage", "CC0047")] public bool Jump { get; set; }

public void SetJump(bool jump)
=> Jump = jump;

Player inputs are synchronized at regular intervals. If you want to control the conditions of synchronization, for example, if you want to synchronize every time the input changes, use the CheckWhetherToSendData method.

Here is an example of synchronizing when either Move or Jump changes.

public class HolidayPlayerInputValues : PlayerInputValues
private Vector2 preMove;
private bool isMoveChanged;

[SuppressMessage("Usage", "CC0047")] public bool Jump { get; set; }
private bool preJump;
private bool isJumpChanged;

public override void SetMove(Vector2 move)
preMove = Move;
isMoveChanged = preMove != Move;

public void SetJump(bool jump)
preJump = Jump;
Jump = jump;
isJumpChanged = preJump != Jump;

public override bool CheckWhetherToSendData()
var ret = isMoveChanged || isJumpChanged;
isMoveChanged = isJumpChanged = false;
return ret;

Add processing triggered by client state

You can use the same event notification as in Messaging. See Adding Processes Triggered by Client State in Messaging for details.

In addition to the above, MultiplayClient has the following event notifications

  • OnObjectSpawned
    • Timing: Immediately after spawning the object to be synchronized
    • Type: IObservable
    • Parameters: Participating client ID, spawned object, message sent