Build Roblox Quests & NPC Dialogues — No Code Needed
Write dialogues, create interactions, send notifications, guide players and add conditional logic.
Shows dialogue bubbles. Pauses the action chain until the player finishes reading.
NPC conversations, story sequences, tutorials, quest briefings, lore reveals.
Pauses the chain. The player must press the action button to continue. Places a hold-E prompt on the entity.
Talking to NPCs, harvesting resources, opening chests, activating mechanisms, picking up items.
Shows a message on the player's screen. Choose between success, error, warning and info styles.
Quest updates, purchase confirmations, error feedback, system messages, achievement alerts.
Places a GPS waypoint to guide the player. The chain pauses until the player arrives.
Guided tutorials, quest navigation, directing players to objectives, discovery mechanics.
Compares two values and goes through Yes if the comparison holds, No otherwise.
Pick a path based on a math comparison: vitality > 50, gold == 0, level >= 10.
Checks something (e.g. does the player have 100 coins?) and picks a path based on the answer. Combine several conditions with AND / OR.
Shop purchases (check gold), locked doors (check key + level), level-gated content, branching dialogues.
Pauses the chain until a condition becomes true (e.g. the player reaches 10 HP). The engine checks every 2 seconds and resumes automatically.
Wait for the player to collect enough items, reach a stat threshold, earn currency — or any combination.
Assigns a daily quest to the player.
Login bonuses, daily objectives, recurring challenges.
Assigns a journal quest to the player.
Storyline milestones, long-term objectives tracked in the journal.
The NPC gives a quest to the player, picked at random from the list. Takes a different path depending on what happens.
Guild NPCs handing out random missions, daily quest givers, storyline NPCs with several possible quests.
Looks at whether the player already has the NPC's quest, and picks a different path depending on the state. Does not change anything.
Use before Give a quest to avoid giving the same quest twice. Use after to branch the dialogue on whether the quest is done, in progress, or failed.
The NPC gives the reward to the player. Only works if the player has finished the quest.
The player comes back to the NPC after finishing the quest, to collect the reward.
The player has to hand over the right items to the NPC, in the right order. If they get it wrong, the quest fails.
Delivery quests (bring 2 mushrooms + 1 flower + 2 turtles) where getting the order wrong means failure.
The NPC forgets the quest they had given. Used so the player can try again after failing.
After the 'Failed' branch of Check the quest: accept the failure and let the NPC give a new quest.
Shows a prompt to the player with a list of response buttons. Each response opens its own branch in the graph.
NPC dialogue forks, quest acceptance prompts, shop menus, dilemmas, player-driven narrative.
Displays a large styled title on the player's screen, with optional sound. Reuses the engine's title display system.
Boss defeat banner, achievement reveal, chapter title card, level-up flourish.
Routes the incoming value to one of its case outputs. Wire a Get → Switch.value, list the case values to match. Each case becomes an output port that fires only when the incoming value matches it. Wire a port onto a downstream gate to apply that branch.
Drive type-specific behaviour : on Warning apply a font + a colour, on Error change just the border, etc.
Reads a value from the player or the project (a stat, an inventory list, the recipe catalogue, etc.).
When you want to display vitality, the inventory list, the active quests, etc.
Performs a maths operation between two values: add, subtract, multiply, divide…
When you want vitality / 10 to get the number of hearts to display.
Builds a text from several parts: fixed pieces and live values mixed.
When you want 'Vitality: 80 / 100' with the live numbers inside.