#Dreamcatcher User Guide

#About this guide

For Godot users who want to create games visually, learn step by step, and still keep full access to Godot-native workflows.

Product: Dreamcatcher v0.9.4 Early Access
Engine target: Godot 4.7 stable compatibility-targeted; Godot 4.6.3 supported
Creator: Journey Beyond Horizons / JBH PRODS
Guide type: User guide, tutorials, and reference

Use this guide to install Dreamcatcher, build your first playable scene, understand the main tools, create maps and interactions, manage generated assets, validate your project, and prepare for export.

Begin with the first-day tutorials, then use the reference sections when you need exact tool, resource, module, or workflow details.

#At a glance

#Version and scope

Dreamcatcher helps you move faster inside Godot, but it does not remove the need to test your project. Exact editor labels can vary slightly between builds, generated assets may still require manual wiring, and final exports still depend on Godot export templates, platform requirements, signing, accounts, and project-specific testing.

#Documentation and version-history map

This public guide matches the current Dreamcatcher v0.9.4 package: 866 addon files, 729 GDScript files, 13 Markdown documentation files, and complete release notes from v0.9.0 through v0.9.4.

Current package note: this guide and README.md describe the current Dreamcatcher v0.9.4 package inventory. Older notes or summaries may describe earlier builds.

Developer QA checklists and internal audit/implementation reports are maintained outside the public addon package. Buyers should use this manual, the compatibility notes, the changelog, the current release notes, and normal Godot project testing.

#Roadmap after v0.9.4 ?

Roadmap note: these are planned improvements after v0.9.4. They are not current v0.9.4 guarantees.

#How to use this documentation

This page is long because Dreamcatcher is a large toolkit. You do not need to read everything at once. Use the route that matches what you are trying to do today.

#Welcome to Dreamcatcher

Dreamcatcher is a no-code / low-code game creation toolkit for Godot 4.7 stable and Godot 4.6.3. It adds a large set of editor tools, visual logic workflows, genre helpers, templates, game-data resources, generated asset management, validation tools, and export-preflight helpers on top of normal Godot projects.

The purpose of Dreamcatcher is not to hide Godot from you. It is to help you move faster inside Godot: create a scene, choose a genre direction, generate or organize content, add interactions, test quickly, and keep your work as project-owned Godot scenes/resources instead of locked proprietary data.

The best first goal is simple: create one small playable scene, add one interaction, validate it, and run Quick Play. After that, you can grow into maps, generated assets, database resources, UI, narrative, audio, VFX, Visual Logic, genre starter workflows, and advanced project management tools.

#Read this first if Dreamcatcher feels overwhelming

Dreamcatcher is large, but you do not need to learn everything at once. Your first goal is not to master all tools. Your first goal is to create one small playable scene.

Use this order:

1. Choose a Genre DNA: pick a direction such as Universal, Platformer, Action RPG, or Visual Novel.
2. Create or open one small scene: use Scene Composer or a safe test scene.
3. Add one interaction: use Visual Logic, Map Editor, or a simple event.
4. Validate it: use Content Validator and read warnings.
5. Test it with Quick Play: confirm the interaction works.

Ignore everything else until your first scene works.

After your first scene works, choose only one next path:

#Learning paths: choose your starting route

Use these routes instead of reading the whole manual from top to bottom.

#What Dreamcatcher is and is not

#Dreamcatcher is

• A Godot 4.7 stable / 4.6.3 plugin for visual/no-code-friendly game creation.
• A collection of editor tools for scenes, maps, UI, narrative, sound, animation, asset generation, validation, modules, and export preparation.
• A project-content workflow: generated outputs should be saved into your project under res://dream/..., not into the plugin folder.
• A low-code bridge: beginners can start visually, while advanced users can still use Godot scenes, resources, nodes, scripts, and normal export workflows.
• An Early Access v0.9.4 package focused especially on the generated asset registry/browser and project-owned generated-content workflow.

#Dreamcatcher is not

• Not an automatic shortcut that ships a complete commercial game.
• Not a replacement for every part of Godot.
• Not a guarantee that every platform export is turnkey.
• Not an asset-rights provider for third-party artwork.
• Not a v1-stable API promise yet.
• Not a full v0.9.5 runtime-binding release for every generated UI/audio/VFX/animation case.

#Early Access scope and boundaries

Dreamcatcher v0.9.4 should be presented as an Early Access generated-asset pipeline release. The central v0.9.4 improvement is that generated outputs can become registry-tracked project content with metadata, preview information, reports, paths, validation state, dependencies, generation presets, and assignment metadata.

In practical terms, v0.9.4 means:

Dreamcatcher v0.9.4 helps you create scenes, maps, game data, generated assets, UI, audio, VFX, and validation workflows while keeping generated content inside your project folders.

Important boundaries:

• Direct regeneration is available for supported stored dungeon/map/overworld presets. Other asset types may be inspectable, duplicateable, assignable, exportable, or validatable, but not necessarily directly regenerable.
• Apply/Assign can write safe metadata and supported fields to known Dream resources. Some assignments are metadata-only so the asset can be traced and validated.
• Full runtime binding for every generated audio/VFX/UI/animation case is a later-scope concern, not a v0.9.4 promise.
• Export Manager and Export Preflight help prepare for Godot export. They do not remove the need for Godot export templates, SDKs, platform accounts, platform-holder approval, or normal platform requirements.

#Known limitations in v0.9.4 ?

Dreamcatcher v0.9.4 is an Early Access release. The documentation is written to help you build safely without promising that every advanced system is finished or automatic.

#Status labels used in this guide ?

#Requirements and installation

#Requirements

• Godot 4.7 stable is the compatibility target for new projects. Godot 4.6.3 remains supported for existing 4.6.x projects.
• A Godot project. First-time users should start in a clean test project before using Dreamcatcher inside an existing project.
• The addons/dreamcatcher/ folder from the Dreamcatcher release.
• No third-party Godot add-on is required by the plugin files themselves.
• Exporting still requires the normal Godot export templates and platform-specific requirements.

#Install Dreamcatcher

1. Create or open a Godot 4.7 stable project. Godot 4.6.3 is also supported.
2. Copy the plugin folder into your project so the path is exactly:

Copyyour_project/
├── addons/
│  └── dreamcatcher/
│    ├── plugin.cfg
│    └── plugin.gd
├── project.godot
└── ...

3. Open the project in Godot.
4. Go to Project → Project Settings → Plugins.
5. Enable Dreamcatcher.
6. Restart Godot if panels do not appear immediately.

Common mistake: double nesting. This is wrong:

Copyaddons/dreamcatcher/dreamcatcher/plugin.cfg

Correct path:

Copyaddons/dreamcatcher/plugin.cfg

#Verifying installation

After enabling the plugin, check for Dreamcatcher editor surfaces such as the main Dreamcatcher / Almanac workspace, Dream Board, Dream DNA, Dream Console, Dream Inspector, Quick Play controls, and the visible editor tools. The exact layout can vary depending on Godot editor layout, enabled modules, and whether the plugin is in headless/no-autoload mode.

