hasan-jawaheri/wasabigame

Game showcase for the Wasabi Engine

wasabigame's Issues

Add a logger

Add a logger to WasabiGame (should be later moved to Wasabi, as should this whole module)

Requirements:

• Globally accessible (in the Wasabi instance)
• Logs timestamp, severity and message
• Log to a buffer, add ability to redirect it
• Implement redirection to a console window

Re-architect server code into cells

Restructure server code to have cells (login/matchmaking/game...) to have rooms and allow scaling and isolation. Initial design at https://1drv.ms/u/s!AtcSRm1uMDFjmb15sSDQ6DCl1FeQLQ?e=BgKIvh

Sometimes player doesn't load map

For some reason sometimes player (client) doesn't load map, as instructed by server

Implement death

Implement a way to die and re-spawn

Graphics are very janky

Graphics are very flickery and it seems like there is a problem passing data to shaders. Need to double check if using a stable version of Wasabi

Reorganize WasabiGame library

This library is a mess. Reorganize as follows:

• Replace "new" with smart pointers wherever possible
• Incorporate networking into the library
• Incorporate the scheduler into the library (separate from networking)

Create a playable map

Anything will suffice, maybe some interesting spots and possibility of "dying" (falling off)

Implement a chat feature

Implement a simple chat box (global chat for now) and player chat bubbles (on top of player) when nearby

Create the simulation

Create the simulation:

FR:

• It should create a Wasabi Physics component
• It should allow visualization
  • For now, always create wasabi debugger on the side
• accept player loading/removal (and send load/unload/update status to players)

Clean and update RollTheBall

Requirements:

• Clean style and namespace all classes
• Remove dead code
• Convert to smart pointers

Implement a server-controlled NPC

Functional requirements:

• NPC driven by an AI on the server
• Does donuts and sometimes jumps
• Players should be able to see him roughly in the same spot

Separate server simulation from unit logic

Server simulation should be optional. It should be separated from player loading, units, etc...

Implement (initial) player synchronization

Functional requirements:

• Server is ultimate source of truth
• Players play on their own, send their motion to server
• Players receive other players' motion in the past in a separate logical timeline and replays it with some delay
• Small incremental corrections to player motion as it skews away from server