NPC TalkKit

English

Tiếng Việt

English

Tiếng Việt

Appearance

NPC TalkKitPlay conversations like you play animations

Add one node, write in the dedicated TalkKit workspace, call play(). Your player controller, quests and saves keep working exactly as before.

Quick start
How-to guides
API reference

Zero files to say a line

Add the node and write in the TalkKit main screen. Content lives in the scene. No database, no resource file per line, no setup step before the first word.

Several speakers, one conversation

A line names who says it. A speaker is a dialogue identity — a name, a face, a voice — never a gameplay character, so a narrator or a radio voice needs no node to exist.

2D and 3D

A bubble that tracks a character's head in 3D, with the camera traps handled — behind-camera, distance, occlusion. Or pinned to the screen. The template does not decide.

Branching without a branching engine

A blocking event pauses playback and hands control back to your GDScript. Read your own quest state, then resume, stop, or jump to another conversation.

From flat panel to layered frame

Pick one of three presets and change a colour beside a live preview. Or drop in a nine-slice frame from an asset pack, then layer on a name box, a portrait frame and corner ornaments. The Anatomy Map shows which setting draws which part.

Game owns the logic

No condition DSL, no variable store, no expression evaluator. Your quest system, inventory and flags already exist — TalkKit asks and waits.

Documentation that is checked

Worked examples are included from real files — the test suite runs the GDScript and compiles the C# — and a checker verifies every API name the prose mentions still exists in the addon.

Script-first writing is coming

The workspace already previews a future writer-friendly script view for long conversations and clean Git review. It will project onto the same resources—no second data model.

The whole integration ​

gdscript
$NPCTalkKit.play(&"greeting", {"player_name": "Alex"})

Opt into as much coupling as you want, and no more:

gdscript
$NPCTalkKit.request_player_lock.connect(set_player_locked)
$NPCTalkKit.event_triggered.connect(handle_talk_event)

No autoload. No base class. No change to the architecture you already have.

Player choice, in five lines ​

gdscript
func _on_blocked(event_id: StringName, payload: Variant) -> void:
    var accepted: bool = await choice_ui.ask(payload["options"])
    $NPCTalkKit.play(&"quest_accepted" if accepted else &"quest_declined")

There is no condition language here because your game already has one. How branching works →

GDScript-first. No telemetry, no network requests, no AI service dependency in the shipped addon.

NPC TalkKit 2.0.0 — © 2026 VanQuyt · Product page · Support