StrikeMC

Why it exists

At thirteen I wanted a competitive Minecraft PvP server that felt premium: fast, fair, and run by someone who cared whether a match was rigged. I could not hire anyone, so I became the whole company. Developer, system administrator, community manager, and eventually the person a staff team of thirty reported to. It still runs today under the same banner it launched with, a blazing PvP experience at strikemc.net.

The engineering

Every layer is mine. I wrote more than 10,000 lines of custom Java covering matchmaking, arena mechanics, and the backend systems that tie a match to a player's record. It runs on hardware I administer rather than a managed host, which means I own the boring parts: the proxy, the panel, the firewall, and the pager.

• Game logic10,000+ lines of custom Java: matchmaking, arena mechanics, ranks, and the systems behind them.
• ProxyFlameCord fronting the backend servers, so players land on one address and get routed to the right instance.
• OrchestrationPterodactyl Panel to manage instances, deployments, and per-server resources.
• HardwareOVH dedicated machines with enterprise-grade DDoS protection, configured and maintained by me.
• Community systemsA Discord with automated moderation, rank synchronization, and event tooling.
• RevenueA Tebex storefront selling ranks and cosmetics, which paid the hosting bill.

A public Minecraft server is a genuinely hostile environment. You get denial-of-service attacks, people hunting for exploits in your plugins, and players who will stress-test every rule you forgot to write down. Running one for years is an education in security, capacity planning, and operational discipline that no tutorial provides, because the feedback is immediate and public.

Running it like a business

StrikeMC was never a hobby server with a donate button. It had costs and it had revenue. Dedicated hardware and DDoS protection are real monthly bills, and I covered them by pricing and packaging a store of ranks and cosmetics that players actually wanted, without selling the kind of advantage that ruins a competitive server. That constraint is the whole game: charge enough to keep the lights on, never enough to make the matches unfair.

I also ran the marketing that brought players in and the community that kept them, and I made the call to keep reinvesting after things went wrong instead of walking away. Doing that at thirteen taught me more about how a business actually works than any class has since.

The people part

I recruited, trained, and led a cross-functional team of more than thirty people covering support, competitive integrity, and moderation, and grew the Discord past two thousand members. Most of them were older than me. That sounds like a problem and it was, until I understood the fix: authority comes from the quality of your decisions and the consistency of your rules, not from your title or your age. Write the policy down, apply it the same way every time, and explain yourself when you change it.

The outages taught me more than the growth did. Anyone can run a server that is working. The job starts when it is not.

When it broke

The part I am most proud of is not the growth, it is the recovery. A run of severe outages took the network down and cost us the community's confidence. I rebuilt the infrastructure from scratch, restored uptime, and then did the slower work of earning trust back one player at a time, which meant admitting publicly what had failed instead of quietly hoping people forgot. The second version was better precisely because the first one failed, and I have never since shipped anything without asking what happens when it goes down at 2am.