I build game systems and the infrastructure behind them.
Gameplay mechanics, Skript systems, and stable multiplayer backend operations.
Gameplay mechanics, Skript systems, and stable multiplayer backend operations.
I build gameplay features players actually use, then handle the infrastructure that keeps them online.
Custom mechanics, Skript workflows, and server features built around progression, balance, and replay value.
Separate lobby, survival, and utility nodes behind one proxy so updates and issues stay isolated.
I build and iterate gameplay systems quickly using Skript and config-driven workflows.
Velocity routing, segmented backend nodes, and practical infrastructure that handles real player load.
Backups, monitoring, and recovery plans are built in from day one, not added later.
My lab environment for testing, breaking, and hardening changes before they hit live servers.
Tools I use daily to build multiplayer features and keep servers stable under real traffic.
I help teams build gameplay systems and the infrastructure that keeps those systems reliable in production.
Progression loops, events, and server-side mechanics built for long-term multiplayer gameplay.
Feature rollouts and balancing passes based on how players actually use the server.
Custom items and assets integrated into drops, shops, progression, and core gameplay systems.
Config-first plugin and server setup so behavior stays consistent and easy to maintain.
Velocity routing and backend isolation that keeps traffic organized and reduces cross-node issues.
Health checks, alerts, backups, and recovery steps so downtime stays short when problems happen.
Projects I'm actively building and maintaining right now.
SugarSMP is my main live environment where I build survival features and run the full multiplayer backend stack.
How a player connection moves through the SugarSMP stack today.
flowchart LR A[Player Client] --> B[SugarSMP] B --> C[Playit Tunnel Ingress] C --> D[Public IPv4 Endpoint] D --> E[Ubuntu Physical Host] E --> F[Pterodactyl Node Runtime] F --> G[Velocity Proxy Container] G --> H["Lobby Container
Internal IP Route"] G --> I["Survival Container
Internal IP Route"] G --> J[Future Backend Containers] classDef outer fill:#0f172a,stroke:#38bdf8,stroke-width:1.5px,color:#e0f2fe; classDef infra fill:#1e1b4b,stroke:#8b5cf6,stroke-width:1.5px,color:#f5f3ff; classDef host fill:#052e2b,stroke:#10b981,stroke-width:1.5px,color:#ecfeff; classDef game fill:#111827,stroke:#c084fc,stroke-width:1.5px,color:#faf5ff; class A,B,C,D outer; class E,F host; class G,H,I,J game;
Runtime path: Player client -> SugarSMP -> Playit ingress -> Public endpoint -> Ubuntu host -> Pterodactyl node -> Velocity proxy -> Lobby and survival containers.
A live survival server focused on fair progression, fun gameplay loops, and dependable performance.
A space for shared systems, assets, and production workflows across multiplayer projects.
A long-term worldbuilding project focused on large maps, progression ideas, and multiplayer design.
If I can't monitor it, recover it, and trust it under load, it's not ready for players.
I'd rather ship one stable feature than five that break under pressure.
I use logs, metrics, and real player behavior to decide what to fix next.
Backups and rollback paths are part of the build, not an afterthought.
If you need help with gameplay systems, server setup, or infrastructure cleanup, reach out.
I can help with mechanics, Skript systems, and the infrastructure behind them from build to live ops.
Email Me