The plugin registers 28 autoloads unless dreamcatcher/advanced/no_autoload_mode is enabled. It also registers 113 custom node types gated by the module manifest. If something appears missing, check the Module Manager and advanced no-autoload setting before assuming the plugin is broken.

Recommended first verification checklist:

• The plugin appears in Project Settings → Plugins and can be enabled.
• Dreamcatcher UI panels appear after enabling or after restarting Godot.
• No critical errors appear in the Godot output panel.
• Quick Play controls are visible or available from the Dreamcatcher workflow.
• A clean project can open the Dreamcatcher workspace.
• The Module Manager shows expected modules as enabled.

#What you should see after installing

• Dreamcatcher appears in Project Settings → Plugins and can be enabled.
• Dreamcatcher docks/tools appear once after the editor reloads.
• New Dreamcatcher custom nodes are searchable in the Godot node dialog when their modules are enabled.
• Autoload services appear in Project Settings → Autoload unless advanced no-autoload mode is intentionally used.
• The Godot Output panel should not show parse errors when the plugin loads.

#Your first 10 minutes

Do not try to learn all 24 tools immediately. The first 10 minutes should build orientation and confidence.

1. Open the Dreamcatcher workspace or Almanac.
2. Choose Universal, Platformer, or Action RPG as your first Genre DNA.
3. Open Scene Composer and create or inspect a small scene/template.
4. Open Generated Asset Browser so you know where generated outputs will appear.
5. Open Content Validator so you know where warnings and readiness checks appear.
6. Run or prepare to run Quick Play on a small test scene.

Success is not “I understand everything.” Success is “I know where to start, where generated content goes, and where to test/fix problems.”

#Build your first playable scene

#What you will make

A small scene with one playable interaction. Use Platformer, Action RPG, Top-down Adventure, or Universal depending on your comfort level.

#Steps

1. Create a clean test project in Godot 4.7 stable. Godot 4.6.3 is also supported.
2. Install and enable Dreamcatcher.
3. Choose a beginner-safe Genre DNA: Universal, Platformer, or Action RPG.
4. Open Scene Composer and create a starter scene or blank safe test scene.
5. Add one player/actor or use the template-provided actor.
6. Add one simple interaction: a door, chest, pickup, NPC dialogue, trigger, or test area.
7. If useful, generate one icon, sound, map, dungeon, loot table, or database resource and save it as project-owned content.
8. Run Content Validator and read warnings carefully. Fix one warning if possible.
9. Run Quick Play and confirm the interaction works.
10. Save the scene and continue into maps, Visual Logic, UI, audio, or a genre starter workflow.

#First success criteria

• You created or opened one scene.
• You added or checked one interaction.
• You know where the project-owned output was saved.
• You validated the scene or asset.
• You tested the result in Quick Play or normal Godot play mode.

#Interface tour

Dreamcatcher is easier to learn when you think in workspaces, not files.

Main
  ├── Player: DreamActor2D
  ├── Door: Node2D
  │   ├── DreamInteractable2D
  │   └── DreamBehavior
  └── UI

Main
  ├── Player: DreamActor2D
  └── IntroTrigger: DreamTrigger2D
      └── CollisionShape2D

Main
  ├── Player: DreamActor2D
  │   └── AttackArea: DreamHitbox2D
  └── Enemy: DreamActor2D
      └── HurtArea: DreamHurtbox2D

#Click-by-click learning path for new users

#Where do I click? Dreamcatcher navigation map

Most Dreamcatcher work starts from the Dreamcatcher dock or panel inside the Godot editor. If a button label is slightly different in your build, use the tool name and nearby label. Dreamcatcher v0.9.4 is Early Access, so exact labels may vary slightly between builds; use the tool name and nearby label if your screen differs.

#Small dictionary for first-time Godot users

Read this before following scenarios. These words appear everywhere in Godot and Dreamcatcher.

#How to follow a click-by-click tutorial

Every beginner workflow should be read like a workflow. Do not continue just because a step is written. Continue only when the expected result appears.

#Which tool should I open?

#Project folders and generated content

Dreamcatcher separates plugin files from your game files. This is essential for safety, backups, export, migration, and project ownership.

Copyaddons/dreamcatcher/    Plugin files. Do not save your generated game content here.
res://dream/generated/   Generated project-owned outputs.
res://dream/generated/_registry/ Registry records for generated assets.
res://dream/database/    Generated or managed game-data resources.
res://dream/maps/generated/ Generated editable map scenes when supported.
scenes/, actors/, items/, etc. Your normal Godot project folders.

Rule: if you created it, generated it, imported it, or plans to ship it, it should live in the project, not inside addons/dreamcatcher/.

#Visual workflow maps

Use these diagrams as a quick mental map. They are intentionally simplified so new users are not forced to learn every tool at once.

#Infographic 1: First playable path

#Infographic 2: Dreamcatcher tool map

#Infographic 3: Generated asset lifecycle

Regeneration is mainly supported for stored dungeon, map, and overworld presets in v0.9.4.

#Infographic 4: Project folder safety map

#Infographic 5: Validation and export-preflight gates

#Infographic 6: Learning ladder

#Build your first full game loop

#What this course teaches

#The game loop formula

#Metaphors that make the system easier

#Universal connection order

Most Dreamcatcher gameplay objects follow the same safe order. When something breaks, return to this order and find the missing link.

1. Create the visible thing.
2. Give it data.
3. Give it collision/area if it must touch or detect.
4. Give it logic.
5. Attach the logic.
6. Add feedback.
7. Save state if the result must persist.
8. Validate.
9. Quick Play.
10. Repeat with the next object.

#Which tool owns which part?

#Game object anatomy

Use this anatomy for NPCs, enemies, chests, doors, pickups, and interactive props.

#Full tutorial: first Action RPG quest room

#Quick Play test order for the loop

1. Player spawns.
2. Player moves.
3. Walls block movement.
4. Camera follows.
5. Interact near NPC opens dialogue.
6. Choosing “Yes” starts the quest.
7. Slime exists.
8. Slime detects the player.
9. Attack damages slime.
10. Slime attacks or reacts.
11. Slime dies.
12. Quest updates.
13. Return to NPC gives reward.
14. Door unlocks.
15. HUD/objective feedback updates.

#What starts what? Trigger guide

A trigger is the thing that starts logic. Most “nothing happened” bugs are trigger bugs: the graph exists, but nothing started it.

#Visual Logic integration: how a graph becomes behavior

A Visual Logic graph becomes game behavior only after three things exist: a trigger, an assigned graph, and a target object that can run it.

#Attachment methods

#Connect Narrative Weaver to gameplay

Narrative Weaver owns words, choices, and branches. Visual Logic owns consequences. A choice only changes the game when it is linked to state, a quest, a resource, a graph, or a map event.

#Level design with Map Editor

Map editing is not only painting pretty tiles. A playable level needs purpose, path, blockers, collision, navigation, events, regions, feedback, and a testable goal.

#First level templates

#Player, input, collision, and navigation

