Code

The problem

Our daily community workflows were extremely slow. Manual processes such as level requests consumed staff time, recurring formatting issues created repeated incidents across different areas, and answering basic questions depended on individual staff members being available.

The community

An international creative community with over 3,000 members and around 200 new members each month, built around using Geometry Dash as an art form.

What I built

A Discord bot that enforces formatting rules and checks submissions for errors, together with a request system that has evolved into a central part of the community's infrastructure. I later expanded it with community commands, support tools, and features designed to improve the user experience.

Technical structure

Pycord-based architecture with cogs, utils, docs, DB, and scripts hosted as a Render web service with scheduled UptimeRobot pings.

report form
  -> Discord events / slash commands / buttons
  -> main.py loads the bot and routes work into cogs
  -> cogs handle feature-specific workflows
  -> utils provide shared helpers and database access
  -> persistent storage remembers long-running state
  -> Discord receives embeds, logs, tickets, reviews, DMs, and summaries 

• Result

  Avenue Guard automated the workflows that had created the greatest recurring friction for members and staff. It has since become a central part of the community's infrastructure, handling recurring interactions while allowing staff to focus on cases that actually require human judgement.

• Impact

  Over 6,000 automated events and more than 300 unique members directly interacting with the system.

• What I learned

  I originally treated errors as isolated failures. Running Avenue Guard continuously changed that. A failed request or lost ticket could affect a real member and create more work for fifteen staff members. I began designing around recoverable state, persistent logs, backups, and workflows that could resume after interruption. Reliability became one of the main parts of the user experience.

• Current status

  The service is fully deployed in our community. I continue to update the bot, add new features, and respond to community requests for new automations and activities.

What it is

Nauta is a service for any community that wants to store their Minecraft world/server coordinates and quickly search stored coordinates and find the nearest ones.

Why I made it

When some friends and I started a Minecraft server, we often found ourselves searching for coordinates written on misplaced pieces of paper, causing us to repeatedly lose track of our farms, portals and other points of interest. That is why a friend and I decided not only to build a bot that made coordinates easy to access, but to integrate it into the Minecraft experience itself.

My role

Though we both worked on the core structure and logic, I focused on frontend and Discord API interactions.

How it works

Based on customizable permissions, a user can register, delete, edit, or list coordinate entries using filters such as dimensions and aliases. The user can also find the saved coordinates nearest to their current location, including routes across dimensions.

Evidence and outcome

Although the bot is still small, it handles dozens of operations per day.

Current status

The bot is available to the public and will continue to be updated.

GitHub profile