Objectives
GM 0.11 update: Objectives system ported for multiplayer compatibility.
Last updated
Was this helpful?
GM 0.11 update: Objectives system ported for multiplayer compatibility.
Last updated
Was this helpful?
GAME MAKER 0.11 - OBJECTIVES MIGRATION (Optional)
Migration to the 0.11 Objectives System is optional. The legacy system will be deprecated later, but is still supported.
MIGRATING OLD QUESTS TO 0.11
Visit Objectives System Port in the 0.11 Upgrade Guide for guidance to update old Experience quests for compatibility with the new Objectives system.
CREATING NEW QUESTS IN 0.11
Visit in Text, Quests & Icons for new ways to build quests in multiplayer Experiences.
Quests are game events that prompt players to take action through descriptive UI and object icons.
A quest may be triggered and completed only ONCE.
Quest data is used in Seasons and Events to track player progression to earn rewards.
While players can scroll through quests in the UI, it is still more user friendly to limit how many quests can be triggered at a time (4-5 maximum recommended).
Visit Text, Quests & Icons in the Logic Guide to learn how to set up quests with dialogue and object icons.
GAME MAKER 0.11 - MORE COMMUNICATION OPTIONS
Objectives now communicate with Game Rules and MP behaviors and components.
Objectives will NOT communicate with [SP] behaviours and components in multiplayer.
GAME MAKER 0.11 - PLAYER SOURCE REQUIRED
⋅ Individuals (player variables) - No modifications needed (player source already required).
┋All players (global variables) - Make Rules spawn an object for all players to interact (e.g., Trigger Volume).
∴ Teams (team variables) - Make Rules teleport team members to interact with a hidden object.
Each quest has its own card and appears in a vertical list. Order can not be changed, but it does not affect when a quest will be triggered.
The Game Maker 0.11 Objectives System update brings a few changes, but nearly identical UI.
GAME MAKER 0.11 - PLAYER SOURCE & MESSAGES IN FOR MULTIPLAYER
Every message received by Objectives must include player source data to change the quest state for every applicable player.
This note applies to every item highlighted below.
- Waits for a specified Message to be unlocked
Auto Launch - Automatically launches the Quest if it is unlocked
- Waits for a specified Message to launch if unlocked
The four types of Quests available are Counter, Asset Death, Timer, and .
Once the condition for the Quest type is met:
Auto Completion - The Quest instantly completes
- A specified Message is still required to complete the Quest
The Wait for Input option was removed in Game Maker 0.11. This can be replaced with the Requires Message quest type.
Once the Quest is completed:
Send Message - A Message will be sent, which can trigger a new Quest or other logic
The Nothing option was removed in Game Maker 0.11 since it is redundant.
The use cases noted for each quest type are only a few ideas to get you started.
The player must collect or destroy a specified number of objects that have a specified tag.
NOTE
The Health Component includes a parameter Invincible, which must be set to False in order for it to be possible to destroy the object and make it count toward the Quest condition.
When you open an Experience built before Game Maker 0.11 and open the Objectives window, you will be prompted to migrate to the new Objectives system.
GAME MAKER 0.11 - RETROCOMPATIBILITY
The legacy Objectives system is still supported in 0.11, so you will not be required to migrate.
If you choose to migrate to the new Objectives system, a helper will appear after quest data is migrated. It will highlight any quests that require manual adjustments to meet requirements of the new multiplayer compatible Objectives system.
Some quest functions could not be adapted to the multiplayer structure and have been modified or removed, but changes are minimal.
Info boxes added to this page provide more detailed explanations of what has changed in the update.
The most important change when migrating is to ensure that for multiplayer games, messages sent to Objectives have a player source for every player who should experience a change in quest status (unlock, launch, completion, post-completion), and players who should not have no way to trigger the message. Player source data is automatically sent with a message upon player interaction (detection, object interaction, etc).
See 0.11 version notes for multiplayer quest use cases and tips.
Every message sent to Objectives must include player source data from direct interaction by every player who should experience quest triggers. Send via Asker, Trigger Volume, Button, etc.
Player source data is sent as long as a chain of logic starts with the correct player(s).
Trigger Objectives with Rules criteria (examples):
The Auto Unlock option was removed in Game Maker 0.11. Use the rule to send the Required Message to Objectives.
Dialogue Strings
Asker behaviours can be triggered in a sequence for conversations with NPCs and result in quest state changes
Object Icons for Quests
Indicator component can apply icons for quest givers, receivers, and objectives to make these objects easier to find in the game world
Singleplayer Experiences
Multiplayer Experiences
Singleplayer Experiences
Multiplayer Experiences
Select CollectedObjects from the dropdown, set the tag to count, and set the amount required. Place at least the specified amount of objects in the game world, each with a Collectible Component, and the Tag noted in the Quest applied.
Use Cases:
Collect the same item as a side Quest, such as voxelite
Collect different items for a combined purpose, such as recipe ingredients, machine parts, etc.
Select Deaths from dropdown, set the tag to count, and set the amount required. Place at least the specified amount of objects in the game world, each with a Health Component and the Tag noted in the Quest applied.
Use Cases:
Destroy the same type of enemies
Destroy a variety of enemies in a room
Destroy objects to propel a narrative (e.g., rocks to escape a cave)
Destroy relay objects to kill a more powerful enemy (boss fight)
Click on the Asset to Watch field to open a window and select a specific object you have placed in the Experience.
Use Cases:
Boss fight, single enemy
Boss fight, multiple "holograms," one target
Destroy a specific object as part of a narrative
Set the Seconds to wait as the timer and select Survive from the Goal dropdown.
The player must not die during that time period.
Use Cases:
Boss fight where a door will open if the player can survive, or else they have to take a different route
Fight an enemy horde
Set the Seconds to wait as the timer and select Defend from the Goal dropdown.
The player must not allow a target object to be destroyed during that time period.
Use Cases:
Protect an important NPC in the narrative
Protect an important item in a narrative from enemy attacks during a battle scene (e.g., castle gate)
Set the Seconds to wait as the timer and select Message Needed from the Goal dropdown.
Use Cases:
Timed parkour race
Timed fetch Quest
Timed collect Quest
Timed quiz given by an NPC with a reward if completed successfully
Set a Message to receive. Place an object in the game world for players to interact with (pressing E to send the Interact message, detection, collection, etc). The player must trigger the message to be sent to Objectives to complete the quest.
Use Cases:
Detect a pickable item or the player's avatar at a location
Quest driven by an NPC's Asker Behaviour responses
Points of interest Quest
SP and MP behaviours and components Game Rules
SP behaviours and components MP behaviours and components Game Rules
SP and MP behaviours and components Game Rules
SP behaviours and components MP behaviours and components Game Rules
Add Quest
Delete Quest
Collapsed Quest Card
Expanded Quest Card
Quest Name Maximum Characters: 20
Quest Description Maximum Characters: 160
The player's actions must trigger a Message during the specified time period. (0.11 Multiplayer) The message must be sent through direct player interaction to include player source data.