Player control becomes reliable only when input, body, collision, camera, interaction area, attack area, and map collision agree.

#First combat loop

Combat is not one button. It is a chain from input to feedback and state.

#First enemy AI

For the first enemy, use a simple finite-state machine instead of a complex behavior tree.

#Make the game remember

State is the game’s notebook. It is what makes a chest stay open, a defeated enemy stay defeated, a door stay unlocked, and an NPC say different lines later.

#Generated assets: from generator to game

Generated content is useful only after you inspect it, assign it, validate it, and test it in context.

#If nothing happens: debugging Dreamcatcher logic

Debugging is checking the chain from player action to feedback. Do not randomly change many things. Follow the chain.

#Workflow diagrams

#Additional practice routes

Use these after the first Action RPG loop works. They are not separate tool demos; they are small playable slices.

#Before you continue

Before calling a tutorial complete, test it against these questions.

• Can a beginner identify which tool owns each part?
• Can the player perform a visible action?
• Does the action have a trigger?
• Is the graph assigned to the object that should run it?
• Does the graph change state or content?
• Does the player receive visible/audio feedback?
• Does the result persist if it should?
• Does Content Validator catch missing links?
• Can Quick Play prove the loop from beginning to end?

#Core creation workflow

The plugin is large, but the workflow is simple:

CopyIdea
→ Choose Genre DNA
→ Create scene/map/UI/resource
→ Generate assets if useful
→ Inspect metadata/reports
→ Assign or apply supported outputs
→ Validate
→ Quick Play
→ Improve
→ Export Preflight

Use Scene Composer for scenes, Map Editor for maps, Database for game data, Visual Logic for interactions, UI Builder for menus/HUDs, Sound Studio for sound/music, Generated Asset Browser for generated content management, and Content Validator before you trust a scene or export.

#Choosing a Genre DNA profile ?

Genre DNA is a user-facing workflow preset. It changes Dreamcatcher’s recommendations, tool focus, templates, and creation flow based on the kind of game you want to build. It should not be explained as an technical system.

Recommended beginner choices:

• Universal: best when you are experimenting or unsure.
• Platformer: best for first movement, camera, checkpoints, pickups, and simple level flow.
• Action RPG: best for items, enemies, quests, loot, combat, and NPC interactions.
• Visual Novel: best for dialogue, choices, portraits, chapters, and scenes.
• Top-down Adventure / Action Adventure: best for doors, pickups, NPCs, and objectives.

Statuses matter. Stable profiles are more complete public workflows. Beta profiles are usable but evolving. Early Access foundation profiles expose foundations but may require more manual setup.

#Genre DNA catalog ?

Tip: hover or focus the help markers and table rows for short explanations.

#Scene Composer

Scene Composer is the place to browse, create, duplicate, and export scenes from templates. The current package README identifies 154 unique Scene Composer template entries, while the package itself contains 36 bundled .tscn scene/runtime UI files. Public docs should use that distinction instead of saying only “36 scene templates.”

Use Scene Composer when you want to:

• Start from a template instead of a blank scene.
• Create a first playable scene quickly.
• Explore genre-specific starter scenes.
• Duplicate a scene safely before experimenting.
• Export or save a template-derived scene into your project.

Beginner task: create a Platformer or Action RPG test scene, save it, validate it, and run Quick Play before editing it deeply.

#Understanding scene-template counts

Dreamcatcher has several scene/template numbers because they describe different things:

• 154 unique DreamTemplateData templates exist in the template data registry.
• These are merged through 43 internal template data groups.
• The Scene Composer UI currently shows 36 visible category groups.
• Those visible groups currently list 149 unique template names.
• The package separately contains 36 bundled .tscn files used for scenes, UI, demos, or editor/runtime surfaces.

So if you see “154 templates” and “36 .tscn files,” they are not contradictory. They count different parts of the package.

#Generated asset workflow ?

Generated assets are project-owned outputs tracked by Dreamcatcher. A generated asset can include metadata, preview data, generation presets, reports, output paths, dependencies, validation status, and assignment metadata.

The public workflow is:

CopyGenerate
→ Preview
→ Inspect metadata
→ Read the report
→ Validate
→ Assign/apply if supported
→ Save inside the project
→ Reuse, duplicate, regenerate if supported, or clean up

Generated outputs should normally live under res://dream/generated/; generated database resources should live under res://dream/database/; registry records live under res://dream/generated/_registry/.

#Assignment boundary

In v0.9.4, Apply/Assign can write safe metadata and supported fields to known Dream resources. Some assignments are metadata-only so the asset can be traced and validated. Full runtime binding for every generated audio/VFX/UI/animation case is not a v0.9.4 promise.

#Direct regeneration boundary

Direct regeneration is supported for stored dungeon/map/overworld presets. Other types may be viewable, duplicated, deleted, assigned, or validated, but regeneration may be disabled until deterministic preset contracts exist.

#Generated Asset Browser ?

Generated Asset Browser is the library for content created by Dreamcatcher. Use it to keep generated work from becoming scattered files.

Use it to:

• Browse generated outputs by type.
• Inspect metadata, previews, reports, output paths, dependencies, and validation status.
• Validate generated asset records and outputs.
• Duplicate useful generated assets.
• Delete failed experiments safely, while understanding whether output files remain project-owned.
• Assign icons, sprites, audio/VFX metadata, formulas, palettes, loot/name tables, UI scenes, and database references where supported.
• Regenerate supported map/dungeon/overworld outputs from stored presets.

If a generated output exists on disk but does not appear in the browser, run validation, refresh the Godot filesystem, and check whether the registry record exists under res://dream/generated/_registry/.

#What Assign/Apply means in v0.9.4

Assign/Apply is safe but not automatical. In v0.9.4 it can write supported fields and metadata to known Dream resources. Some assignments are intentionally metadata-only so you can trace, validate, and organize the generated asset. Full automatic runtime binding for every audio, VFX, UI, animation, and generated content case is not a v0.9.4 promise.

#Assignment-key reference for generated assets ?

#Generated asset type reference ?

Tip: hover or focus the help markers and table rows for short explanations.

These are the canonical 18 generated asset registry types in v0.9.4. Database concepts such as items, enemies, quests, shops, skills, crafting rules, and dialogue are usually represented as database_resource, loot_table, name_table, or related resource outputs, not as separate top-level generated asset types.

Common user interpretation:

• Map / Overworld / Dungeon: generated layout content that may become editable map scenes with layers and regions.
• Sprite / Icon / Converted Image: visual assets usable by UI, items, actors, enemies, or scenes.
• Music / SFX / Converted Audio: audio outputs that can be assigned as metadata or to supported resources.
• VFX: visual effects that can be tracked and assigned where supported.
• Database Resource: generated game-data resources such as items, shops, enemies, quests, skills, or related .tres files.
• Loot Table / Name Table / Palette / Formula Preset: reusable data helpers for content generation, UI, combat, naming, themes, or balancing.
• 3D Shape / Isometric Scene / Dialogue UI: specialized generated content with project-owned records and validation.

#Database resources and game data

