We can probably do this right after build_map.
I suggest we ignore mobs respawning for the sake of simplicity.

This issue will detail the tasks we need to complete in order to get an MVP (minimal viable product).

Backend

• Set up websocket route for communicating with frontend.
• Map drawn out and movement implemented.
• Game mechanics (scoring, progression, etc).
• Multiple connections (might require the introduction of accounts)

Client

• Mockup layout for client.
• Set up connection with the backend through websockets.
• Handle incoming map and player data.

`Time passes, but you didn't do anything this round!"
Gets a bit annoying...

Game functionality.

• The starting map with the story.
• Basic gist of our bug. Single player that tries to do actions and show how they get scrambled.
• Basic multiplayer gist:
• • Chat between players (regardless of room)
• • Updates from other player's actions.
• • Mob deaths only notify players in the room. Player deaths notify every other player.
• • Player wins get notified to the entire server.
• Player leveling up.
• Player death screen.
• Player win screen.
• Killing stuff can be quite hard! You encouraged to quest alongside other "players".
• AOE heals and attacks can be very powerful! But they affect every entity other than the caster! You can heal your enemies and hurt your allies, so you're encouraged to be careful and not exploit this power too much.
• Wouldn't you like to know how much mana and health you have? But your brain is too scrambled to tell! You won't know until it's too late so you have to be careful ;)

Technical stuff / Design decisions.

• Slide to showcase how messages are sent and received by the player.
• Some miscelaneous stuff like message creation (e. g: f"You tried {tried}ing {with_} {target_name} but you don't have mana!")

Same-named mobs crash the server after being killed.

Probably because their UIDs aren't being generated uniquely.

I added obliterate to facilitate testing but it shouldn't be an action that a player can actually do.

Players can try registering twice and this causes an error.

Requires more testing, movement is getting scrambled for sure.

This is our /bug/ would be a bit sad if our bug that's a feature was actually not a bug that is not a feature.