thedivergentai/game-dev-agentic-skills

godot-dialogue-system

Expert patterns for branching dialogue systems including dialogue graphs (Resource-based), character portraits, player choices, conditional dialogue (flags/quests), typewriter effects, localization support, and voice acting integration.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/thedivergentai/game-dev-agentic-skills --skill godot-dialogue-system

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

Dialogue System

Data-driven dialogue routing — not beginner typewriter tutorials.

NEVER Do in Dialogue Systems

  • NEVER hardcode dialogue text in GDScript — Store lines in Resources / JSON / CSV so localization works.
  • NEVER show choices the player has not unlocked — Hide (or intentionally gray) gated options.
  • NEVER use unvalidated loose strings for node transitions — Typos in next_node_id soft-lock mid-convo; assert / registry IDs.
  • NEVER force a typewriter without skip — Click/confirm must finish the line immediately.
  • NEVER drive reveal with per-character `Timer` / `OS.delay_msec()` — Use visible_ratio / visible_characters + Tween (see typebox_effect.gd).
  • NEVER store dialogue cursor state only in the UI node — Scene changes drop the player; keep progress in the manager Autoload / session object.
  • NEVER `get_node()` from NPCs into Dialogue UI — Start via manager signals (start_dialogue(res)).
  • NEVER invent regex for BBCode — Prefer RichTextLabel BBCode / custom effects.
  • NEVER save/load inside a dialogue node Resource — Nodes are data; persistence belongs to SaveSystem.
  • NEVER hardcode portrait paths in code — Assign textures on node Resources or a portrait database.

Decision Tree: Authoring Engine

Authoring needEngineMANDATORY scriptsDo NOT Load
Designer-friendly .tres graphs in-repoResource Autoload graphdialogue_resource.gd → dialogue_manager_singleton.gd → dialogue_ui_controller.gd → typebox_effect.gddialogue_engine.gd JSON path
External writers / spreadsheet → JSONJSON graph enginedialogue_engine.gd (+ optional dialogue_manager.gd) → UI + typeboxResource Autoload stack
Visual node editor in-projectGraphEdit authoringKeep runtime on Resource or JSON export; GraphEdit is editor-only toolingShipping GraphEdit as the runtime walker
Conditions / quest gatesEitherbranching_condition_validator.gdEmbedding flag checks in UI buttons
Portraits / expressionsEitherdialogue_portrait_manager.gd—
Localization keysEitherlocalized_dialogue_resource.gdHardcoded language if trees
Quest / gameplay hooks from linesEitherdialogue_event_bridge.gdSide effects inside UI controller

Default golden path: Resource Autoload → UI controller → typebox_effect. Pick one runtime engine; do not run Resource manager and JSON engine in parallel.

Available Scripts (single catalog)

Runtime (golden path)

Supporting

Alternate engines (load only if decision tree says so)

Typewriter Contract (skip-safe)

Use typebox_effect.gd: set full text, tween visible_ratio (or RichTextLabel visible_characters) from 0→1. On skip input: kill tween and snap visibility to complete. Do not spawn a Timer per character.

Elite Deltas

MANDATORY for GraphEdit tooling, TTS/lipsync, analytics, and moved inline manager/UI tutorials: elite-dialogue-patterns.md. Do NOT Load for Resource Autoload golden path only.

Reference

Progressive disclosure: open Official Documentation links only when researching a specific API; load Related Skills when routing to a peer domain — do not preload the whole lattice.

Official Documentation

  • Resources — Why dialogue graphs belong in Resource / .tres data instead of hardcoded strings in scripts.
  • BBCode in RichTextLabel — Native markup for speaker emphasis, custom tags, and effects without rolling your own parser.
  • RichTextLabel — visible_characters / image helpers and BBCode APIs the dialogue UI should drive for typewriter and portraits.
  • Internationalizing games — tr() / TranslationServer workflow so line text stays key-based across locales.
  • Localization using spreadsheets — CSV translation tables that map cleanly onto dialogue text_key fields.
  • Importing translations — How Godot imports CSV/PO so localized dialogue resources resolve at runtime.
  • Using signals — Emit line/choice/end events upward so UI, quests, and audio never hard-reference the manager internals.
  • Singletons (Autoload) — Register a DialogueManager that survives scene changes and owns traversal state.
  • Tween — Drive visible_ratio / character reveal timing without blocking the main thread.
  • Text-to-speech — DisplayServer TTS callbacks for placeholder VO and lipsync-adjacent timing.
  • GraphEdit — Editor surface for authoring branching dialogue graphs when .tres lists become unwieldy.
  • JSON — Parse external dialogue graph files when designers prefer JSON over Resources.

