-
Notifications
You must be signed in to change notification settings - Fork 2
Home
Alex Calderwood edited this page Dec 6, 2023
·
3 revisions
- Skeleton the threads:
- In the miro board, create a frame for the thread and label it with the thread number.
- Create sticky notes within this frame for each choice that a player is able to make. These represent the fragments.
- Ensure that connecting arrows map out the branching choices
- Ensure that arrows connect to other threads to communicate where the thread switching happens
- Author the thread
- Open up the Google spreadsheet. Place the text from sticky notes on the miro board under the notes column to dictate which fragment is equivalent to the skeleton
- Create IDs for each fragment (row) in the spreadsheet.
- Enter the GoToChoices as comma-separated fragment IDs in the appropriate column.
- Write content in the “content” column
- Write the choice label in the correct column
- Ensure that the pre/post conditions are correct
- Render the thread text into Step code using the utility script in
StoryAssemblerRedux/Utilities/frag_creator/
. This will copy the Step episode into the Unity project. - Playtest the game in Unity
- Take of narrative discontinuities
- Play other writers' threads as well
- Revise, rewrite, edit, repeat