Database resources are reusable game-data files. They can represent actors, items, enemies, quests, cards, dialogue, shops, weapons, armor, crafting rules, loot tables, map-region data, creature-collector data, sports/racing configs, and more.

Use the Database tool when you want to create or edit structured game content. Use generated database workflows when you want Dreamcatcher to create starter data under res://dream/database/.

Basic resource workflow:

1. Choose the resource category, such as Item, Enemy, Quest, Shop, Skill, or Dialogue.
2. Create the resource or open an existing .tres file.
3. Fill required fields such as ID/name/description/references.
4. Assign generated icons, loot tables, name tables, formulas, or palettes where supported.
5. Save into your project, preferably under a clear folder such as res://dream/database/items/ or your normal project folders.
6. Validate to catch missing IDs, missing icons, invalid references, duplicate IDs, or incomplete relationships.

#Map Editor and TileMapLayer workflows

Map Editor is for map painting, map organization, and map gameplay metadata. v0.9.4 generated dungeons and overworlds can create editable DreamMapRoot scenes under res://dream/maps/generated/ using real TileMapLayer layers where supported.

Use Map Editor when you want to:

• Paint or edit a map.
• Organize layers such as terrain, walls, objects, collision, navigation, or visual detail.
• Place map events like doors, chests, NPCs, triggers, spawns, or exits.
• Paint gameplay regions such as encounter zones, music zones, weather zones, safe/danger zones, or fast travel points.
• Validate map structure before testing.

Beginner task: create a small map with one floor layer, one obstacle/collision area, one NPC/event, one region, and one Quick Play test.

#Map events

Map events are user-facing gameplay objects placed on maps. They are useful for classic adventure/RPG workflows and for visual no-code logic.

#Regions, encounters, music, weather, collision, and navigation

Regions give parts of a map gameplay meaning. v0.9.4 documentation can describe more than only encounters/music/weather. Public map-region behavior can include biome, encounter, music zone, weather zone, quest zone, cutscene trigger, safe zone, danger zone, fast travel, spawn, collision, navigation, and custom markers.

Practical examples:

• Paint an encounter region to control enemy encounter behavior.
• Paint a music zone to mark where a map BGM should apply.
• Paint a weather zone to mark rain, fog, storm, or ambience behavior.
• Paint a safe zone where random encounters or danger effects should stop.
• Paint collision and navigation helpers to guide movement and pathfinding setup.
• Paint a fast travel region to connect to another map or hub.

#Classic 48x48 layout workflows and asset rights

Dreamcatcher can help with Classic 48x48 tilesheet layout workflows and Godot-native TileSet setup. This should be described as layout compatibility, not as ownership of third-party artwork.

Safe public wording:

Classic 48x48 layout support means Dreamcatcher can help organize tilesheet-style workflows commonly used in grid-based 2D games. Only import artwork you created, own, or are licensed to use. Dreamcatcher does not grant rights to third-party proprietary assets.

Do not imply Dreamcatcher includes or licenses RPG Maker RTP/default/proprietary art. Use Dreamcatcher-owned wording such as Classic 48x48 layout profiles, compatible tilesheet import, Godot-native TileSet workflow, and asset-rights guidance.

#Visual Logic basics

Visual Logic lets you create gameplay behavior by connecting triggers, conditions, actions, variables, and feedback without writing GDScript.

Beginner mental model:

CopyWhen this happens
→ Check this condition
→ Do this action
→ Show feedback
→ Save
→ Quick Play

#Visual Logic templates as starting points

Visual Logic templates are small behavior patterns. Use them as a starting graph, then connect the graph to a real trigger, a condition, an action, feedback, and a state change.

What you should see: a saved graph/resource, a node or map event pointing to it, a clear trigger signal, visible feedback during Quick Play, and a changed state if the graph is supposed to remember progress.

#Visual Logic practical tutorials

#NPC dialogue

1. Place or select an NPC/interactable object.
2. Create or assign a dialogue resource.
3. Add a Visual Logic sequence: When player interacts → Show dialogue.
4. Save and Quick Play.

#Locked door

1. Place a door or transfer event.
2. Create a key item resource.
3. Create a Visual Logic sequence: When player interacts → Check key item → Open door or show locked message.
4. Validate missing item/scene references.

#Chest reward

1. Create an item resource.
2. Place a chest event.
3. Add logic: Interact → If not opened → Give item → Play sound/VFX → Set opened true.
4. Validate the item reference and test twice to confirm it does not give infinite rewards unless intended.

#Quest start

1. Create a quest resource.
2. Create an NPC dialogue.
3. Add logic: Talk to NPC → Start quest → Show objective → Update quest log.
4. Validate quest references and rewards.

#Damage zone

1. Place an Area2D/Area3D or map danger region.
2. Add logic: Actor enters → Deal damage → Play effect.
3. Validate collision layers and test in Quick Play.

#UI Builder

UI Builder helps create menus, HUDs, and visual interface layouts. Use it for title screens, pause menus, feature list, dialogue boxes, health/mana/stamina bars, quest trackers, shop UI, settings screens, mobile layouts, and controller-friendly UI.

Basic workflow:

1. Choose the UI type or template.
2. Pick layout and theme settings.
3. Customize labels, icons, colors, sizing, and placement.
4. Connect UI elements to resources or game state where supported.
5. Preview the UI.
6. Save it as project content.
7. Add it to a scene and test.

Beginner task: create a simple HUD with health, currency/score, and one item/icon slot. Validate missing textures and test it in a small scene.

#Narrative Weaver

Narrative Weaver is for dialogue, branching stories, choices, quests, and story flow. Use it when your game needs conversations, story beats, NPC responses, affection/relationship changes, quest starts/completions, or cutscene-like dialogue sequences.

Beginner workflow:

1. Create a dialogue or chapter resource.
2. Add speaker names and lines.
3. Add a choice if needed.
4. Connect the dialogue to an NPC or map event.
5. Validate missing portraits, backgrounds, variables, or quest references.
6. Quick Play and test the conversation.

#Sound Studio and SFX

Sound Studio and SFX generation tools help create, preview, organize, and assign audio. Generated SFX/music outputs can be registered as generated assets with metadata and output paths.

Use audio assignments for cases such as UI confirm/cancel/click/error, chest open, door open, item pickup, quest start/complete, battle start/victory/defeat, enemy hit/death, player hit/death, skill cast, spell impact, map BGM, battle BGM, region BGM, and weather ambience.

v0.9.4 assignment reminder: audio assignments can store metadata and supported resource fields. Full runtime binding for every case is not guaranteed by v0.9.4 alone.

#VFX, Animation Studio, and Cinematic Editor

Use VFX for visual feedback, Animation Studio for sprite/skeletal animation authoring or preset work, and Cinematic Editor for cutscenes, camera moves, event timing, dialogue beats, audio timing, and scene transitions.

Beginner cinematic task:

1. Start a scene.
2. Move or focus the camera on an NPC/object.
3. Show dialogue.
4. Play a sound or VFX.
5. Return control to the player.
6. Validate missing audio/VFX/dialogue references.

