본문으로 건너뛰기
cccskills
무료GitHub에 공개

godot-genre-visual-novel

Expert blueprint for visual novels (Doki Doki Literature Club, Phoenix Wright, Steins;Gate) focusing on branching narratives, dialogue systems, choice consequences, rollback mechanics, and persistent flags. Use when building story-driven, choice-based, or dating sim games. Keywords visual novel, dialogue system, branching narrative, typewriter effect, rollback, bbcode, RichTextLabel.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

실행 점수 미검증

설치 방법 보기

포함된 파일(12)

  • SKILL.md12.1 KB
  • references/architecture-overview.md1.7 KB
  • references/common-pitfalls.md403 B
  • references/core-loop.md272 B
  • references/godot-47-visual-novel-ui.md119 B
  • references/godot-tips.md452 B
  • references/key-mechanics.md2.2 KB
  • references/migration-notes.md3.6 KB
  • scripts/dialogue_ui.gd2.7 KB
  • scripts/story_manager.gd3.5 KB
  • scripts/visual_novel_patterns.gd3.9 KB
  • scripts/vn_rollback_manager.gd2.7 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Genre: Visual Novel

Branching narratives, meaningful choices, and quality-of-life features define visual novels.

Core Loop

  1. Read → dialogue / narration
  2. Decide → choice moment
  3. Branch → flag or path change
  4. Consequence → immediate line variation and/or lasting flag
  5. Conclude → one of multiple endings

NEVER Do (Expert Anti-Patterns)

Narrative & Flow

  • NEVER create the "Illusion of Choice" exclusively; strictly provide Immediate Dialogue Variations or Flag Changes even if the plot converges later.
  • NEVER skip mandatory QoL features; strictly implement Auto-Play, Fast-Forward, and Backlog/History for replayability.
  • NEVER display "Walls of Text"; strictly limit dialogue boxes to 3-4 Lines max to avoid intimidating the reader.
  • NEVER hardcode dialogue text inside GDScripts; strictly store narrative scripts in External Files (JSON, CSV, or custom Resources) for iteration.
  • NEVER ignore the Rollback mechanic; strictly maintain a history stack so players can undo miss-clicks or reread missed lines.

Technical & UI

  • NEVER use plain text for emotional beats; strictly use RichTextLabel BBCode (e.g., [shake], [wave]) to add visual weight.
  • NEVER parse massive narrative files on the main thread; strictly use ResourceLoader.load_threaded_request() to prevent transition stutters.
  • NEVER use standard Strings for frequently accessed game flags; strictly use StringName (&"met_alice") for faster dictionary lookups.
  • NEVER use _process for letter-by-letter animation; strictly use a Tween on visible_ratio for smooth, frame-independent reveals.
  • NEVER neglect character Z-ordering; strictly ensure the active speaker is brought to the front for visual clarity.
  • NEVER use z_index for Control node priority if input handling is required; strictly use move_to_front() to ensure draw order and input propagation match.
  • NEVER use absolute pixel positioning for character sprites; strictly rely on Anchors & Percent-based Offsets for responsive scaling.
  • NEVER allow text animations to continue when the player skips; strictly set visible_ratio to 1.0 instantly on input.
  • NEVER leave orphaned character sprites; strictly use queue_free() when actors exit the stage to prevent memory leaks.
  • NEVER mutate flags before snapshotting rollback state — always push history, then apply the choice.

🛠 Expert Components (scripts/)

MANDATORY before implementing undo / branching / presentation:

  1. vn_rollback_manager.gd — history stack (flags/backgrounds/index)
  2. story_manager.gd — flag-aware dialog orchestration
  3. dialogue_ui.gd — typewriter + choice UI
  4. visual_novel_patterns.gd — BBCode, choice filtering, sprite layering

Catalog (deduped)

  • story_manager.gd - Flag-aware dialog orchestrator with branching logic and character state persistence.
  • dialogue_ui.gd - Presentation layer: typewriter tweens (visible_ratio) and choice-window generation.
  • vn_rollback_manager.gd - History stack for state rollback (flags/backgrounds/index).
  • visual_novel_patterns.gd - Reusable BBCode effects, choice filtering by flags, sprite layering.

Decision Tree: Script Storage vs Plugin

ApproachWhen to chooseNotes
JSON / CSV scriptsWriters edit outside Godot; rapid iterationLoad via FileAccess or threaded ResourceLoader; validate schema in StoryManager
Custom Resource dialogue treesDesigner Inspector editing, typed fieldsPeer godot-resource-data-patterns; MANDATORY story_manager.gd
Dialogic (plugin)Full VN suite (timelines, characters, themes) with editor toolingPrefer when shipping a large route graph fast; still keep rollback + flag discipline. Skip building a second StoryManager if Dialogic already owns timelines
Build lightweight customTiny kinetic novel / learning projectUse scripts in this skill; do not re-stub StoryManager inline

