logo

I'm Ricardo Antonio (aka ricodevvv). I live in Hidalgo, where I build the future.

I write server software for Minecraft. Not maps, not builds — the layer
underneath: a PaperSpigot fork with its own knockback and packet APIs, a
packet-level anticheat, a practice core running ten minigames, a replay system
that records matches and plays them back.

Most of it is Java. Some of it is 1.8.8 and Java 8 because that's where
competitive PvP still lives, and some of it is Java 21 with MongoDB, MinIO and
zstd because storing thousands of replays is a storage problem before it's a
Minecraft problem. Working across both ends has been the most useful thing about
this niche: you learn NMS internals and distributed storage in the same project.

I care about the parts nobody demos. Knockback that feels identical on every
server in the network. An anticheat that flags a real cheater and not a player on
a bad connection. A kit format someone else can edit without opening an IDE.
That's the work.

Outside of Minecraft I build with Next.js and TypeScript — this site included.

Usage

Tools, technologies and gadgets I use on a daily basis but not limited to.

### Editor and terminal

IntelliJ IDEA for anything Java, which is most of what I do. VS Code for the
web side. GitLab Mono as the editor font — it's also the mono typeface on this
site.

### Languages and runtimes

Java is home: Java 8 for 1.8.8 server work, Java 21 for everything modern.
TypeScript and Next.js for the web. Gradle when I get to choose, Maven when the
project already decided.

### Storage

MongoDB for anything that outlives a match. MinIO / S3 for replay blobs, with
zstd in front of it — replays compress extremely well and the bandwidth savings
are worth the CPU.

### Everything else

Git, obviously. PacketEvents for anything touching the network layer.

Heroes

Inspired by Rafael Condo's heroes list, here's my own curated lineup of code conjurers and digital dynamos that I'm absolutely stoked to meet someday. "In no particular order"