Project_Exodus

Table of Contents

1. Description
2. Elevator Pitch
3. User Story
4. Team
5. Acceptance Criteria
6. Credits
7. Issues and Resolutions
8. Future Development
9. Wireframe
10. Link
11. Screenshot

Description

Exodus is a choose-your-own-adventure application, taking the retro game concept and giving it a sleek, refined front end experience. This group project utilizes sequelize, express, handlebars, mySQL, Bootstrap as well as multiple css libraries.

Upon accessing the application the user will be presented with a flickering title, and upon clicking it they will be brought into the game. Finding themselves trapped in a scene straight from a horror movie, the user will be given a series of prompts about what is going on and options about how they can interact. The goal for the user is to escape the house.

If the user fails in their attempt they will be brought back to the beginning of the game, with their failure being recorded in the local storage.

Upon successfully escaping the house the user will be allowed to record their name in the highscore table, which will take their recorded number of failed attempts and automatically post it alongside.

Elevator_Pitch

Retro is having a comeback. We see it in clothing, in film, in music, why not games? Team Undefined took this craze and applied it to our choose-your-own adventure game: EXODUS. Evoking memories of classic horror alongside a front-end design that is sleek in its simplicity, we built EXODUS to entertain and thrill the user as they attempt to escape a nightmarish imprisonment.

User_Story

As an end user I want to be able to navigate through the game, interacting with objects and characters, and have my failed attempts recorded. So that I can post my score when reaching the end.

Team

1. Front End
   • Wyatt Hancock and Jameson Midgley
2. Backend
   • Dilan Lee, Rajesh Baduwal and Sam Greilick
3. Story Builder

• Ammon Jeffery

Acceptance_Criteria

• GIVEN a choice of options when presented with a certain scenario.
• When the user chooses an option
• Then the user is either taken to the game over screen (where their failed attempt is recorded) or they are allowed to proceed.
• Given a view of the game over screen.
• When the user clicks "return to game"
• Then they will be brought back to the beginning of the game.
• When the user chooses the correct series of options
• Then they will successfully navigate through the game and be presented with the success screen.
• Given the success screen.
• When the user types their name into the highscore form.
• Then their name and the number of failed attempts in their run-through will be recorded in the database to be displayed.

Credits

• Aakhya Signh for creating the typewriter css and js effect:
  • Link To Codepen
• Prathamesh Koshti for creating the LIGHT flickering animation:
  • Link To Codepen
• Mateusz Rybczonec and Geoff Graham for creating the Timer Animation:
  • Link to Codepen
• Tremaine Eto for explaining how to create a fade in and out effect with css:
  • Link to Website
• Daniel Malkafly for creating the end credits scroll:
  • Link to GitHub
• Fesliyan Music for background music (Track Name: Monsters in the Field):
  • Link to Website
• Background Music: Unseen Horrors Kevin MacLeod (incompetech.com) Licensed under Creative Commons: By Attribution 3.0 License http://creativecommons.org/licenses/by/3.0/:
  • Link to Website
• Fesliyan Music for background music (Track Name: Monsters in the Field):
  • Link to Website
• freesoundeffects.com for the heartbeat effect:
  • Link to Website

Issues_And_Resolutions

• With the front end we had a lot of complicated css effects occuring at the same time on different objects or lines of text, and sometimes these effects could interfere with one another. In order to fix this we had to seperate a lot of the effects into seperate css files and only allow for the effects to be trigged in certain instances with javascript.
• Making sure the Continous Integration and Continous Deployment process was not interrupted with every commit was a big learning curve.Merging only the final and fully functional codes to the master branch was very critical to make sure CI is occuring smoothly.

Future_Development

• One thing that we'd like to accomplish with future iterations of this application is to expand out the house. Due to us only having two weeks to accomplish this project we focused on only five rooms to prove the concept. To flesh out the story we'd like to have over twenty rooms, situated in an upstairs, main floor, and basement.
• A couple features we'd like to add in the future are, an inventory system, and a health system with healing items.

Wireframe:

Link

Deployed Website

Screenshot