Create Games and Experiences in the Metaverse

Game Maker 0.12

Guidelines for creators

Multiplayer

Multiplayer functionality is an exciting part of building an experience, but it does come with an added layer of complexity. As soon as more participants are involved, it introduces extra ‘layers’ to consider when deciding how players interact.

This is because MP Behaviours and Components can’t send messages to, or receive messages from, SP Behaviours and Components in multiplayer experiences.

✴️ To emulate how messages will communicate in a multiplayer experience inside edit mode, toggle the singleplayer-multiplayer button at the top right.

Synchronized

Synchronized [MP] supports synchronization that controls and changes the position or state of objects and the environment for everyone. They are triggerable by ALL players, and they will change for ALL player.

Some behaviours are only available as MP.

Client-only

Client Only [SP] work locally, meaning changes to the experience will only occur for an individual player, even in a multiplayer experience.

Quests created in the Objectives tab aren’t multiplayer and can only be triggered by ‘Client Only’ messages and completed by individual players.

Performance

[MP] behaviours/components used in multiplayer experiences consume bandwidth and affect general gameplay performance. There are four groups of BEH/COMP according to bandwidth consumption: high, medium, low and null (all SP)

Below you can find a list of all high and medium behaviours and components, along with a maximum amount for each considering those are the only behaviours in the experience. Make sure to combine them taking this into account.

✴️ The following lists are also available inside the Game Maker if you hover over a behaviour or component while choosing them.