#Procedural Toolkit

Procedural Toolkit is the broad generation workspace for sprites, palettes, maps, audio, VFX, and related generated content. Use it when you want Dreamcatcher to create starting material that can later be inspected, saved, validated, and reused.

Recommended workflow: generate a small result, inspect the preview/report, save into res://dream/generated/, register it in Generated Asset Browser, validate it, then assign or reuse it only after checking output quality.

#Asset Pipeline and converters

Asset Pipeline processes external and generated assets into project content. Converters can produce converted images/audio and related generated asset records where supported.

Use this area when you want to import, convert, slice, stitch, export, or prepare external files. Keep asset-rights rules in mind: only import files you created, own, or are licensed to use.

#Gameplay Director

Gameplay Director helps configure gameplay rules, pacing, and director logic. It is useful for enemy packs, loot tables, quest chains, items/gear generation, difficulty pacing, and genre-specific gameplay scaffolding.

Beginner task: in an Action RPG test project, generate or create one enemy, one loot table, one item, and one simple quest, then validate all references before using them in a scene.

#Ideation Board

Ideation Board is for planning. Use it to organize ideas, references, game design notes, mechanics, tasks, and concept directions before building. For beginners, it is a safe place to decide the first playable loop before opening complex tools.

#AI Dream Advisor

AI Dream Advisor provides guided answers about Dreamcatcher tools, DNA profiles, and workflows. Treat it as a helper for navigation and planning, not as a guarantee that a feature is complete or validated. Always check Content Validator and actual project behavior.

#Content Validator and generated asset validation

Validation helps find missing references, incomplete resources, unsafe paths, broken generated assets, map issues, and export-preflight problems before they become harder to debug.

Common validation categories:

• Missing scene reference.
• Missing icon/audio/VFX/texture.
• Missing generated asset metadata.
• Invalid or duplicate resource ID.
• Map event missing target.
• Quest missing reward/objective/reference.
• Shop missing item resource.
• Export template missing.
• Unsupported platform assumption.
• Asset path inside plugin folder.
• Orphan/stale generated asset registry record.

Warnings do not always mean the content is unusable. They mean you should inspect and decide whether the warning matters. Errors usually require fixing before relying on the result.

#Performance Panel

Performance Panel is for inspecting runtime performance and budgets. Use it after a prototype becomes larger, when maps feel slow, when many generated assets are loaded, or when UI/audio/VFX systems become heavy.

Beginner rule: do not optimize before you have a playable scene. Intermediate rule: if Quick Play feels slow, validate content, clean unused assets, and inspect performance before adding more systems.

#Module Manager and missing features

Dreamcatcher has 50 module IDs, and autoload/custom-type registration is gated by module state. This matters because users may think a node or feature is missing when its module is disabled.

Use Module Manager when:

• A tool or node is missing.
• A Genre DNA profile does not expose expected systems.
• You want a smaller/minimal project setup.
• You are troubleshooting plugin load behavior.
• You need to validate the module registry.

Advanced setting: dreamcatcher/advanced/no_autoload_mode skips autoload registration. Most users should leave it off. If it is enabled, runtime systems that depend on autoloads may not be available.

#Migration Assistant

Migration Assistant helps upgrade older project or save data to current schemas. Use it when opening older Dreamcatcher projects, after plugin updates, or when validation reports schema/version problems.

Before migration: back up your project. After migration: run Content Validator, open affected scenes/resources, and test with Quick Play.

#Bake Manager and Exit Ladder

Bake Manager helps bake/export project resources and data tables. The Exit Ladder / no-lock-in idea means users should understand how their work lives as Godot project content and how much of it can remain useful outside active editor workflows.

Use Bake Manager when you want to prepare resources for export, freeze generated data into project-owned files, or reduce dependence on live generation workflows. Validate after baking.

#Asset Cleaner

Asset Cleaner helps find unused or orphaned assets. Use it after heavy generation sessions, after deleting experiments, or before release/export preparation.

Safety rule: review before deleting. Registry records can sometimes be removed while output files remain project-owned. Existing target-resource assignment writes may also remain after a registry record is removed.

#Export Manager and export preflight ?

Export Manager helps configure export presets and prepare builds using Godot’s standard export workflow. Export Preflight helps find missing templates, missing files, configuration warnings, and platform-specific preparation issues.

What to expect:

Export Manager and Export Preflight help you prepare for Godot’s standard export workflow. Some platforms require Godot export templates, external SDKs, platform accounts, or platform-holder approval. Dreamcatcher does not guarantee turnkey console export.

#Export Preflight does not replace Godot export requirements

Export Manager and Export Preflight help you prepare your project. They do not remove the need for Godot export templates, platform SDKs, platform accounts, mobile signing setup, console platform-holder approval, or testing the exported build.

Preflight checklist:

• Run Content Validator.
• Run Generated Asset validation.
• Check scenes used by the project.
• Check missing textures/audio/resources.
• Check export templates.
• Check platform-specific settings.
• Export a test build if possible.
• Test the exported build, not only the editor playtest.

#Example project scenarios

These scenarios are the learning spine of the documentation. Follow them in order when learning Dreamcatcher for the first time. Each scenario builds a small playable loop before adding more complexity.

#First day learning plan

#Scenario A: Absolute beginner first scene

#Scenario B: 2D Platformer vertical slice

#Scenario C: Action RPG quest loop

#Scenario D: Visual Novel route

#Scenario E: Generated dungeon RPG prototype

#Scenario F: Advanced hybrid game from scratch to preflight

#Scenario G: Existing project adoption

1. Back up the whole project folder.
2. Open the copy, not the original.
3. Install and enable Dreamcatcher.
4. Do not move existing files yet.
5. Create one separate Dreamcatcher test scene.
6. Run Content Validator and read warnings before applying fixes.
7. Adopt tools gradually: Scene Composer, Visual Logic, Generated Asset Browser, then other systems.

#Scenario H: First map-based RPG room

1. Choose Universal or Action RPG DNA.
2. Open Map Editor and create a small map, such as 10×10.
3. Assign a user-owned tileset or placeholder TileSet.
4. Paint ground first, then walls.
5. Place player spawn in a safe tile.
6. Place one NPC or sign and one chest.
7. Add one exit door or transfer trigger.
8. Validate and Quick Play.

#Scenario I: First HUD from zero

1. Decide one value to show: score, coins, HP, or quest text.
2. Open UI Builder and choose a HUD layout.
3. Add a Label or Resource Counter.
4. Name it clearly, such as ScoreLabel or CoinCounter.
5. Preview the UI.
6. Save/export as a .tscn UI scene.
7. Instance it in the playable scene.
8. First show static text; connect dynamic values later.

#Scenario J: First Visual Logic graph from zero

1. Open Visual Logic.
2. Create a new graph or sequence.
3. Add a start/event node.
4. Add one action node, such as show dialogue, show notification, or print message.
5. Connect the execution wire.
6. Save the graph as a .dcs file.
7. Select a scene object or map event.
8. Attach the graph through DreamBehavior or the event editor.
9. Validate and Quick Play.

