CSSE Multi-User Features, Server Deployment

[MatthewBorabo]

Assigned

Trystan, Mathew, Ian, Gavin I

Brain write Teacher

• Rohan will work as Scrum master.
• Talk with Rohan and get his brain write.
• Review posted material on week 18, it is in "Tools and DevOps" column.

Key server concepts

• AWS server setup, Electric Cloud Compute (EC2)
• Deployment on EC2
• Web sockets
• Serializing and exchanging player movements.
• Visualizing other players in level

Key features multiuser ....

• Brain write provided to Rohan
• Integrate Multi-user from Rohan's work
• Build and AWS server
• Consider how you will stage a Multiuser event in Game... how will players get into game, how will use settings UserID for identification, will you be able to see score and determine winner?

Key Code ownership and Expertise

• Review implementation ticket from Rohan, built on GameLevels v1.0
• AWS deployment guide
• Node Backend Readme contains Nginx configuration

[MatthewBorabo]

Regarding today's event, you will work on it today and be prepared to discuss it on Tuesday. "assigned GameLevels 2.0 teams discuss Brain Write and Design Mock ups with Teacher and Operation Officers/Project Managers (1 point activity)"

1. Start a team Issue in GitHub
2. Review your activity with my notes.
3. Have a Team meeting to discuss activity and write down notes in your issue.
4. Consider activity and division of work, think of the following: a. What code or features will you add to the project? b. Who will be primarily responsible for each feature (individuals or pairs)? c. How will you support each other on tasks? d. What other teams will you need to work with to accomplish your project? e. What do you think will be assets or lessons that describe what you make so others can understand it, learn from it?
5. In design, often Engineers make pictures or visuals of plans to help others understand what you are making. Add these to Team Issue.
6. You should plan on talking to the teacher and a coordination team member for 5 to 8 minutes on Tuesday, this will be graded.
7. Having an issue is really important, this will be used to track your work for Pull Request.

[MatthewBorabo]

Brain Write (by Rohan): https://nighthawkcoders.github.io/teacher_portfolio//2023/12/04/CSSE-tri2-oop-multi-player.html (includes Implementation Ticket)

[MatthewBorabo]

4. a. Code/Features:

   • Allowing players to play with others using AWS (opposite of local)
   • Servers can handle up to 30 players.
   • Players will have different skins and have their Github ID or custom name above their character
   • Using collision and items, players can interact with others.
   • Make a racing mode where players will try to compete for the fastest time or the mode levels completed.
   • Cooperate with the enemy team to sync the enemies together so it is not client-based.
   • Collaborate with the collision team to have separate death animations (if needed) for multiplayer.
   • Determine when the game ends and how it will end.
   • Embed a chat function inside the game/repo b. Dividing the work (may be updated in the future) THE MULTIPLAYERS Gavin I:
     • Ian M:

     • Matthew B:

     • Trystan S:

     • Setting up Amazon Web Services (AWS)

     • Rohan J (Scrum Master & TA):

     • Giving help/guidance to us.
     • Making the brain write, implementation ticket, and multiplayer set-up/outline. c. We can work in pairs and ask help from Rohan if needed. d. We will collaborate with the leaderboard and RPG team. e. The multiplayer brain write and implementation ticket made by Rohan will help others understand the idea of multiplayer. In terms of the closest student lesson to multiplayer, our local storage lesson and leaderboard lesson would help as they have similar ideas and use with multiplayer.

[Im2008]

3. Notes (Updating):

Focusing on Multiplayer Repo since multiplayer would be better on different repo.

Keep Mario in

Possibly add styles to make basic mechanics look appealing

Add descriptions for commits as a summary

(Working on): Multiplayer Adding levels [etc...]

(Fixed): [nothing currently]