GO BLOX

I originally built GO BLOX because my small Indonesian Roblox community desperately needed a way to stay organized. When we were just a handful of friends, every new member brought a flood of questions and a chaotic channel layout. Relying on endless text commands was causing too much noise, and I kept seeing users make the exact same mistakes over and over. I wanted a smoother experience that felt welcoming from the moment someone joined, a phase of the project I detailed in my article about building for this community.

To fix the command confusion, I made visual interactivity a core principle from day one. I completely shifted away from plain text inputs and focused on providing tools that feel native to Discord. Under the hood, I used discord.js version 14 and built a modular architecture, dividing the application into independent pieces. The main goal was to keep the bot lightweight enough to run continuously on modest hardware, a technical challenge I discussed in my post about continuing the GO BLOX journey.

Projects like this are never really finished, and recently I have been focused on refining the user interface and stripping out unnecessary bloat. Starting around the version 1.2.0 release, I spent time evaluating what actually mattered to our server. Here is what I have been working on lately:

1. Removing the chatbot functionality
   To stay true to my goal of keeping the application lightweight and focused on server organization, I ended up entirely removing the chatbot feature. It was a necessary step to ensure the bot runs smoothly without wasting hardware resources.
2. Implementing booster roles and modals
   I added dedicated logic for server boosters. Since visual interfaces are a core part of the bot, I built interactive modals for boosters to use. I recently spent time fixing modal bugs to make sure the interface stayed clean and responsive.
3. Adding detailed bot information modules
   I integrated new visual modals specifically for displaying bot information, reducing the need for users to type out help commands. This ties directly back to my original goal of cutting down channel noise.
4. Building the AFK System
   I introduced an AFK system to help community members keep track of who is currently available, which directly addresses the organizational needs of our growing server.

Building GO BLOX has been a great lesson in iterating based on how people actually use a tool. Instead of packing it with random features, I am constantly watching where users get stuck and updating the visual interface to guide them better.