Skip to content
←Return to Projects
Case Study

IceLegends SMP

A vanilla-first Romanian Minecraft SMP built for clean 3–4 month seasons.

The Problem

Running a community SMP means balancing plugin depth against vanilla feel, managing a world-reset cycle, and keeping operations simple enough for a solo admin. IceLegends SMP solves this with 11 carefully chosen plugins, strict feature gating per a "vanilla-first" principle, and fully automated backups and world resets.

My Role

Designed, configured, and deployed solo — server architecture, 11-plugin selection and configuration, LuckPerms permission model, economy and nation design, Docker infrastructure, and Cloudflare Tunnel ingress for Dynmap.

Join the Server ↗

Highlights

  • PaperMC 1.21 on Docker with a hard 11-plugin cap — every plugin is justified and none are redundant
  • Towny nations with seasonal quests (Quests + Citizens NPCs) and a single manually-spawned MythicMobs boss per season
  • AureliumSkills passive bonuses only — active abilities disabled to preserve vanilla combat (P-01)
  • DiscordSRV bridge logs every death, join, and chat event to dedicated Discord channels in real time
  • Daily automated backups with 7-day retention; resource world resets every Monday at 05:00 via cron

Stack

PaperMC 1.21DockerCloudflare TunnelLuckPermsTownyAureliumSkillsMythicMobsDiscordSRVDynmap

Constraints

  • Solo admin — every operation must complete in under 10 minutes (P-02).
  • Vanilla-first (P-01): if any plugin disappeared tomorrow, the game must continue unchanged.
  • 11-plugin hard cap — every addition must displace something or prove unique, irreplaceable value.

System Architecture

Edge
Cloudflare Tunnel (Dynmap web map)
TCP :25565 open (Minecraft clients)
Runtime
Docker + docker-compose
itzg/minecraft-server image
Core
PaperMC 1.21
Vault
LuckPerms
EssentialsX
CoreProtect
Gameplay
Towny
AureliumSkills
ShopGUI+
Quests + Citizens
MythicMobs
Multiverse-Core
Ops
DiscordSRV bridge
Daily backup cron (04:00)
Weekly world reset cron (Mon 05:00)

Key Trade-offs

The decisions worth defending — what I chose, what I turned down, and why.

Plugin count cap

Chose

Hard cap at 11 plugins

Rejected

Unlimited plugin stack

Each plugin is a maintenance surface and a potential conflict point. The cap forces prioritisation and keeps the dependency graph legible for a solo admin.

Public ingress for Dynmap

Chose

Cloudflare Tunnel (no open ports)

Rejected

Expose :8123 directly via UFW

No origin IP exposure, free DDoS protection, and zero firewall rule maintenance — the same pattern used by the IceLegends portfolio site.

AureliumSkills scope

Chose

Passive bonuses only, active abilities disabled

Rejected

Full AureliumSkills feature set including active combat abilities

Active abilities alter vanilla combat — a direct violation of P-01. Passive bonuses reward playtime additively without changing the combat model.

Season lifecycle

Chose

Full world reset every 3–4 months

Rejected

Incremental map expansion with no reset

Resets keep the world fresh, prevent terrain exhaustion, and give every new player an equal start — critical for community health in a small SMP.

What I'd Do Differently

An honest retrospective — the stuff I'd change with more time, more users, or a second pass.

  1. 1Add a staging compose stack so plugin updates can be tested before touching the live season — one bad update cost several hours of rollback work.
  2. 2Move backup storage off-site from day one; local-only archives are a single hardware failure away from a full season loss.
  3. 3Wire Dynmap as a named Docker service rather than relying on the host port, so the Cloudflare Tunnel config survives container IP reassignment on restart.

Technical Deep-Dive

Architecture, specifications, and implementation details.

20 — Plan — Player Analytics

"

Dashboard web cu statistici detaliate despre jucătorii tăi

#De ce e necesar

Fără Plan nu știi:

  • Câți jucători unici ai avut în ultimele 7 zile
  • La ce oră sunt cei mai mulți jucători online
  • Cine a stat cel mai mult pe server
  • Când au plecat jucătorii și de ce (corelezi cu events)

Plan îți dă toate astea într-un dashboard web accesibil via browser.

#Download

Sursă:   github.com/plan-player-analytics/Plan
Licență: LGPL-3.0 — gratis
Impact vanilla: zero

#Instalare

cp Plan-*.jar data/plugins/
docker compose restart mc

# Plan pornește un web server intern pe portul 8804
# Expune via Cloudflare Tunnel (similar cu Dynmap)

#Cloudflare Tunnel pentru Plan

# În Cloudflare Zero Trust Dashboard:
# Adaugă un nou Public Hostname:
# stats.serverultau.ro → http://mc:8804

# În docker-compose.yml — cloudflared primește ambele rute
# automat prin același tunnel token

#Ce vezi în dashboard

SecțiuneInformații
OverviewJucători online acum, peak zilnic, sesiuni totale
PlayersTimp jucat per jucător, ultima conectare, locație geografică
SessionsGrafic activitate pe ore și zile ale săptămânii
ServerTPS history, RAM usage, performance trends
GeolocationsHarta de unde se conectează jucătorii

#Config cheie

# data/plugins/Plan/config.yml

Webserver:
  Port: 8804
  # Accesibil via Cloudflare Tunnel — nu deschide în UFW

Database:
  Type: SQLite    # suficient pentru un SMP mic
  # MySQL disponibil dacă crești

Display:
  Time_zone: Europe/Bucharest
  Language: Romanian    # dacă există, altfel English

#Permisiuni LuckPerms

# Admin și Moderator văd dashboardul complet
/lp group moderator permission set plan.inspect.other true
/lp group admin permission set plan.* true

# Jucătorii văd doar profilul propriu (opțional)
/lp group jucator permission set plan.inspect.own true

#Utilizare practică

# Link dashboard admin
https://stats.serverultau.ro

# Link profil jucător specific
/plan inspect NumeJucator   # generează link direct

# Export CSV pentru analiză externă
/plan export players

#Related Documents

  • Discord observability → 10_discord_integration.md
  • Performance monitoring → 13_performance.md
  • Season analytics → 15_season_lifecycle.md
~ End of Document ~
Kiwi