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.

31 — Bounty System — Recompense pe Jucători

"

Pui recompensă pe dușmanul tău din Towny — rivalitate organică

#De ce e interesant

Bounty System transformă conflictele Towny în ceva mai profund. Când o națiune câștigă un war, perdanții pun bounty pe liderul lor. Oricine îl omoară primește recompensa. Creează tensiune și povești organice.

#Download

Sursă:   spigotmc.org (caută "Bounties" sau "BountyHunters")
Alternativă: github.com/body-guard/Bounties
Licență: Gratis
Impact vanilla: zero — doar economie și PvP existent
Dependință: Vault

#Cum funcționează

1. Jucătorul A pune bounty pe Jucătorul B: /bounty set B 500
2. 500 coins sunt reținuți din contul lui A
3. Toți jucătorii văd bounty-ul în /bounty list
4. Jucătorul C îl omoară pe B → primește 500 coins automat
5. Anunț pe tot serverul: "C a colectat bounty-ul de 500⛃ pe B!"
6. Anunț în Discord #chat-minecraft via DiscordSRV

#Config

# data/plugins/Bounties/config.yml

# Bounty minim și maxim
min-bounty: 100       # minim 100 coins — nu spam cu 1 coin
max-bounty: 10000     # maxim 10k — nu domină economia

# Durata bounty-ului
bounty-duration: 72   # ore — expiră după 3 zile
refund-on-expiry: 80  # returnează 80% din coins la expirare

# Tax pe bounty (sink de economie)
bounty-tax: 10        # 10% merge la "stat" — sink economic

# Protecție anti-abuse
same-player-cooldown: 24    # nu poți pune bounty pe același om de 2x în 24h
death-cooldown: 5            # minute de protecție după ce ești omorât

# Anunțuri
broadcast-on-place:  true
broadcast-on-collect: true
discord-webhook: ""   # completezi cu webhook-ul din Discord

# Format mesaje în română
messages:
  bounty-placed:    "&c[Bounty] &7{placer} a pus &c{amount}⛃ &7pe capul lui &c{target}!"
  bounty-collected: "&6[Bounty] &7{killer} a colectat &6{amount}⛃ &7pentru capul lui &c{target}!"
  bounty-expired:   "&7[Bounty] Prețul pe capul lui &c{target} &7a expirat."

#Comenzi

# Jucători
/bounty set <player> <amount>   # Pune bounty
/bounty list                     # Lista tuturor bounty-urilor active
/bounty info <player>            # Bounty-ul pe un jucător specific
/bounty remove <player>          # Retrage bounty-ul tău (cu penalitate)

# Admin
/bounty admin clear <player>    # Șterge orice bounty
/bounty admin list              # Toate bounty-urile din server

#Permisiuni LuckPerms

/lp group jucator permission set bounties.place true
/lp group jucator permission set bounties.list true
/lp group jucator permission set bounties.info true
/lp group moderator permission set bounties.admin true

#Integrare cu Towny Wars

Scenariul clasic:
1. Națiunea NORD declară war pe SUD
2. NORD câștigă — cuceresc 3 teritorii
3. Liderul SUDULUI pune bounty 2000⛃ pe Regele NORDULUI
4. Un mercenar neutru îl vânează pentru recompensă
5. NORDUL pierde un teritoriu înapoi la pace
→ Economie, politică, PvP — totul conectat organic

#Leaderboard Bounty Hunters

# Via DecentHolograms la spawn
/dh create bounty-board
/dh addline bounty-board "&c&l◆ Top Bounty Hunters ◆"
/dh addline bounty-board "&71. {bounty_top_1_name}: {bounty_top_1_collected}⛃"
/dh addline bounty-board "&72. {bounty_top_2_name}: {bounty_top_2_collected}⛃"

#Related Documents

  • Towny Wars → 04_towny_nations.md
  • Economy → 03_economy_design.md
  • Discord alerts → 10_discord_integration.md
~ End of Document ~
Kiwi