A Hytale world: overgrown ruins above a path, sun breaking through the towers
Hytale server infrastructure · solo

Your community outgrew your bash script.

I'm BitaceS. I build the technical layer Hytale communities run on — control panels, Discord bots, server setups. Not an agency. One person, on the same Discord as you at 2am when a node goes down. TalePanel is the proof, and you can install it tonight.

My own world · Hytale
01 — The proof

I didn't write a portfolio. I shipped a panel.

Most panels treat a game server as one thing: a process with a console and a start button. Hytale isn't that. Hytale is worlds, mods, players and hosts — and an operator with more than one box needs all four to be real objects, not folders on a disk.

Ruins and open terrain in one of my Hytale worlds

TalePanel

A Go control plane, a Rust daemon on every node, a Nuxt panel on top. Nodes enroll with a single-use token and report back in about thirty seconds. Roles, two-factor, an audit log over every action. Backups, a file manager, mods and plugins you can switch off without deleting them.

It's a 0.9.0-beta. That's not modesty, it's a version number — things will break, and I'll tell you before they do. I don't put a feature on a website before it exists in the repo.

AGPL-3.0 Go · Rust · Nuxt Multi-node 130+ endpoints One-line install
02 — What I build

TalePanel is what I build when nobody's paying me.

Here's what I build when someone is.

Server infrastructure

Panels, daemons, provisioning, deployment, multi-node setups — the boring parts that decide whether your community stays. If you're running more than one box and it currently lives in your head and a bash script, that's the conversation.

Discord bots

Server status, whitelist and role sync, ticket flows, moderation, panel integration. The kind that talks to your actual game server instead of posting an embed and calling it a feature.

Websites for communities

Community sites, landing pages, stores, docs. No page-builder bloat, no four megabytes of JavaScript to render a server IP. The page you're reading is one file.

No client logos here, because I'm not going to put a logo on this page that I haven't earned. What I can show you is a product you can download and run tonight.

03 — Background

I learned this where it goes wrong, not where it's taught.

I worked at a hosting provider before I built any of this. Not writing features — keeping other people's machines alive. The rest I picked up the way you pick things up when you're self-employed and nobody else is coming: by breaking it, then fixing it.

Customer servers

Real customers, real outages, real clocks. Someone's server is down, they're losing players, and "I'll look into it" isn't an answer. You learn very fast which explanations are true and which ones are just comforting.

Linux & Windows

Provisioning, patching, migrating, hardening — on both. Not a course, not a homelab: production boxes where a mistake shows up in someone else's business.

Network & DDoS

Firewalls, filtering, routing, absorbing attacks. It's why TalePanel's daemon watches the Hytale UDP ports and can rate-limit a flood with nftables before it ever reaches the game. That feature isn't a bullet point — it's a scar.

Virtualisation & game hosting

Hypervisors, game server platforms, automated provisioning. I've stood on the other side of the panel — which is exactly why I had opinions strong enough to go build my own.

Anyone can write a feature. Keeping a box alive under load, with real players on it, at 3am, is a different job — and it's the one most gaming projects lose.

04 — How I work

Four things, so we both know what this is.

01

You talk to me. That's the whole org chart.

No account manager, no handoff to someone junior, no "we". There is no we. There's me, and there's your project.

02

I don't oversell, and I don't overbook.

I do this alongside a job, which means I take few projects and I tell you my real timeline instead of the one you want to hear. If I can't do it well, I'll say so and, where I can, point you at someone who can.

03

You get the source.

Everything I build for you is yours — code, repo, deploy scripts, documentation. No black boxes, no rental hostage situation, no "only I can maintain this."

04

If the code doesn't do it, I don't claim it.

That rule is why TalePanel's site doesn't have a feature list full of things that "are coming". It's the same rule here.

05 — Stack

What I actually use.

Backend
Go (Gin, pgx) · Rust (tokio, axum) · Node
Game side
Java / JVM — a Hytale server is a JVM process. TalePanel's daemon supervises it and ships its own Temurin runtime, so the box doesn't need a system JDK.
Data
PostgreSQL · MariaDB · Redis
Frontend
Nuxt 3 / Vue · TypeScript · plain HTML when plain HTML is right
Infra
Linux (Debian, Ubuntu, Rocky) · Windows Server · Docker · Caddy · systemd — from a hosting provider, not a tutorial
Network
nftables rate limiting · UDP flood detection on the game ports · TLS with Let's Encrypt, a real certificate even without a domain · node enrollment and heartbeats across hosts
Bots
discord.js / Discord API

Not a list of logos I once opened a tutorial for. This is the stack TalePanel is built from, and you can verify every line of it.

07 — Contact

Tell me what you're building.

Server setup that's outgrown you? A bot that needs to do something real? A community site that should load in under a second? Send me the messy version — I'd rather read three honest paragraphs than a polished brief.

info@diengdoh.com

Usually back within 48h. If it's not a fit, I'll say that in the first reply instead of the third.