GitHub

Nicole created and organized a GitHub repository that could do the following:

• Quickly and easily share files
• Track progress and maintain an organized workflow
• Periodically create stable builds of the game
• Systematically identify and fix errors, without corrupting said builds
• Develop comprehensive and user-friendly documentation

You can visit the official Murder at Supper repository here.

As discussed in the many pull requests on the repository, Nicole created several branches for each feature/stage of the project.

Examples:

• Development (dev)
• Inventory System (feat/inventory)
• Clues for Inventory (feat/clues)
• Documentation (docs)
• and more

Since not everyone in her group was familiar with GitHub, Nicole developed a comprehensive Guide to Getting Started, explaining the usage, terminology, and more.

Additionally, she carefully crafted very detailed descriptions in all of her commits and pull requests. This not only kept everyone up-to-date through the Discord, but also helped her keep track of her work.

As all game-lovers tend to do, Nicole created a Discord as a central hub of communication. More importantly, she setup a webhook between the repository and the server itself, allowing any updates to flow into a specific channel. These updates are automatically hyperlinked, making it quick and easy to stay up-to-date with the project.

From the kickoff of the Game Jam, Nicole created a GitHub repository that was shared with all the team members.

The benefits to this repo are similar to Murder at Supper:

• • Members could actively collaborate on the same project
  • Files could be accessed from one central location
  • Developers forked each others’ work for experimentation

Nicole’s GitHub skills have improved tremendously since Red Flags, which you can see in her work on Murder at Supper.

As discussed in the many pull requests on the repository, Nicole created several branches for each feature/stage of the project.

Examples:

• Development (dev)
• Inventory System (feat/inventory)
• Clues for Inventory (feat/clues)
• Documentation (docs)
• and more

Like a few other games, Nicole and her group utilized YarnSpinner to set up a simple dialogue system. However, with the continuously branching storylines, the script got a bit confusing.

Nicole devised a keyword system in which writers could go through the script and leave a code comment with a keyword that (A) does not appear in the script, and (B) is not a recognized programming term.

For instance, when changing the expression of the player’s date (Jeremy), the writers used the keyword “ALBATROSS” to indicate a needed update in the script.

Additionally, she carefully crafted very detailed descriptions in all of her commits and pull requests. This not only kept everyone up-to-date through the Discord, but also helped her keep track of her work.

Like a few other games, Nicole and her group utilized YarnSpinner to set up a simple dialogue system. However, with the continuously branching storylines, the script got a bit confusing.

Nicole devised a keyword system in which writers could go through the script and leave a code comment with a keyword that (A) does not appear in the script, and (B) is not a recognized programming term.

For instance, when changing the expression of the player’s date (Jeremy), the writers used the keyword “ALBATROSS” to indicate a needed update in the script.

Additionally, she carefully crafted very detailed descriptions in all of her commits and pull requests. This not only kept everyone up-to-date through the Discord, but also helped her keep track of her work.