#Micro-tutorials for common first tasks

#Starter path for every featured tool

This table gives the first safe action for each of the 24 featured tools. Use it when a beginner asks, “Where do I click first?” Exact button labels can vary slightly between Godot 4.7 stable and Godot 4.6.3.

#The 24 featured tools reference ?

Tip: hover or focus the help markers and table rows for short explanations.

These are the canonical featured tools from the v0.9.4 tool catalog. The Welcome / Setup Wizard is onboarding and is not counted as a featured tool. Each tool below now includes a concrete first task so users do not face a feature dump.

#Almanac

Status: Stable
Category: Creation
Use it when: your central hub for Dreamcatcher navigation, content, and project knowledge.

#First task

Open Almanac, locate Scene Composer, Database, Generated Asset Browser, and Content Validator.

#Inputs

A Godot project with Dreamcatcher enabled.

#Outputs

Navigation context, database access, and links into creation/validation tools.

#How it connects

Usually comes before choosing a tool; use it to return to the main workflow.

#Common mistakes

Opening every tool at once; treating reference pages as tutorials; ignoring validation links.

#Validation

Confirm you can find Scene Composer, Database, Generated Asset Browser, and Content Validator.

#Visual Logic

Status: Stable
Category: Creation
Use it when: you need no-code gameplay behavior.

#First task

Create an NPC interaction: player interacts → show dialogue.

#Inputs

A scene with an NPC/object and optional dialogue resource.

#Outputs

A saved interaction/sequence that can be tested in Quick Play.

#How it connects

Often follows Scene Composer or Map Editor and connects to Database/Narrative Weaver.

#Common mistakes

No trigger assigned; missing target resource; forgetting to save/test; collision layer mismatch.

#Validation

Run Quick Play and confirm the trigger fires once and produces visible feedback.

#Scene Composer

Status: Stable
Category: Creation
Use it when: you want a starter scene instead of an empty scene tree.

#First task

Create one Platformer or Action RPG starter scene and save it.

#Inputs

Enabled plugin and selected Genre DNA.

#Outputs

A saved scene or template-derived scene inside your project.

#How it connects

Usually comes after Genre DNA and before Visual Logic, UI, and validation.

#Common mistakes

Confusing .tscn file counts with template entries; editing template source instead of saved scene.

#Validation

Open the saved scene, run validator, and verify it can be played or inspected.

#UI Builder

Status: Stable
Category: Creation
Use it when: you need HUDs, menus, feature list screens, or interface layouts.

#First task

Create a simple HUD with health, score/currency, and one icon slot.

#Inputs

A scene or game state concept that needs display.

#Outputs

A UI scene/layout or configured interface elements.

#How it connects

Often follows Database/Generated Asset Browser and is tested through Quick Play.

#Common mistakes

Unreadable scaling; missing icons; untested controller/mobile layout.

#Validation

Preview and Quick Play the UI; validate missing textures or references.

#Narrative Weaver

Status: Stable
Category: Creation
Use it when: you need dialogue, choices, branches, chapters, or quest story flow.

#First task

Create a two-line NPC dialogue with one choice.

#Inputs

NPC/story idea, optional portraits/backgrounds, optional quest resource.

#Outputs

Dialogue/chapter/choice resources and story flow links.

#How it connects

Connects to Visual Logic, UI Builder, Database, and map events.

#Common mistakes

Choice branches with no destination; missing portraits; dialogue not connected to NPC.

#Validation

Quick Play conversation and confirm choice results and references.

#Map Editor

Status: Stable
Category: Creation
Use it when: you need maps, TileMapLayer workflows, events, or gameplay regions.

#First task

Create or open a small map, add one event, and paint one region.

#Inputs

A map scene, tileset, or generated map output.

#Outputs

Map layers, events, and region metadata.

#How it connects

Connects to Generated Asset Browser, Database, Visual Logic, and Content Validator.

#Common mistakes

Painting on wrong layer; missing event target; region has no behavior; invalid tileset rights.

#Validation

Validate map structure and test the event/region in Quick Play.

#Animation Studio

Status: Stable
Category: Creation
Use it when: you need sprite/skeletal animation previews or presets.

#First task

Import or select a sprite/animation preset and preview idle/walk.

#Inputs

Sprite or character visual asset.

#Outputs

Animation data/preset or configured animation resource.

#How it connects

Usually connects to actors, UI, VFX, or cinematics.

#Common mistakes

Wrong frame size; missing animation names; no preview before assignment.

#Validation

Preview animation and validate references before assigning to gameplay.

#Sound Studio

Status: Stable
Category: Creation
Use it when: you need SFX, loops, music, or audio feedback.

#First task

Generate or select one SFX and assign metadata to a chest/open action.

#Inputs

A sound need, action/event, or generated audio preset.

#Outputs

Music/SFX output, metadata, or resource assignment.

#How it connects

Connects to Generated Asset Browser, Visual Logic, map regions, and UI.

#Common mistakes

Assuming metadata assignment guarantees runtime behavior; missing output path; volume too loud.

#Validation

Preview audio, validate references, and test the interaction that should play it.

#Cinematic Editor

Status: Stable
Category: Creation
Use it when: you need cutscenes, camera moves, timed events, or presentation beats.

#First task

Create a small intro moment: camera focus → dialogue → return control.

#Inputs

A scene, camera, target object/NPC, and optional dialogue/audio.

#Outputs

Cinematic sequence/timing setup.

#How it connects

Connects to Narrative Weaver, Sound Studio, Animation Studio, and Visual Logic.

#Common mistakes

No return-to-control step; missing camera target; unvalidated dialogue/audio.

#Validation

Quick Play the sequence and confirm control returns properly.

#Sketch Enhancer

Status: Beta
Category: Asset
Use it when: you want to clean rough sketches into usable visual assets.

#First task

Import a sketch, produce a cleaned output, save it as a generated visual asset.

#Inputs

A user-owned sketch or licensed image.

#Outputs

Cleaned image output and/or generated asset record.

#How it connects

Connects to Asset Pipeline and Generated Asset Browser.

#Common mistakes

Using unlicensed art; expecting finished production art without review; saving into plugin folder.

#Validation

Check asset rights, preview output, and validate path/metadata.

#Gameplay Director

Status: Stable
Category: Creation
Use it when: you want enemy/loot/quest pacing or gameplay rule scaffolding.

#First task

Create one enemy, loot table, and basic encounter pacing setup.

#Inputs

A genre direction, simple game loop, and optional resources.

#Outputs

Gameplay pacing/rule configuration and related data.

#How it connects

Connects to Database, Visual Logic, Map Editor, and Content Validator.

#Common mistakes

Building too much before first loop works; missing reward/enemy references.

#Validation

Validate all enemy, loot, quest, and encounter references.

#Ideation Board

Status: Stable
Category: Creation
Use it when: you need to plan a game loop before building.

#First task

Define your first playable loop in 5 cards: player, goal, obstacle, reward, test.

#Inputs

A rough game idea.

#Outputs

