A utility bot for anarchy minecraft servers with more than 100 commands, a database size of 50GB saving player data for more than 1.5 million Minecraft players and over 100 million messages.

I also monetized and sold $20 usage rights to over 15 different server owners.

Closed-source. Source code available for review upon request.

• Engineering Challenges
• Migration History
• Key Features
• User Commands
• Admin Commands/Tools/Configuration

graph TD
    %% --- Section 1: UUID Caching ---
    Bot[UUID Parsing] -->|1. Resolve User| Check{In Cache?}
    
    Check -->|Yes| DB[(SQLite DB)]
    Check -->|No / Stale| API[Mojang API]
    
    API -->|2. Backfill Data| DB
    DB -->|3. Return UUID| Bot

    %% --- Section 2: Message Grouping ---
    subgraph "Message Grouping/Queuing"
    Msg1[Chat 1] & Msg2[Chat 2] & Msg3[Chat 3] --> Aggregator[Grouper]
    end
    
    Aggregator -->|Single Embed Count <= 10| Batch[Add to queue]
    Batch -->|Wait 1000ms/embed| Discord[Discord API]

    %% --- Section 3: Smart Server Pinger ---
    subgraph "Connection Logic (Smart Pinger)"
    Disconnected([Disconnected]) --> Timer[/Wait 3s/]
    Timer --> Ping[Ping Packet]
    
    Ping --> Status{Online & Players > 0?}
    
    Status --No--> Timer
    Status --Yes--> Join[Initiate Join]
    end

Benchmark Results (20M Rows Active Dataset):

• Legacy Search (LIKE): 5.599s (Thread Blocking)
• Optimized Search (FTS5): 0.010s (Instant)

Query Latency Comparison:
Legacy (LIKE): |==================================================| 5600ms
FTS5 (Match):  |                                                  | 10ms

My messages were constantly getting blocked for being too similar so I added some code to check if a message was sent by the server after 2 seconds, and if it wasn't, the message is automatically resent with extra characters at the end.

I wanted to avoid hammering the Mojang API, so I added a UUID caching system. Usernames are locked for 37 days following a name change, so I set my limit to 35 days. UUIDs are stale after 35 days and will automatically be regrabbed upon request. This resulted in much fewer api requests as I was essentially the API.

Same concept of the message queuer but for discord. I added the bot to a server with nearly 30K players all chatting at the same time and there was around 10 messages every second. The discord rate limit is 4/s with 10 embeds per group. So I created the grouper and queuer which brought my limit from 4 msgs/s up to 40 msgs/s

Originally the bot was just sending out messages whenever players sent commands, but sometimes multiple players want to run commands at once, so this feature automatically queues up messages so the bot is never limited by the antispam.

I wanted to avoid hammering the Mojang Auth API which logged in my account everytime I tried to connect to a server. Instead of logging in, I just added a pinger which detects exactly when a server comes online and if theres more than 0 players, so I can instantly join.

All migration scripts have been archived and can be found in /migrationscripts

I was trying to scrape 2b2t.vc for historical playerdata to fill in the missing gaps, and had to deal with rate limits. Instead of a static 10 second cooldown, I added a feature that automatically adjusted the cooldown to get the max number of requests without getting errored. I also added a feature to automatically cut new players (that haven't been checked yet) to the front of the queue so data was as accurate as possible without having to wait 2 months for all data to be scraped.

graph LR
    subgraph "Historical Data"
    New[Recently Joined Players] -->|High Priority| PQueue[("Scrape Queue")]
    Old[Inactive Players] -->|Low Priority| PQueue
    end

    PQueue -->|Pop Next Item| Worker[Scraper Worker]
    Worker -->|Request| Site[2b2t.vc]
    
    Site -->|Response| Check{Status Code?}
    
    %% Success Path
    Check -->|200 OK| Success[Process Data]
    Success -->|Save| DB[(Database)]
    Success -->|"Decrease Delay (-150ms)"| AdjustDelay[Throttler Config]
    
    %% Failure Path
    Check -->|429 Rate Limit| Fail[Backoff]
    Fail -->|"Increase Delay (+500ms)"| AdjustDelay
    Fail -->|Re-queue Item| PQueue
    
    AdjustDelay -.->|Apply Cooldown| Worker

FTS-5 is essentially a copy of the messages table and takes up a ton of space. I realized there's a lot of useless spam on these servers and added a command to delete all rows containing certain phrases like discord links. This cut the database size in half.

I wanted to add a !clout command which shows how many times a phrase has been said in chat, normally this SQL query takes 10+ seconds to run as it has to go through millions of messages, but I added FTS-5 support which makes it incredibly efficient to search through text. With 20 million rows, the legacy LIKE operator took 5600ms, while FTS5 match took only 10ms.

I had some missing data that was never saved which I was able to grab from the logs I kept going back to 2021. I was able to add new commands (like !joins to show how many times a player joined) and backfill the data from the logs. I also saved all death messages going back to 2021 so I could add commands like !lastdeath. I was also able to fill in missing data caused by a bug years ago that didn't save join dates for a few months.

For my messages table I was using an array of messages converted into a string for each player which wasn't ideal. I converted everything into per row and later added FTS-5 support to make searches instantaneous.

Originally, the bot was using JSON files saved for each individual player. This is a terrible way of storing data with files randomly corrupting, and I even ended up reaching the Linux INode limit. (df -i) Once that happened I immediately got to work and started migrating everything to an SQLite database which is much more efficient and allows for commands that would never be possible with a bunch of JSON files.

Back when I first created the bot, one of the very first migrations I had to do was converting the format of the files.

The bot has full support in discord for cross chatting and running commands!

The bot uses sqlite3 to store all kinds of player statistics and messages.

The bot will queue up messages so all messages can go through and the bot won't get kicked for spam.

The bot automatically groups up messages (up to 10 embeds per message) to avoid getting rate limited by discord with lots of chat messages

The bot will automatically retry messages that fail to send after a few seconds.

The bot will automatically save kill and death messages without requiring a regex statement. This works by checking for usernames in the message. Use OppositeDeathMessages if the killer comes first

The bot includes an advanced configurable regex system for custom chat regexes if the default doesn't suit your needs.

The bot will automatically ping the server every 3 secs before joining to make sure it's online, has more than 0 players online in case the main server is down, and avoids constant logins.

Never miss a message with a full logging system. The bot will automatically log messages and join/leave msgs and automatically compress log files to save space.

The bot will automatically accept TPA requests.

When enabled the bot will automatically run /realname USERNAME for any nicknamed players.

UUIDs are cached to a database and recached after 35 days to avoid hammering the Mojang API (Minecraft usernames are locked for 37 days before they can be taken)

All players have their own mailbox and other players are able to send them messages while they are offline so they can recieve it once they go back online.