Play Space Escape!

GitHub Repo!

1. Background
2. Technologies
3. Features
4. Installation
5. Instructions
6. License
7. Code
8. Authors
9. Credits

• Inspiration Excited to create game of some sort, our five person team (members of the UC Berkeley Extensions Full-Stack Bootcamp) felt motivated and confident to build a complex project that stretched our knowledge of ReactJS. The game we created takes inspiration from simplistic computer games of the past such as Oregon Trail and Mario Party, while also giving it a modern and comedic flare referencing popular culture surrounded by the theme of the modern day space race.

• Instructions Create an account, choose a character, and start playing! Each location contains an encounter in which you will make a user decision, or play a minigame.

• License This application is using the MIT license.

• Front-End

  • HTML
  • SCSS & CSS
  • Javascript (JSX)
  • Excalidraw
  • Local Storage
  • howler.js
  • Chart.js
  • anime.js
  • axios

• Back-End

  • Node.js
  • npm
  • Express
  • MySQL
  • Sequelize ORM
  • JWT

The game played by the user is, at high-level, a loop through various components handled by conditionally rendering those components. To illustrate, the drawing shows the component names and the loop that we create:

Within the game component, we import our global state variable which keeps track of the currently rendered component by saving a boolean associated with each component we want to render:

In each sub-component, we can dispatch actions to change which component is rendered based on the user's input. As an example of a simple component, the Story component contains a continue button

That continue triggers a call of dispatch with an action to render the prompt component which is inside the Encounter component. This code pattern is the general approach we take to rendering other components within the game component.

When presented with new encounters, the user can make a choice: one of those choices can lead them to a direct outcome, affecting their character stats or they can possibly choose an option that requires them to play a minigame. To create a game that matched our theme, we wanted something fairly complex but not something that would hinder our learning of ReactJS. We chose to use a tutorial on creating an asteroid game in static HTML, but then convert that into something we can integrate into a React app. The Collect Gold and Pelters minigames were based off of the same functions used in the asteroids game, but tweaked in a way that we chose.

• See freeCodeCamp.org for how the minigame is created.

• Each game includes home page, rules page, prepare page, game page and result page

  • Asteroids

  

  * Collect Gold

  

  * Pelters

  

Using the same coding pattern as above, we render minigames by creating a component for a individual minigame; in this case we have three minigames:

Components within each minigame contain an opening screen, rules, prepare screen, the minigame (canvas), and the results page. To tie the sub components together, we have a file containing each component conditionally rendered:

User authentication is necessary for us allow users to have saved game data and ensure that only the right user can continue or delete their games.

To authenticate users, we implement JSON Web Tokens that are created on user login or sign up, and store in local storage.

Backend: On user login through the browser, the user's username and password are sent to the server via a POST request to /api/user/login. This route checks the password against the hashed password, signs a token (24 hour expiration) with the user information, and sends the token back to the frontend for saving a session:

The sign up route is similar, with the only difference being that the user is created.

Once the user has the token save in local storage, any requests to the backend will be checked for an authorization header and the logic is taken care of in this withAuth function

To protect an entire set of routes, we can specify at the top of the file containing that set of routes.

Frontend: Once the user is logged in, any of the fetch requests requiring authentication need to contain an authorization header. Using axios, we specify an option containing our generated authorization request header:

GIF demonstration: see sign up

• Peter Consagra | GitHub | Portfolio
• Denzal Martin | GitHub | Portfolio
• Troy Johnson | GitHub | Portfolio
• Quishuang Tian | GitHub | Portfolio
• Pranav Byakod | GitHub | Portfolio

Thank you to the UC Berkeley Bootcamp teaching staff for providing the resources and help to us in completing this project.