Do not paste incomplete JSON StoryManager demos — implement from MANDATORY story_manager.gd.


Golden Path (order matters)

  1. Snapshot before mutate — On every advance/choice, MANDATORY vn_rollback_manager.gd pushes {line_index, flags, background, music} before flag writes.
  2. Typewriter + skip — dialogue_ui.gd: Tween visible_ratio 0→1; on skip/advance input set visible_ratio = 1.0 and kill the tween.
  3. Choice filter by flags — Present only options whose requires StringName flags pass; apply choice → mutate flags → jump label (visual_novel_patterns.gd + story_manager.gd).
  4. Speaker focus — move_to_front() on Control actors (not z_index alone) + dim inactive.
  5. Heavy CG/BG — ResourceLoader.load_threaded_request for backgrounds; never sync-parse huge scripts on the main thread.
# Choice handler shape (flags after snapshot)
func make_choice(choice_id: StringName) -> void:
    rollback_manager.push_snapshot()  # BEFORE mutate
    match choice_id:
        &"be_nice":
            flags[&"relationship_alice"] = int(flags.get(&"relationship_alice", 0)) + 1
            story_manager.jump_to_label(&"alice_happy")
        &"be_mean":
            flags[&"relationship_alice"] = int(flags.get(&"relationship_alice", 0)) - 1
            story_manager.jump_to_label(&"alice_sad")

Common Pitfalls

  1. Walls of text — Cap dialogue to 3–4 lines.
  2. Illusion of choice — Always vary lines or flags even on converging plots.
  3. Missing QoL — Auto / Skip / Backlog / Save are mandatory genre features.
  4. Broken rollback — Mutating flags before snapshot makes undo lie.

Deep recipes (on demand)

TopicReference / script
Story driver & typewriter UIarchitecture-overview.md
Branching / rollback / focuskey-mechanics.md
RichText / async loadsgodot-tips.md

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

  • BBCode in RichTextLabel — shake/wave BBCode and append_text for emotional dialogue without plain Label walls.
  • Size and anchors — percent offsets and anchors so character sprites and dialogue boxes scale across resolutions.
  • GUI containers — VBox/HBox choice rows and dialogue chrome instead of absolute pixel layouts.
  • Background loading — ResourceLoader.load_threaded_request so heavy CG/background swaps never hitch the typewriter.
  • Saving games — FileAccess patterns for flags, history stacks, and multi-slot VN saves.
  • Resources — typed dialogue/choice Resources as an alternative to brittle hardcoded JSON strings.
  • Internationalizing games — tr() / CSV keys so script lines stay localization-ready.
  • Audio streams — BGM crossfades and optional voice lines tied to line advances.
  • Using InputEvent — skip/advance/ui_accept handling that finishes visible_ratio instantly.
  • Singletons (Autoload) — persistent flag/history owners across chapter scene changes.
  • Signals — line_advanced / options_presented wiring between StoryManager and DialogueUI.
  • Tween — tween_property on RichTextLabel.visible_ratio for frame-independent typewriter reveals.

Related Skills

Prerequisites

Complements

Downstream / consumers

Master

  • godot-master — library router and mirrored module entry for cross-skill discovery.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Bevy ECS skill for 2D sprite animation. Keywords: Bevy, sprite, animation, AnimationPlayer, AnimationClip, 2D.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

thedivergentai/Game-Dev-Agentic-Skills8882026년 10월 17일 업데이트

Spawn and tune Bevy 0.20 directional, point, and spot lights, cascade shadows, distance fog, and a nearest-light shadow budget. Use when a 3D scene needs a sun, local lights, or fog on the camera. Keywords: DirectionalLight, PointLight, SpotLight, CascadeShadowConfig, DistanceFog, bevy_light.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

thedivergentai/Game-Dev-Agentic-Skills8882026년 10월 17일 업데이트

Bevy ECS skill for PBR materials. Keywords: Bevy, StandardMaterial, PBR, material, ExtendedMaterial.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

thedivergentai/Game-Dev-Agentic-Skills8882026년 10월 17일 업데이트

Bevy ECS skill for 3D level assembly. Keywords: Bevy, level, scene, mesh, world, ECS.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

thedivergentai/Game-Dev-Agentic-Skills8882026년 10월 17일 업데이트

Bevy ECS skill for abilities. Keywords: Bevy, ability, cooldown, ECS, gameplay.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

thedivergentai/Game-Dev-Agentic-Skills8882026년 10월 17일 업데이트

Rewrite Bevy 2D actors and cameras into 3D meshes and Camera3d while keeping gameplay components. Use when a Bevy 2D game should gain a perspective camera, mesh draw, and a planar velocity lifted onto XZ. Keywords: Camera2d, Camera3d, Sprite, Mesh3d, StandardMaterial, WishVelocity.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

thedivergentai/Game-Dev-Agentic-Skills8882026년 10월 17일 업데이트

thedivergentai의 스킬 모두 보기

이 스킬의 문제 신고