Red Flags

You’re a grad student burdened with debt, and in a desperate attempt to keep the lights on, you opt for an unconventional method: going on dinner dates with rich men who will cover the check. The men, however, are some of the most outlandish playboys out there. And the only way to get what you want is to match their level of weirdness. So, throw on a nice outfit, fake a semi-convincing smile, and get ready to redefine “freaky” romance.

• Developed in Unity & C#
• Coded in Visual Studio Code
• Version Controlled through GitHub
• Implemented dialogue through YarnSpinner

Programming

Highlights from her role as Gameplay Programmer:

Players make narrative-based decisions to charm the bachelor of the evening, Jeremy, into paying the bill. Nicole utilized YarnSpinner & C# to systematically create a conversational gameplay loop. See here for more information.

Project Management

Highlights from her role as Project Manager:

• Created and managed GitHub repository for the project.
• Recorded detailed and user-friendly documentation.
• Developed a keyword system for script updates between writers and developers.
• Organized meetings to develop project plans.

Nicole created and managed a repository for the project, which allowed her to sync her and her group members’ work over multiple computers.

She also frequently met one-on-one with each group member to sketch out a timeline of deliverables. See here for more information.

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.