Related Skills

Prerequisites

Complements

  • godot-signal-architecture — Signal-up / call-down contracts for line_displayed, choice selection, and narrative event bridges.
  • godot-ui-rich-text — RichTextLabel BBCode, custom effects, and image embedding beyond the basics used in typewriter UIs.
  • godot-ui-containers — Layout choice buttons and dialogue panels without fighting Control sizing and focus.
  • godot-tweening — Skip-safe Tweens for character reveal, portrait entry, and panel transitions.
  • godot-audio-systems — Voice-line players, bus ducking during dialogue, and subtitle sync with spoken audio.
  • godot-quest-system — Quest flags and objectives that gate conditional choices and fire from dialogue event bridges.
  • godot-save-load-systems — Persist dialogue flags / seen-node state outside UI nodes so progress survives reloads.

Downstream / consumers

  • godot-genre-visual-novel — Full VN presentation loops consume this skill’s graph traversal, portraits, and choice UI patterns.
  • godot-inventory-system — Dialogue effects often grant/require items; keep grant logic in inventory, not inside line Resources.
  • godot-monte-carlo-balancer — Simulate skill-check / branching choice trees when narrative gates or reward paths need balance passes.

Master

  • godot-master — Library router and mirrored module entry; open when discovering which Domain Skill owns narrative, UI, or quest concerns.
같은 저장소의 Skills

더 많은 Skills

모든 Skills
thedivergentai
커뮤니티

godot-combat-system

Expert patterns for combat systems including hitbox/hurtbox architecture, damage calculation (DamageData class), health components, combat state machines, combo systems, ability cooldowns, and damage popups. Use for action games, RPGs, or fighting games. Trigger keywords: Hitbox, Hurtbox, DamageData, HealthComponent, combatstate, combosystem, abilitycooldown, invincibilityframes, damagepopup.

1시간 설치 수
1
GitHub Stars
977
업데이트
10월 16일
thedivergentai
커뮤니티

godot-2d-animation

Expert patterns for 2D animation in Godot using AnimatedSprite2D and skeletal cutout rigs. Use when implementing sprite frame animations, procedural animation (squash/stretch), cutout bone hierarchies, or frame-perfect timing systems. Trigger keywords: AnimatedSprite2D, SpriteFrames, animationfinished, animationlooped, framechanged, frameprogress, setframeandprogress, cutout animation, skeletal 2D, Bone2D, procedural animation, animation state machine, advance(0).

1시간 설치 수
2
GitHub Stars
969
업데이트
10월 16일
thedivergentai
커뮤니티

godot-camera-systems

Expert patterns for 2D/3D camera control including smooth following (lerp, positionsmoothing), camera shake (trauma system), screen shake with frequency parameters, deadzone/drag for platformers, look-ahead prediction, and camera transitions. Use for player cameras, cinematic sequences, or multi-camera systems. Trigger keywords: Camera2D, Camera3D, SpringArm3D, positionsmoothing, camerashake, traumasystem, lookahead, dragmargin, cameralimits, cameratransition.

1시간 설치 수
2
GitHub Stars
969
업데이트
10월 16일
thedivergentai
커뮤니티

godot-particles

Expert blueprint for GPU particle systems (explosions, magic effects, weather, trails) using GPUParticles2D/3D, ParticleProcessMaterial, gradients, sub-emitters, and custom shaders. Use when creating VFX, environmental effects, or visual feedback. Keywords GPUParticles2D, ParticleProcessMaterial, emissionshape, colorramp, subemitter, oneshot.

1시간 설치 수
2
GitHub Stars
969
업데이트
10월 16일