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.

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.

19 — ViaVersion — Compatibilitate versiuni

"

Jucătorii cu 1.19, 1.20.x se conectează la serverul 1.21 fără să facă nimic

#De ce e necesar

Serverul rulează PaperMC 1.21. Un prieten are Minecraft 1.20.4 și nu se poate conecta. ViaVersion rezolvă asta transparent — fără să cobori versiunea serverului, fără să ceri jucătorilor să upgradeze forțat.

#Familia Via — 3 pluginuri

PluginRolVersiuni suportate
ViaVersionCore — versiuni mai noi conectate1.21 → acceptă 1.21.x
ViaBackwardsVersiuni mai vechi conectateAcceptă 1.8 → 1.20.x
ViaRewindVersiuni foarte vechiAcceptă 1.7.x (rar necesar)
"

Recomandare pentru SMP: Instalează ViaVersion + ViaBackwards. Acoperă 99% din cazuri.

#Download

ViaVersion:   modrinth.com/plugin/viaversion   — gratis
ViaBackwards: modrinth.com/plugin/viabackwards  — gratis

#Instalare

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

# Verificare
docker compose logs mc | grep -i via
# Trebuie să apară: [ViaVersion] ViaVersion X.X.X enabled

#Config (ViaVersion)

# data/plugins/ViaVersion/config.yml

# Blochează versiunile prea vechi (opțional)
block-protocols:
  enabled: false    # true dacă vrei să blochezi sub 1.16

# Supresia warning-urilor de incompatibilitate
suppress-metadata-errors: true
suppress-conversion-warnings: false

# 1.9+ combat pentru jucătorii pe versiuni vechi
# (lasă default — nu schimba dacă nu știi ce faci)

#Versiuni acceptate după instalare

Client 1.21.x  → conectare directă (nativ)
Client 1.20.x  → ViaVersion (transparent)
Client 1.19.x  → ViaBackwards (transparent)
Client 1.18.x  → ViaBackwards (transparent)
Client 1.17.x  → ViaBackwards (transparent)
Client 1.16.x  → ViaBackwards (transparent)
Client sub 1.16 → ViaRewind (dacă instalezi)

#Limitări importante

  • Jucătorii pe versiuni mai vechi nu văd blocurile/itemele noi din 1.21 corect
  • Unele mechanic-uri noi din 1.21 pot comporta ciudat pe clienți 1.19
  • Nu afectează jucătorii pe 1.21 în niciun fel
  • Nu există impact pe gameplay pentru jucătorii pe versiunea corectă

#Mesaj recomandat pentru jucători

# Pune asta în #regulament pe Discord:

Serverul rulează pe Minecraft 1.21.
Poți juca și cu versiunile 1.16 → 1.20.x via ViaVersion,
dar recomandăm upgrade la 1.21 pentru experiență completă.

#Related Documents

  • System architecture → 01_system_architecture.md
  • Plugin stack → 02_plugin_architecture.md
~ End of Document ~
Kiwi