AI Quest Giver NPCs: Free Conversation, Story Beats Intact

Talking to a quest giver usually means picking from three options, one of which is "Tell me more", until the journal updates. Neocortex lets the player talk to an AI quest giver in their own words, bargain, lie, wander off topic, while a Conversation Flow quietly keeps the quest moving through the beats your story needs.

What it looks like

Hollow Reach is a mining moon in an original sci-fi western. Marshal Odessa Crane is the only law for three hundred kilometres of dust, and she needs a stolen ore manifest back from a claim-jumping gang called the Dust Rats. She is tired, wry, and has met a lot of offworlders who promised more than they delivered.

The player has never been here before. They try their luck:

Player: I'm a licensed bounty hunter. Guild rate is double. Odessa: Licensed. Then you'll have a guild tag on that collar. No? Thought not. Standard rate, half up front, because I like your nerve. Player: Fine. Where do I find them? Odessa: Shaft Nine, past the old pump house. Bring me the manifest, not their heads.

Behind the scenes, the conversation is following a flow with four beats. The Start node has Odessa size up the stranger. A Checkpoint marked job_explained fires once she has described the manifest and the gang. Another, terms_agreed, fires when pay is settled. The End node returns quest_accepted, and the game adds the quest to the journal. In the same reply, Odessa returns a GIVE_ADVANCE action aimed at the player and a MARK_MAP action aimed at Shaft Nine.

The player could just as easily have asked about her scar, complained about the weather, or refused outright. She would have answered every one of those in character, then drifted back to the job, because that is where the flow points.

How Neocortex makes it work

• Conversation Flows. You draw the quest conversation as Start, Checkpoint and End nodes in the visual editor. The character works toward each beat while the player talks however they like. Flows are on every plan, including Free.
• flowState keywords. Every reply carries a flowState value. When it matches a keyword you chose, like terms_agreed or quest_accepted, your quest system knows exactly where the conversation stands.
• Several endings. A flow can have more than one End node, so "accepted", "refused" and "talked into a better deal" can each send your game down a different branch.
• Character design. Odessa's personality, backstory and voice decide how she reacts to a bluff. Make her sharp and she catches it; make a different quest giver gullible and the same lie works.
• Knowledge base. Upload the quest's background as a PDF or TXT file: the gang, the mine, the manifest. Free includes 1 upload, Starter 5, Pro 20 and Team 100.
• Actions. GIVE_ADVANCE, MARK_MAP or GIVE_ITEM come back with a target ID, and your code hands over the credits or places the marker.
• Events. Feed in what happened in the world, and a quest giver can raise it: a new problem, a rumour, a side job.
• Session memory. Keep the sessionId and send it when the player comes back to turn in the quest. Resume the player's session and the first thing Odessa wants to know is whether they found the manifest.

Ideas to build

The quest giver you can talk down. A grieving miller asks the player to kill the man who burned his barn. A patient player can persuade him to settle for the truth instead. The flow has two End nodes, revenge_quest and truth_quest, and your quest system offers whichever one the conversation reached.

The clerk who believes a good lie. A guild clerk only hands senior contracts to senior members. Players who bluff their rank get the better job. Later, send an event like "the clerk found out the player's real rank", and the next visit opens very differently.

Side quests from what just happened. A dockside tavern keeper turns recent events into work. When your game logs "a cargo barge sank at the north pier" or "wolves took two sheep on the hill road", your quest system picks a side quest and the tavern keeper pitches it in their own words, with a flow for accepting or turning it down.

A mentor with a lesson plan. In a martial arts game, the old teacher's flow is a lesson: one Checkpoint per technique, an End node when the student is ready. The player can ask about the teacher's past or argue about philosophy, and the lesson still moves forward.

Building it

AI quest givers run through the Unity SDK, the Unreal Engine plugin with Blueprints, the Godot addon (beta) or the Web API from any engine. Your quest system stays where it is; Neocortex tells it when each beat is reached.

1. Write the beats first. Before any dialogue, list what must happen in the conversation: the hook, the details, the terms, the decision.
2. Build the flow in the visual editor with a Start node, a Checkpoint per beat and one End node per outcome. Name the keywords after the events your quest system already understands.
3. Design the quest giver: personality, backstory, what they know about the quest, how easily they are fooled, a voice and the actions they may return.
4. Try to break it in the dashboard. Lie, refuse, go off topic, ask about the weather for ten minutes. Adjust until the character stays in character and still gets back to the job.
5. Connect flowState to your quest system, so a keyword adds the quest, updates the journal or ends the scene.
6. Map actions and events: run the actions that come back, and send world events so side quests can come from what actually happened.

Keep each flow short. Three or four Checkpoints per quest conversation is plenty; more than that and the character starts sounding like it is ticking boxes. Flows run in one-to-one conversations, not in group chat, so give each quest one quest giver.

Quest givers are one of our AI NPC, ambient AI and voice command use cases. For the people who sell the player their gear, read AI shopkeeper NPCs, and for a narrator who runs the whole story, see an AI game master and narrator. The Conversation Flow feature page and the interactive storytelling page go deeper. Start with one quest and the beats it can't skip.

Checked October 2026.

Frequently Asked Questions