Team 13 Final Project Submission

.gitignore

@@ -0,0 +1,2 @@
+config.env
+node_modules

README.md

@@ -1,56 +1,33 @@
 # cs4241-FinalProject
+# Team Members: Jonathan Dang, Ivan Eroshenko, Clay Oshiro-Leavitt, Adrianna Staszewska
 
-For your final project, you'll implement a course project that exhibits your mastery of the course materials. 
-This project should provide an opportunity to be creative and to pursue individual research and learning.
+1. We created an exciting multimedia experience - Pacpeople. This web application is a modern take on the hit classic - Pacman. This time, there are multiple players and takes place on a larger game board. With up to four human players and 5 monsters, the game can become quite intense and challenging.
 
-## General description
+Game Link: https://pac-people.herokuapp.com
 
-Your project should consist of a complete Web application, exhibiting facets of the three main sections of the course material:
-
-- Static Web page content and design. You should have a project that is accessible, easily navigable, and features significant content.
-- Dynamic behavior implemented with JavaScript (TypeScript is also allowed if your group wants to explore it).
-- Server-side programming *using Node.js*. Typically this will take the form of some sort of persistent data, authentication, and possibly server-side computation. Ideally it will also include support for realtime commmunication as discussed below.
-- Groups are *highly encouraged* to consider including some type of realtime communication technology in their projects (chat, networked multiplayer games, collaborative coding/editing, video/audio via WebRTC etc.) We'll be discussing many of these technologies in class next week. 
-- A video (less than five minutes) where each group member explains some aspect of the project. An easy way to produce this video is for you all the groups members to join a Zoom call that is recorded; each member can share their screen when they discuss the project or one member can "drive" the interface while other members narrate (this second option will probably work better.) The video should be posted on YouTube or some other accessible video hosting service. 
-
-## Project ideation
-
-Excellent projects serve someone/some group; for this assignment you need to define your users and stakeholders. I encourage you to identify projects that will have impact, either artistically, politically, or in terms of productivity. Consider creating something useful for a cause or hobby you care about.
-
-## Logistics
-
-### Team size
-Students are will work in teams of 3-5 students for the project; teams of two can be approved with the permission of the instructor. Working in teams will allow you to build a good project in a limited amount of time.
-
-### Deliverables
-
-__Proposal:__ 
-Provide an outline of your project direction and the names of the team members. 
-The outline should have enough detail so that staff can determine if it meets the minimum expectations, or if it goes too far to be reasonable by the deadline.
-This file must be named proposal.md so we can find it.
-Submit a PR to turn it in by Monday, 11:59 PM
-
-There are no other scheduled checkpoints for your project. 
-
-#### Turning in Your Outline / Project
-
-**NOTE: code is due before the project presentation day due to the end of term / grading schedule constraints**
-Submit a second PR on the final project repo to turn in your app and code.
-
-Deploy your app, in the form of a webpage, to Glitch/Heroku/Digital Ocean or some other service.
-Folks on the same team do not need to post the same webpage, but must instead clearly state who is on the team in their proposal.
-
-The README for your second pull request doesn’t need to be a formal report, but it should contain:
-
-1. A brief description of what you created, and a link to the project itself.
-2. Any additional instructions that might be needed to fully use your project (login information etc.)
+2. Additional instructions: you can play as a single person, however it is preferable to play with 1-3 other players. You can open up multiple browser windows to test the multiplayer aspect. If two players run into each other they will die.
 3. An outline of the technologies you used and how you used them.
-4. What challenges you faced in completing the project.
-5. What each group member was responsible for designing / developing.
-6. A link to your project video.
-
-Think of 1,3, and 4 in particular in a similar vein to the design / tech achievements for A1—A4… make a case for why what you did was challenging and why your implementation deserves a grade of 100%.
-
-## FAQs
+4. While working, we quickly discovered the limitations of Ably’s free services. We continually exceeded Ably’s message rates and limits, resulting in several of our accounts being suspended while testing. We also ran into issues with the maximum message size that is allowable over Ably. This required some rework of our message design to fit within the allowable message size.
+5. Team Workload:
+- Jonathan Dang
+  - Handled logic of players colliding with one another
+  - Handled the detection of when game ended
+  - Helped out with player movement logic
+- Clay Oshiro-Leavitt
+  - Wall detection and move validation logic
+  - Player spawn location logic
+  - Player movement logic
+  - Integration and composition of game music
+- Ivan Eroshenko
+  - Implemented UI
+  - Helped to give a head start on project implementation
+  - Implemented the boss with A*
+
+- Adrianna Staszewska
+  - Coin collection by players
+  - Updating user’s scores in the database 
+  - Movement of monsters 
+
+6. Here is the link to our project demonstration video.
+https://youtu.be/Lpv8TB81V8g
 
-- **Can I use XYZ framework?** You can use any web-based frameworks or tools available, but for your server programming you need to use node.js. Your client-side language should be either JavaScript or TypeScript.

config/db.js

@@ -0,0 +1,23 @@
+const mongoose = require("mongoose")
+
+const connectDb = async(mongoUri) => {
+    try {
+        const conn = await mongoose.connect(mongoUri, {
+            useNewUrlParser: true,
+            useUnifiedTopology: true,
+            useFindAndModify: false,
+        });
+
+
+        console.log(`MongoDB Connected: ${conn.connection.host}`)
+
+
+    } catch (e) {
+        console.log(e);
+        process.exit(1);
+    }
+}
+
+
+
+module.exports = connectDb

middleware/auth.js

@@ -0,0 +1,16 @@
+module.exports = {
+    ensureAuth: function (req, res, next) {
+        if (!req.user) {
+            res.redirect("/login");
+        } else {
+            next();
+        }
+    },
+    ensureGuest: function (req, res, next) {
+        if (req.user) {
+            res.redirect("/");
+        } else {
+            return next();
+        }
+    }
+}