❗0.11 Upgrade Guide

Please review these topics to update old Experiences and use 0.11 features best.

Game Maker 0.11 updates collisions and introduces a multiplayer compatible Objectives System.

🌐 Languages (more options coming soon): | 한국어 | 日本語 | Türkçe | Tiếng Việt | Indonesia & Melayu |

Checklist

• Adjust block/asset spacing for the new Default palette

• Test all custom avatar animations for the new Default palette

• Align climbable assets with surface/platform edges

• Update complex climbable assets/use for simpler collisions

• Adapt Speaker component setup for removed [SP] collisions

• Migrate to 0.11 Objectives, and trigger quests in multiplayer with interactive [MP] logic

Visit Game Maker 0.11 version notes for all updates in this version.

Collision Changes

Movement Palettes

This setting will affect game feel, including camera, controls, and animations.

New Experiences use the Default palette with Coyote Time & Edge Recovery for better platforming, but different object/block positions are needed.

Pre 0.11 Experiences may optionally update from the Legacy palette.

Default palette features

Key Impacts

• Preventing player access to areas

• Platforming with carefully designed jump heights/distances and/or ramp of difficulty

• Some asset design

• Custom avatar use

CUSTOM AVATARS & MOVEMENT PALETTES

Older assets may not include Edge Recovery animations when using the new 0.11 default Movement Palette. Always playtest custom avatars carefully for every animation needed.

Access barriers must be 3 blocks high instead of 2 with the new Default palette.

Game Design (Blocks)

Player Reach Estimates

Legacy (Pre 0.11)

Jump Distance (Walking)

5 blocks

Jump Distance (Running)

7 blocks

Jump Height

1.5 blocks

Default (0.11+)

Jump Distance (Walking)

7 blocks

Jump Distance (Running)

10 blocks

Jump Height

2.5 blocks

Asset Design (Voxels)

Player Reach Estimates

Legacy (Pre 0.11)

Jump Distance (Walking)

160 voxels

Jump Distance (Running)

224 voxels

Jump Height

48 voxels

Default (0.11+)

Jump Distance (Walking)

224 voxels

Jump Distance (Running)

320 voxels

Jump Height

80 voxels

---

Climbable Component

Align object edges and apply Climbable to objects with simpler colliders for best results.

Alignment

Line up edges for smoother transitions from climbable objects to surfaces.

❌ Not aligned

✅ Aligned

Complex Collisions

Remove collisions on objects with many faces. Then apply the Climbable component to an invisible asset in the same location with simple collisions for smooth climbing.

❌ Too many climbing surfaces to calculate

✅ Substituted climbable asset for easy calculations

---

Speaker Component

Applying [SP] Speaker to an object removes its collisions. Logic may need modifications.

Due to the Look at Target option, which rotates an actor, [SP] Speaker component can cause inconsistent physics between server and client in multiplayer Experiences. There are two update options:

🔷 If [MP] is Acceptable

Change [SP] Speaker component to [MP] and adjustment as needed for the same logical outcomes.

⚠️ In multiplayer, this changes the object's communication from client to synchronised (server). It will no longer communicate with [SP] objects. Modify other logic if needed.

⚠️ If the object also has other [SP] logic applied, [MP] can not be applied. If modifying this is too complicated, the other update option may be a better solution.

🔷 If [SP] is Needed

Keep the [SP] Speaker component on the object. Then, create a duplicate with collisions, remove all of its logic, and set it to invisible.

---

Objectives System Port

New: Cooperative and Competitive Quests!

0.11 OBJECTIVES SYSTEM

• Migrating old Experiences is optional.

• Minor UI changes remove redundancies and improve functionality.

• 👤 SINGLEPLAYER - [SP] behaviours and components will trigger Objectives.
• 👥 MULTIPLAYER - Triggers from interactive [MP] behaviours and components must be used to send player source data:

  • [MP] object --> Objectives
  • [MP] object --> other logic (including Rules) --> Objectives
  • Rules --> Spawned [MP] object / teleportation to [MP] object --> Objectives

Upgrade Existing Quests

Follow the step-by-step instructions below for each quest state depending on pre 0.11 quest settings (tab names):

1.

Unlock Quest

Auto Unlock

Auto Unlock option was removed. For the same functionality:

1. Choose Requires Message and select or create a message

2. Open Game Rules and add a #onplayerjoin rule
3. Set the rule's outgoing message to the required message to trigger Objectives

Requires Message

Singleplayer

No change needed.

Multiplayer

Player source data required.

All players who should be included in the quest must directly interact with a [MP] behaviour or component that triggers Objectives or triggers a chain of logic that includes Objectives.

2.

Launch Quest

Auto Launch

No change required.

Requires Message

Singleplayer

No change needed.

Multiplayer

Player source data required.

All players who should be included in the quest must directly interact with a [MP] behaviour or component that triggers Objectives or triggers a chain of logic that includes Objectives.

3.

Quest Type

Counter

Collected Objects

Singleplayer

No change needed.

Multiplayer

Modify each collectable object's Global setting to suit intended gameplay.

Gameplay

Each player can collect a tagged object

Setup

Per collectable object, Global = False

Total Collectable Items

Player Count x Object Count

Gameplay

One player can collect a tagged object

Setup

Per collectable object, Global = True

Total Collectable Items

Object Count

Gameplay

Combination

Setup

Per collectable object, set Global to False / True as needed

Total Collectable Items

(player count x object count) + object count

Object Deaths

No changes needed.

Asset Death

No change needed.

Timer

Survive or Defend

No change needed.

Message Needed

Singleplayer

No change needed.

Multiplayer

Player source data required.

All players who should be included in the quest must directly interact with a [MP] behaviour or component that triggers Objectives or triggers a chain of logic that includes Objectives.

Wait for Message

Singleplayer

No change needed.

Multiplayer

Player source data required.

All players who should be included in the quest must directly interact with a [MP] behaviour or component that triggers Objectives or triggers a chain of logic that includes Objectives.

4.

Quest Completion

Auto Completion

No change needed.

Requires Message

Singleplayer

No change needed.

Multiplayer

Player source data required.

All players who should be included in the quest must directly interact with a [MP] behaviour or component that triggers Objectives or triggers a chain of logic that includes Objectives.

Wait for Input

Wait for Input option was removed. For the same functionality, change to the Requires Message quest type.

5.

Action After Completion

Send Message

Singleplayer & Multiplayer

No change needed since this is an outgoing message.

This message includes player source data!

It can trigger changes in a team variable or a player variable in Game Rules if a rule's Required Message is set as this message.

End Game

End Game option was removed. For the same functionality:

Singleplayer

Use the Send Message option to trigger an object's Victory or Defeat component.

Multiplayer

Use the Send Message option to trigger an object's Victory or Defeat component.

Player source data required.

All players who should be included in the quest and the end of game must directly interact with a [MP] behaviour or component that triggers Objectives or triggers a chain of logic that includes Objectives.

Nothing

Nothing option was removed due to redundancy. No change needed.

Create New Quests

Game Maker 0.11 Objectives communicate on the server (synchronised) level now, which opens up many new creative possibilities.

Though this first version is intended to help creators migrate to the same functionality (solo questing in social hubs), we understand our community will want to explore a variety of scenarios that are now possible. Future updates will make multiplayer scenarios easier to build.

Visit Text, Quests & Icons for potential new scenarios for Multiplayer Compatible Quests (0.11) with different dependencies, such as which players should experience a quest and whether Game Rules logic should be part of the criteria to trigger it.

Please keep in mind that these are generalized logic flows which need to be tested thoroughly. Please share your ideas and what you learn in the Creators Forum.