This is a networked-multiplayer game based on Flappy Bird
To play this game, first start your server with npm start.
To get your computer's network name, look in SystemPreferences/Sharing. You should see a name along the lines of [ComputerName].local.
Open up a browser and go to localhost:3000 to start the game. Space lets you jump, and W... makes things easier.
To play with other people, have someone else use your computer's network name like so [ComputerName].local:3000
You should see a rainbow sheep appear on your version of the game when someone else goes to that address, or refreshes their page. When they jump in their game, you will see the rainbow sheep jump in your game.
(Unfortunately, the games do not sync up, so each computer sees separate games. It works best if everyone watches the same screen.)
Use a Flappy Bird Clone to make a networked game that includes simultaneous multiplayer and saving a user's game data to a postresql database.
Learn the ins and outs of Networking and sharing simultaneous data between multiple users.
- User can play a basic Flappy Bird clone using the Spacebar
- Map is generated randomly with a reusable seed, allowing multiple players to see the same random map.
- User can log in, and we will use a postresql database to save high scores, achievements, flap count
- Users will be able to connect to each other from different computers to play a head-to-head game.
- Game saves win loss record after versus games
- Database saves locations where players have died, and you can see the deaths of people you played a vs. match against.
- Test backend and testable front end functions with chai
- Implement character movement without Phaser
- Implement random obstacle generation without Phaser
- Implement collision detection without Phaser
Do not remove these specs - they are required for all goals.
- The artifact produced is properly licensed, preferably with the MIT license.
Well formatted code
- Code uses a linter, which can be invoked with a command (e.g.
npm run lint). [50 points] - Running the linter on all source code files generates no linting errors. [50 points]
Clear and useful README
- Repository includes a README file with installation and setup instructions. [25 points]
- Repository includes a README file with usage instructions and at least one example use case. [25 points]
Proper dependency management
- There is a command to install dependencies (e.g.
npm install) and it is specified in the installation and setup instructions of the README. [50 points]
Good project management
- Commit messages are concise and descriptive. [25 points]
- All features are added via pull requests. [25 points]
- Every pull request has a description summarizing the changes made. [25 points]
- Every pull request has been reviewed by at least one other person. [25 points]
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.