Planning cards/notes that guide your first prototype.

#How it connects

Comes before Scene Composer and helps avoid feature overload.

#Common mistakes

Planning huge scope; never converting cards into a small playable test.

#Validation

Check that the board defines one small testable loop.

#Procedural Toolkit

Status: Stable
Category: Asset
Use it when: you want to generate maps, sprites, palettes, audio, VFX, or helper content.

#First task

Generate a small dungeon/map/icon/palette and register it.

#Inputs

A generation goal and safe project output folder.

#Outputs

Generated output, registry record, metadata/report where supported.

#How it connects

Feeds Generated Asset Browser, Map Editor, Database, Sound Studio, and validation.

#Common mistakes

Generating many tests without naming/validating; ignoring reports; overwriting useful outputs.

#Validation

Inspect record, preview/report, output path, and validation status.

#Generated Asset Browser

Status: Stable
Category: Asset
Use it when: you need to inspect, filter, validate, duplicate, assign, delete, or regenerate generated outputs.

#First task

Filter assets, inspect metadata, validate, duplicate, assign, and delete one test asset.

#Inputs

At least one generated or registered asset.

#Outputs

Managed asset records, assignments, duplicates, deletion decisions, or regeneration actions.

#How it connects

Sits after any generator and before assignment/cleanup/export.

#Common mistakes

Deleting without review; expecting every type to regenerate; confusing metadata-only assignments.

#Validation

Validate record, check output path, and test assigned content.

#AI Dream Advisor

Status: Stable
Category: System
Use it when: you need guidance about tools, DNA profiles, or workflows.

#First task

Ask which tools to use for your chosen genre, then verify advice with docs/validator.

#Inputs

A question or game goal.

#Outputs

Guidance and suggested next steps.

#How it connects

Use it with the docs; verify all advice with Content Validator and real tests.

#Common mistakes

Treating suggestions as proof that a feature works; skipping validation.

#Validation

Cross-check suggested workflow against the relevant manual section and validator.

#Database

Status: Stable
Category: Creation
Use it when: you need items, enemies, quests, shops, skills, actors, cards, or other data.

#First task

Create an item resource and assign an icon if available.

#Inputs

A data category and required fields such as name/ID.

#Outputs

Godot resource files and related data records.

#How it connects

Connects to Generated Asset Browser, Visual Logic, Gameplay Director, and UI.

#Common mistakes

Duplicate IDs; missing icons/rewards; broken resource paths.

#Validation

Run Content Validator and confirm references resolve.

#Content Validator

Status: Stable
Category: Validation
Use it when: you need to catch missing references and readiness problems.

#First task

Run validation on a test scene and fix one warning.

#Inputs

A scene, map, resource, or project to inspect.

#Outputs

Warnings/errors and readiness reports.

#How it connects

Use before Quick Play/export and before asking for support.

#Common mistakes

Ignoring warnings; misunderstanding warning vs error; validating before saving.

#Validation

Rerun after fixes and confirm warnings/errors changed as expected.

#Asset Pipeline

Status: Stable
Category: Asset
Use it when: you need to import/process user-owned or generated assets into project content.

#First task

Import a user-owned image/audio asset and prepare it as project content.

#Inputs

A file you created, own, or are licensed to use.

#Outputs

Processed/imported project asset and metadata.

#How it connects

Connects to converters, Generated Asset Browser, UI/Audio/VFX workflows.

#Common mistakes

Importing unlicensed assets; saving into addon folder; skipping preview.

#Validation

Validate path, rights, file type, and assignment target.

#Performance Panel

Status: Stable
Category: System
Use it when: you need to inspect runtime performance and budgets.

#First task

Open the panel during Quick Play and note FPS/budget warnings.

#Inputs

A running scene or test build.

#Outputs

Performance readings and budget warnings.

#How it connects

Use after a prototype exists, especially before export preflight.

#Common mistakes

Optimizing before gameplay works; ignoring generated asset load costs.

#Validation

Compare readings before/after changes and test in exported build if possible.

#Module Manager

Status: Stable
Category: System
Use it when: a tool/node/profile appears missing or you need module control.

#First task

Check whether a missing node/tool is disabled by module state.

#Inputs

Enabled plugin and module registry.

#Outputs

Module state information and registry validation.

#How it connects

Use with troubleshooting and advanced project setup.

#Common mistakes

Changing modules randomly; enabling no-autoload mode accidentally.

#Validation

Confirm module state matches expected visible tools/custom types.

#Migration Assistant

Status: Stable
Category: System
Use it when: you are opening older Dreamcatcher projects or schemas.

#First task

Back up, run migration check, then validate older resources.

#Inputs

A backed-up older project/resource set.

#Outputs

Migration report and updated resources where supported.

#How it connects

Use before editing old projects heavily.

#Common mistakes

Migrating without backup; skipping validation after migration.

#Validation

Open affected scenes/resources and run Content Validator.

#Bake Manager

Status: Stable
Category: Asset
Use it when: you need to bake/export resources or data tables.

#First task

Bake/export project data tables or resources, then validate outputs.

#Inputs

Project resources ready for baking.

#Outputs

Baked/exported data files or resources.

#How it connects

Comes after validation and before export preparation.

#Common mistakes

Baking broken data; not checking output paths; assuming bake fixes references.

#Validation

Validate before and after baking; inspect output files.

#Asset Cleaner

Status: Stable
Category: Asset
Use it when: you need to review unused/orphaned assets after experiments.

#First task

Find unused generated test assets and review before deletion.

#Inputs

A project with generated/imported experiments and a backup.

#Outputs

Cleanup candidates and deletion decisions.

#How it connects

Use with Generated Asset Browser and Content Validator.

#Common mistakes

Deleting without backup; deleting outputs still referenced by scenes/resources.

#Validation

Review references and rerun Content Validator after cleanup.

#Export Manager

Status: Stable
Category: System
Use it when: you are preparing Godot export presets and preflight checks.

#First task

Run export preflight, check templates, and build only after validation.

#Inputs

Validated project and target platform decision.

#Outputs

Export presets, preflight results, and build preparation.

#How it connects

Comes after Content Validator, Asset Cleaner, Bake Manager as needed.

#Common mistakes

Assuming console/mobile export is turnkey; missing templates/SDKs/signing.

#Validation

Install required Godot templates/SDKs and test exported build.

#Resource reference: 47 data/resource scripts

These are the current scripts under addons/dreamcatcher/resources/. Most extend Resource; DreamMapEvent extends Node2D and should be explained as a map-event object/data-runtime bridge rather than as a plain data resource.

#Resource family map

Safe file rule: keep project-owned game data under your project folders such as res://dream/. Avoid editing or saving your own content inside res://addons/dreamcatcher/.

Common user-facing groups:

