Today we are moving from planning into building. Our goal is to leave class with a shared direction, real work started by every group, and everyone comfortable with our tools.
We will briefly review all five role pages together so everyone understands what each group is responsible for and how the teams fit together. While we do this, storytellers will be working independently on their tasks.
Once storytellers are ready, we will review the submitted pitches anonymously and vote as a class to choose the final story direction for our game. This decision will guide all work for the rest of the session.
We will review the class GitHub repository together.
We will use the browser-based GitHub interface for now to make uploading easier.
You will see where different types of work live (art, audio, scripts, data).
Everyone is encouraged to upload completed work to the repo and ask for help if needed.
We will move to the shared draw.io brainstorming board.
Each group has its own shape or area to add ideas and list priorities.
Groups should think about features, order of work, and what needs to happen first.
This board is for brainstorming and communication, not final decisions.
Next class, we will introduce separate kanban-style boards for each group and a game-wide kanban board that project managers will use for planning and tracking progress.
Decide on the final game title.
Write the complete intro story text that will appear at the start of the game.
Focus on tone and clarity rather than long lore.
Upload the intro text to the docs folder in the repository when finished.
Learn how to use your tool, find tutorials or videos as needed.
Decide on a color palette for the game or create one: https://lospec.com/
Save as .png, use color dropper tool to add color pallet to your app/software/webapp of choice. Save .png to github repo so you don't lose it/easy download if you do.
Begin work on the main playable character design.
If time allows, start sketching or creating additional assets.
Upload palette references and any finished art to the repository.
Learn how to use your tool, find tutorials or videos as needed.
Begin creating an intro or title theme that fits the chosen story.
Create at least one sound effect.
Sounds do not need to be final. Drafts and placeholders are encouraged.
Upload audio files to the repository when ready.
Explore the Godot project and existing scenes.
Make small changes in areas marked as safe to edit to observe cause and effect.
Test movement, camera behavior, and scene flow.
Note questions or ideas for future systems.
Help groups stay focused and moving forward.
Note what still needs to be done next.
Check in with teammates and get the teacher if help is needed.
We will do a brief check-in to confirm progress and next steps.
Everyone should make sure completed work is uploaded or saved and that questions are written down for next class.