Emoji Guess

ok so I completely forgot I had to make these 💀. I ended up adding the following things
- Containerization
- Disconnect Detection and redirecting
- Env Detection
- More words
- Connection Dot (helps players see their connection status)
- Fixed issues where players could connect to themselves.
- Queue Message that tells the player how many people are in queue

Next up is probably making the backend typesafe using Pydantic (i am never using python for backend again) and then implementing room creation and joining functionality (as well as bug fixes)

We're almost there. I've implemented the ending logic (if guesser gets it right/wrong and if someone disconnects). I've also added a modal that pops open when the round is over informing them what the word was and redirecting them to the home page. I have (mostly) created what I need for an MVP, now all that's left is to deal with my technical debt and get this ready for prod.

Fully implemented the game window (chat interface, conditional info) as well as the chat features, and functional timer, now I have to implement message filtering and a win/lose screen (prob gonna make it a modal)

Took another break, but I'm back for a (hopefully) more consistent commit schedule. I've finally fixed the connection logic and get started working on the actual game part

AI NOTICE 🤖: I use AI to help me with an issue I had. I was struggling to pass the websocket connection to the game page whenever navigating, so I asked AI to create a solution. While the AI did code it for me, I wanted to go through and make sure I understood what it did instead of blindly copying it.

Basically, it used the useContext hook from react to pass down the reference of the websocket to the page instead of having it within the page itself. This allows the root component to navigate between pages while maintaining the same connection (if you want to read more abt useContext use
this link
) it then instantiated the useWebsocket hook as normal and passed down the neccesary state variables.
Next will be actually creating game logic and the 'chat-room' aspect of the project.

it's been a while...

I had a bunch of IRL stuff to attend to so barely any coding. The architecture was also starting to intimidate me and I realized that the scope of this project was massive (I also got distracted by how hirable Java is like I never anticipated that happening).

I finally got around to making the joining logic, cut out a bunch of bloat. You don't know how happy I am to see this screenshot

FINALLY GOT WEBSOCKETS WORKING!🎉🎉🎉

Took forever cause I didn't really understand how to connect the frontend to backend and how to format backend code but from here it should be relatively easy

For this project, I wanted to make a simple chat app, then attach a game element onto it. I started out with a LOT of research into what tech stack to use as I'm unfamiliar with Websockets and how to use them. I ended up settling with FASTAPI backend and Vite frontend. I set up dev env for vite and made a basic UI, and I'm going to start looking into react Router for routing.