• Actors/combat/RPG: DreamActorData, DreamClass, DreamEnemy, DreamWeapon, DreamArmor, DreamSkill, DreamTroop, DreamState, DreamPerkData.
• Inventory/economy: DreamItem, DreamShop, DreamLootTable, DreamRecipe.
• Narrative/quests: DreamDialogue, DreamChapter, DreamQuest.
• Cards/board/puzzle/rhythm/sports/racing: DreamCard, DreamDeck, DreamBoardPath, DreamPuzzle, DreamRhythmChart, DreamSportConfig, DreamRaceConfig.
• Generated asset system: DreamGeneratedAsset, DreamGeneratedAssetMetadata, DreamGeneratedAssetPreview, DreamGenerationPreset, DreamGenerationReport.
• Maps/tiles/regions: DreamTilesetData, DreamMapEvent, DreamMapEventPage, DreamMapEventCondition, DreamMapRegionData, DreamRegionBehavior, DreamGrid, DreamEnvironment.
• Creature collector: DreamCreatureSpecies, DreamCreatureInstance, DreamCreatureRoster, DreamCaptureRule.

#Autoload services ?

In Godot, an autoload is a script or scene that Godot loads automatically when the project starts. It behaves like a global service. Dreamcatcher uses autoloads for shared runtime systems such as audio, input, scene flow, dialogue, weather, accessibility, screen effects, and event messaging.

Most users do not edit these scripts directly. You normally use Dreamcatcher tools, custom nodes, resources, and Inspector fields; the autoloads support those workflows behind the scenes.

#Autoloads at a glance

#Safe autoload troubleshooting

1. Confirm Dreamcatcher is enabled in Project Settings → Plugins.
2. Confirm the module that owns the feature is enabled.
3. Check Project Settings → Autoload to verify presence, not to edit plugin scripts.
4. Check the Godot Output panel for missing singleton, missing resource, or missing method messages.
5. Check the scene node, resource, tool, and Inspector configuration before changing plugin files.
6. Run Content Validator or the relevant map/generated-asset validator.
7. In existing projects, check whether another autoload or manager conflicts with the same role.
8. Only advanced users should change autoload mode or plugin files, and only after backing up the project.

#Custom node type overview

Dreamcatcher v0.9.4 registers 113 custom node types when their modules are enabled. These are visible Godot custom types, not all necessarily beginner-facing tools. They are grouped by module below so users can understand why a node may appear or disappear when modules are enabled/disabled.

#Which custom nodes should beginners use first?

Why this matters: custom nodes are powerful because they sit inside real Godot scenes. A missing node usually means a disabled module, a plugin registration issue, or a project that needs a restart after enabling the plugin.

#Module: actors

#Module: ai_director

#Module: combat

#Module: dialogue

#Module: director

#Module: genre_autobattler

#Module: genre_battleroyale

#Module: genre_cards

#Module: genre_farm

#Module: genre_fighting

#Module: genre_hackslash

#Module: genre_horror

#Module: genre_idle

#Module: genre_moba

#Module: genre_procedural

#Module: genre_puzzle

#Module: genre_racing

#Module: genre_rhythm

#Module: genre_roguelike

#Module: genre_runner

#Module: genre_shmup

#Module: genre_simulation

#Module: genre_sports

#Module: genre_stealth

#Module: genre_survival

#Module: genre_td

#Module: genre_vn

#Module: input

#Module: networking

#Module: rpg

#Module: ui

#Module: weapon_aim

#Module: world

#Module ID reference

These module IDs are the names Dreamcatcher uses for its major feature groups. In the Module Manager, they help you understand which systems belong together and which groups can be enabled or disabled for a project.

#Localization and translated editor strings

Dreamcatcher includes translation resources for several editor/plugin strings. Current package files include Arabic, German, English, Spanish, French, Italian, Japanese, Korean, Portuguese, Russian, and Chinese .translation resources, plus the source CSV.

These files support plugin/editor localization surfaces where wired. They do not automatically translate your game content. For your own game text, manage dialogue, UI labels, and localization resources inside your project and validate missing text references where applicable.

#Other documents included with the plugin

#What beginners should not touch yet

Until your first playable scene works, avoid:

• Editing files inside addons/dreamcatcher/.
• Changing module settings randomly.
• Enabling no-autoload mode.
• Using Asset Cleaner without a backup.
• Baking/exporting before validation.
• Importing third-party assets without license checks.
• Building a large hybrid game before testing one small loop.

#Common validation messages and fixes

#Genre starter workflows

Every genre starter workflow helps you build a first playable loop instead of only describing the genre. Stable profiles can be treated as normal v0.9.4 workflows; Beta and Early Access foundation profiles should be validated more carefully.

#Universal

Status: All systems
Best for: All genre systems visible for custom or hybrid projects.

#First playable loop

Create a small scene with one actor, one object, one interaction, one generated asset, and one validation pass.

#Use these tools first

Almanac, Scene Composer, Generated Asset Browser, Content Validator, Quick Play.

#Create these resources first

One scene, one actor/object, one interaction, optional generated asset.

#Validation gate

Scene opens, interaction works, generated asset path is known, validator output is understood.

#Advanced path

Choose a specific DNA once your direction becomes clear.

#Platformer

Status: Stable
Best for: Jump/dash, camera follow, checkpoint and respawn workflows.

#First playable loop

Move, jump, collect a pickup, reach an exit, and respawn from a checkpoint.

#Use these tools first

Scene Composer, Visual Logic, Map Editor, UI Builder, Content Validator.

#Create these resources first

Player actor, pickup, hazard, checkpoint, exit trigger.

#Validation gate

Player spawns, collision works, pickup feedback appears, checkpoint/exit work.

#Advanced path

Add enemies, hazards, camera tuning, and level regions.

#Action RPG

Status: Stable
Best for: Crit/parry/status, slow-motion and loot workflows.

#First playable loop

Talk to an NPC, accept a quest, defeat an enemy, collect loot, and receive a reward.

#Use these tools first

Database, Scene Composer, Map Editor, Visual Logic, Gameplay Director, Generated Asset Browser.

#Create these resources first

Player actor, NPC, enemy, item, quest, dialogue, loot table.

#Validation gate

Quest starts/completes, enemy/reward references resolve, loot works.

#Advanced path

Add equipment, skills, shops, dungeons, bosses, and status effects.

#Visual Novel

Status: Stable
Best for: CG/affection, dynamic choices, portraits and typewriter text.

#First playable loop

Show a scene, display dialogue, present a choice, change a variable, and branch to a result.

#Use these tools first

Narrative Weaver, UI Builder, Visual Logic, Sound Studio, Content Validator.

#Create these resources first

Dialogue/chapter, characters, choice variable, optional portraits/backgrounds/audio.

#Validation gate

Choice branches correctly and missing visual/audio references are intentional or fixed.

#Advanced path

Add routes, affection variables, chapters, endings, and audio cues.

#Card Battler

Status: Stable
Best for: Draw/play/shuffle and card battle management.

#First playable loop

Draw 5 cards, play one attack card, enemy loses HP, then discard/end turn.

#Use these tools first

Database, Visual Logic, UI Builder, Scene Composer, Content Validator.

#Create these resources first

Cards, deck, enemy/target, battle UI, damage rule.

#Validation gate

Card can be drawn/played, HP changes, turn ends cleanly.