Text, Quests & Icons
Last updated
Was this helpful?
Creators
Last updated
Was this helpful?
Was this helpful?
See Dialogue in our Narrative Design resources for information about creating engaging dialogue that fits within the technical limits, and communicating plans with a team.
See Playability for tips to make your Experience Page and game UI more polished.
Speaker component (object)
Detect players, "bark" to get attention (can send player source data)
Simulate a conversation between NPCs
Asker behavior (object)
Player dialogue with NPCs (can send player source data)
Quizzes
Indicator (object text), toggled on and off with Actor Property Switcher behaviour
Crowd Event (object)
Title (with colour selection)
Description per Element (how to earn points)
Modifying the text format can add character, make it more readable, or emphasise hints or instructions for players. Simply add opening and closing tags around the text to be formatted.
Formatting does not work in HUD slots, but works in most other text fields.
Formatting tags count against the character limits different text fields have.
Game Client & Game Maker UI
Software UI is only available in English (e.g., menus) at this time.
There are 37 available sprites that may be used in many text fields by typing the tag <sprite=1> with a sprite number from 1 to 37. There is no closing tag for sprites. Learn more (video)
Visit the 0.11 Upgrade Guide to migrate to the new Objectives system and adapt quest design for multiplayer compatibility.
It is possible to build a game without quests, but quest UI and icons make the same gameplay feel much more responsive and polished.
Quests are one-time-use player objectives that can be used for:
Tutorials for your unique Experience mechanics
Meeting important characters or Worldbuilding
Points of interest or large scale item collection to encourage exploration
Linear game flow, optional side quests, or branching logic based on player actions
(Partners) Track player progression in Seasons and Events to earn rewards
and more
See Quest Types for use cases per quest type.
In multiplayer Experiences, quests are now managed on the server. Messages sent to Objectives must include player source data, so [SP] logic will not work.
In singleplayer Experiences, [SP] and [MP] logic will trigger quests.
The new Objectives system opens up possibilities for quests to be triggered depending on which player(s) should experience a quest in multiplayer games.
In this first version, feature continuity for solo questing is the main design focus. However, many creators may explore building logic for multiple players to experience quests at nearly the same time.
It isn't as simple as using the Game Rules system, where dependencies for variables are built in (player, team, and global), so we've provided some options to try out. Some are simple, and some a bit more advanced.
USING THIS RESOURCE In the generalized suggestions below, Step 1 should trigger Step 2, and so on, to send player source data and trigger Objectives for intended players. Please test thoroughly and share what you learn in the Forum!
[MP] trigger (options):
Collectable component (Global = TRUE)
Trigger Volume (destroy this object after one use)
Button (destroy this object after one use or spawn a 
Speaker to inform players that they weren't first)
Asker (Only once = TRUE or apply 
Toggle to turn off after one use)
[MP] 
Message Broadcaster (Broadcast only once = TRUE if trigger in step 1 can't be removed or prevented)
Objectives
Use Cases
Quests with rewards or incentives
Special roles, side-quests, or branching narrative options
[MP] trigger (options):
Collectable (Global = FALSE)
Trigger Volume
Button
Asker
Objectives
Use Cases (gameplay without rules criteria)
Social hub quests
Competitive solo narrative questing
Side quests any player can complete
The examples below do not use built in features. Since there is a break in logic flow and quests do not trigger at the exact moment, test your design thoroughly to ensure it works consistently. More developments are on the way to make multiplayer quest design easier.
Trigger options:
All players enter a location:
[MP] Trigger Volume (Detection = EveryAvatarInRange)
Rules (global variable as a criteria to send a message)
Asset Spawner spawns [MP] Trigger Volume (Detection = EveryAvatarInRange)
Objectives
Use Cases
Cooperative Escape Room, etc.
Players vs Enemy quests (PVE)
If you're new to creating multiplayer Experiences, try adding a collaborative goal with Crowd Event behaviour. It's easier to set up than quests and has its own UI!
The Objectives system sets up the structure of quests, which have a beginning, middle, and end. Use the Indicator component to set quest icons to appear on objects related to your quest.
PLAYER ICON - EXCLAMATION MARK
Directs players to start a quest
Appears when a quest is unlocked
Disappears when a quest is launched
BUILDER SETUP
Objectives - set the quest conditions
Indicator - apply this component to an object
Click Add+ next to Giver and select the quest name from the dropdown list to make the icon appear above the object during play
One NPC may need to say different dialogue depending on the state of a quest:
Beginning State - An NPC informs players about the quest so they can accept it
Middle State - An NPC reminds players they haven't finished the quest yet and may provide a hint
End State - Congratulate players if the quest is complete (may suggest where to find a new quest)
A dialogue string is a series of logic events used to:
display a conversation between an NPC and a player (with answer options)
display quiz questions (with answer options)
display a "read only" conversation between NPCs (using Speaker component)
An object may only have one Asker behaviour and one Speaker component. This means that multiple objects are needed to create a dialogue string. That usually includes objects with visibility turned off.
Asker behavior may be triggered in a linear sequence or may trigger different paths of gameplay.
