Board game for UNO code competition
This repository has been archived on 2023-11-15. You can view files and clone it, but cannot push or open issues or pull requests.
Find a file
2022-12-09 20:14:52 -06:00
.vscode Initial commit 2022-12-09 17:12:17 -06:00
dev Initial commit 2022-12-09 17:12:17 -06:00
public Commit all final fixes 2022-12-09 20:14:52 -06:00
src Minor changes 2022-12-09 17:22:05 -06:00
.eslintrc.json Initial commit 2022-12-09 17:12:17 -06:00
.gitignore Initial commit 2022-12-09 17:12:17 -06:00
.prettierrc Initial commit 2022-12-09 17:12:17 -06:00
LICENSE Initial commit 2022-12-09 17:12:17 -06:00
nodemon.json Initial commit 2022-12-09 17:12:17 -06:00
package-lock.json Fixed issue 2022-12-09 17:24:03 -06:00
package.json Update 'package.json' 2022-12-09 17:15:05 -06:00
README.md Initial commit 2022-12-09 17:12:17 -06:00
tsconfig.json Initial commit 2022-12-09 17:12:17 -06:00

Blue Team: The Game

Description

Files strewn across the board which may or may not contain a virus. The players must protect their end point/router/network from the enemy (which is the computer). Certain players have different powers that help you in defending your endpoint.

Powered By

  • Node.js - the runtime for this project because it is quick and easy to spin up.
  • Typescript - most if not all of the backend code is written in typescript. TS was chosen over javascript because it ensures that types remained consistent throughout which is crucial to having less error prone code.
  • Express.js - used as the minimalist web framework to display the web page. It gave me low enough capabilities without going too low that it was hard to develop with.
  • Socket.io was used to make realtime interaction possible through the use of websockets and HTTP Long Polling as a fallback.
  • Catppuccin was used for the color scheme, it is pleasing and dark, with good guidelines on how to implement it.

TODO:

Game

  • Finish rules
  • Play the game

Backend

  • Setup DB
  • Setup classes
  • Implement class abilities
  • Implement turns
  • Implement computer/file interaction
  • "Success" needs to be rolling
  • Leaving player breaks things
  • No "scratch disk class"
  • Sort detected
  • Fix movement

Frontend

  • Setup CSS
  • Finish main menu
  • Finish gameplay menu
  • Finalize