[{"data":1,"prerenderedAt":231},["ShallowReactive",2],{"doc-global_essentials\u002Fintroduction\u002Fgetting_started":3},{"id":4,"title":5,"body":6,"description":220,"extension":221,"meta":222,"navigation":226,"path":227,"seo":228,"stem":229,"__hash__":230},"docs\u002Fdocs\u002Fglobal_essentials\u002Fintroduction\u002Fgetting_started.md","Getting Started",{"type":7,"value":8,"toc":211},"minimark",[9,13,22,27,34,47,54,58,65,80,83,87,94,113,120,124,127,180,183],[10,11,5],"h1",{"id":12},"getting-started",[14,15,16,17,21],"p",{},"The fastest way to understand Dryad Engine is to ",[18,19,20],"strong",{},"play"," with it before you try to build anything.",[23,24,26],"h3",{"id":25},"_1-play-the-tutorial-game","1. Play the Tutorial Game",[14,28,29,30,33],{},"Dryad Engine comes with a ",[18,31,32],{},"Tutorial"," game that walks you through the core ideas:",[35,36,37,41,44],"ul",{},[38,39,40],"li",{},"Moving through dungeons and scenes",[38,42,43],{},"Interacting with choices, quests, and dialogue",[38,45,46],{},"Seeing characters, inventories, and UI in action",[14,48,49,50,53],{},"If you haven’t already, start by ",[18,51,52],{},"playing the Tutorial from beginning to end",".",[23,55,57],{"id":56},"_2-open-the-tutorial-in-the-editor","2. Open the Tutorial in the Editor",[14,59,60,61,64],{},"Once you’ve played it, the next step is to ",[18,62,63],{},"open the Tutorial game in the editor"," and see how it’s put together:",[35,66,67,70,73],{},[38,68,69],{},"Browse characters, items, stats, abilities, dungeons, and quests as data.",[38,71,72],{},"Click through different tabs to see how everything connects.",[38,74,75,76,79],{},"Notice how much of the game is defined through ",[18,77,78],{},"structured content",", not code.",[14,81,82],{},"You don’t have to understand every panel yet. The goal is just to see that the whole game lives in one place, and the editor understands it.",[23,84,86],{"id":85},"_3-the-game-editor-your-power-house","3. The Game Editor: Your Power House",[14,88,89,90,93],{},"The ",[18,91,92],{},"Game Editor"," is where you’ll spend most of your time:",[35,95,96,103,110],{},[38,97,98,99,102],{},"It manages ",[18,100,101],{},"all of your game data"," and how different systems connect.",[38,104,105,106,109],{},"You can create and tweak ",[18,107,108],{},"stats, abilities, item slots, characters, dungeons, quests, and more"," without writing code.",[38,111,112],{},"As your project grows, the editor keeps your content organized so you don’t get lost.",[14,114,115,116,119],{},"It’s completely possible to build a ",[18,117,118],{},"fully playable game"," by staying inside the editor the whole time.",[23,121,123],{"id":122},"_4-optional-where-else-you-might-work","4. Optional: Where Else You Might Work",[14,125,126],{},"While the editor can take you very far on its own, there are a few optional “extra power” tools you might want to use during development:",[35,128,129,142,159],{},[38,130,131,134],{},[18,132,133],{},"Google Docs (strongly recommended for story‑heavy games)",[35,135,136,139],{},[38,137,138],{},"Great for writing and reviewing long scenes, dialogue, and branching storylines.",[38,140,141],{},"You draft and iterate in Google Docs, then import the content into your game with a click of a button.",[38,143,144,147],{},[18,145,146],{},"Code editor (for advanced use cases)",[35,148,149,156],{},[38,150,151,152,155],{},"Used for writing ",[18,153,154],{},"custom JavaScript logic and CSS"," when you want to go beyond what the editor offers out of the box.",[38,157,158],{},"Ideal for special mechanics, unique UI widgets, or one‑off behaviors that are specific to your game.",[38,160,161,164],{},[18,162,163],{},"Community plugins",[35,165,166,173],{},[38,167,168,169,172],{},"Look for ",[18,170,171],{},"community‑made plugins and content packs"," to add or change data, logic, or UI without reinventing the wheel.",[38,174,175,176,179],{},"Dryad Engine is designed like ",[18,177,178],{},"Lego bricks"," – you can snap in new pieces, remove them, or mix and match them to create exactly the game you want.",[14,181,182],{},"Most devs will:",[35,184,185,195,204],{},[38,186,187,188,191,192,194],{},"Do ",[18,189,190],{},"structure and systems"," work in the ",[18,193,92],{},",",[38,196,187,197,200,201,194],{},[18,198,199],{},"writing"," in ",[18,202,203],{},"Google Docs",[38,205,206,207,210],{},"And only touch the ",[18,208,209],{},"code editor"," like VS Code when there's no plugins for it and they want to add a truly unique mechanic.",{"title":212,"searchDepth":213,"depth":213,"links":214},"",2,[215,217,218,219],{"id":25,"depth":216,"text":26},3,{"id":56,"depth":216,"text":57},{"id":85,"depth":216,"text":86},{"id":122,"depth":216,"text":123},"The fastest way to understand Dryad Engine is to play with it before you try to build anything.","md",{"plugin":223,"category":224,"page":225},"global_essentials","introduction","getting_started",true,"\u002Fdocs\u002Fglobal_essentials\u002Fintroduction\u002Fgetting_started",{"title":5,"description":220},"docs\u002Fglobal_essentials\u002Fintroduction\u002Fgetting_started","mue1_mPsNWNGI3mMFbidZMoMcZ4cRnlbl5s4NueZU6A",1779582260807]