abishekdevendran / chainreactionvite

A multiplayer chain reaction game made with ReactJS, TailwindCSS, Vite, SocketIO, etc.

Hi 👋, I'm Abishek Devendran

A passionate fullstack + AI developer from India.

• 🔭 I’m currently working on Aristotle

• 🌱 I’m currently learning Plugin Based backend architecture

• 👨‍💻 All of my projects are available at https://github.com/abishekdevendran

• 📝 I regularly write articles on https://abishek-devendran.pages.dev/

• 💬 Ask me about React, Svelte, Langchain, RAGs, Agentic systems.

• 📫 How to reach me [email protected]

Connect with me:

Languages and Tools:

From: 08 December 2022 - To: 19 June 2024

TypeScript      535 hrs 34 mins >>>>>>>>>>>>>>-----------   56.11 %
JavaScript      95 hrs 36 mins  >>>----------------------   10.02 %
Python          72 hrs 30 mins  >>-----------------------   07.60 %
C++             72 hrs 22 mins  >>-----------------------   07.58 %
Svelte          46 hrs 43 mins  >------------------------   04.90 %

chainreactionvite's Issues

premoving ability

Making a Game State Manager to manage turns and multiplayer endpoints

• High level turn manager
• Network dispatches
• Individual forfeit manager
• Make Hot Toast work
• Promote server instance to express

Show last player move highlighted

Migrate from Heroku to Render

Heroku free tier is going down by September.

find a way to fix icons on custom rendered hot toasts

Board anims and page transitions

Fix resetting isReady at index.js backend

forfeit still works after defeat

new room from RoomCreator component has double calls, while direct URL drops and restarts dont

unready toggle is inverted

Initial Project Structure

Setup folder structure with Vite and Tailwind setup and ready to go.

Color Picker

Building a working game board logic

This is exclusively for the logic and doesn't account for visual appearance.

• Make Squares
• Have top level game board logic at board level

client volume slider

client boardSize mismatch on join

client isReady same name bug

board physics

Player can still forfeit after losing

Main Project Shortcomings

1. Use dispatches and reducers for complex state management. This seems trivial but is crucial in combating stale state management.
2. Map where data sits and interacts before starting to write bottom up code.
3. Prevent data duplication by keeping one instance either on server or client so wouldn't have to manage syncing state.

spectate on joining lobby after match start is buggy