Add narrative text for intro & outro

[jgbourque]

Why this task matters

This is where your story comes alive. The intro and outro narrative helps your player understand the journey and its emotional stakes.

Steps

Git Setup

1. Update your local repository. Open Git Bash and navigate to your project folder. Before creating a new branch, switch back to the main branch and pull the latest changes from your team's GitHub repository. This makes sure that the new branch you are about to create will have the latest updates from your team's StoryQuest.

   git switch main
   git pull

2. Create a new Git branch
   Now, create a new branch for your work:

   git switch -c new-branch-name

   In general, choose a branch name that reflects what you're doing, like intro-outro-tilemap or add-custom-path. This keeps your work organized. Click here for a more detailed guide and more information on updating your local repository and creating a branch.

---

3. Open your custom intro scene in Godot. In the FileSystem (bottom left), navigate to your StoryQuest intro scene, for example: res://scenes/quests/story_quests/stella/stella_intro/. Double-click the .tscn file for your intro scene (e.g., stella_intro.tscn).
4. Edit your dialogue file. In the same folder, find the dialogue file (e.g., stella_intro.dialogue). Double-click to open it. Replace the lines of placeholder text with your custom text. You can copy and paste the narrative text from your GDD.
5. Link your dialogue file. Even if your dialogue file sits right next to your scene file in the FileSystem, Godot doesn’t automatically know they belong together, you have to link them manually in the scene:

• While looking at the intro scene, in the Scene Tree (top left, list of nodes for the scene), click on the Cinematic node, this is the part of your scene that controls how dialogue plays.
• Look at the Inspector on the right. Find the property labeled Dialogue. It might still be linked to an older file.
• Drag your edited dialogue file (the one you just changed) from the FileSystem into this Dialogue field.
• You should now see your dialogue file’s name listed there.

7. Repeat for outro. Repeat the above steps for the outro scene.
8. Save your changes. Preview your changes by playing the scene. Then, use Scene → Save All Scenes.

---

Save To Git and GitHub

9. Stage and commit your changes. In Git Bash, here is an example of how this flow will generally look:

   git status
   git add scenes/quests/story_quests/yourStoryQuest/
   git commit -m "Add your message here - explain to your team what you changed"
   git push --set-upstream origin your-branch-name

• Make sure the file path shows your actual story quest name, write your own descriptive commit message, and use your actual branch name.
• You can use git add to add more than one file simply by putting a space between file paths you paste in.
• You only need to use --set-upstream the first time you push a new branch to GitHub.
  Click here for a more detailed guide and more information on saving and pushing your changes to GitHub.

10. Submit a pull request. Go to GitHub, navigate to your fork, and click Compare & pull request. Write a clear title and description indicating what you changed and why, then click Create pull request.
    Click here for a more detailed guide and more information on creating a pull request to your team's forked repo.

Note: Pull requests are better with a peer review! Click here to learn more. If you are working alone, you can merge your own pull request after submitting it.
✅ Done! This ensures your edited dialogue file is actually used when the game plays.

Video