Survival Minecraft Server Configuration
Budget: $30 – $250 USD
Hi! I run a Minecraft server that currently relies heavily on Skript-based custom features and several existing plugins. I recently joined another server that feels like a "perfected version" of what I’m trying to build — smoother, more polished, and better optimized. I need a Minecraft server specialist who can:
Audit & Replicate — Join the reference server (IP provided via PM), identify what plugins, configurations, and mechanics they use to achieve that level of polish, and replicate the relevant setup on my server.
Build from Scratch — Set up a complete survival-mode server from zero, optimized for 100–200 concurrent players with zero lag spikes.
Preserve & Optimize Existing Features — Several custom features and systems already exist on my current server and must be preserved, not deleted. Your job is to migrate, refactor, or optimize them so they run lighter and more stable on the new stack.
Scope of Work
A. Reference Server Investigation
Join the target server (IP sent via PM) and document what plugins / systems create the smooth gameplay experience.
Identify their anti-cheat, economy, chat, permission, world-protection, and QoL plugins.
Provide a written report of findings + recommendation on which ones fit my server vision.
B. Core Server Setup
Install and configure Paper (or Purpur if you recommend it for 100–200 players) on my VPS/dedicated host.
Install, configure, and test:
EssentialsX (chat, economy, teleport, warps, kits)
WorldEdit (build team tools)
LuckPerms (permission hierarchy)
WorldGuard (spawn protection & region flags)
Fine-tune spigot.yml, paper-global.yml, paper-world.yml, bukkit.yml:
View distance, simulation distance, entity limits, mob spawning
Tick timings, async settings, chunk loading
JVM flags (G1GC tuning, heap size, etc.)
Run a stress test / benchmark simulating 100+ players (or show proof of past high-population setup).
C. Existing Feature Preservation & Optimization
Audit my current server (configs, Skript files, plugin data) and identify which features must be kept.
Migrate or refactor existing custom features so they work on the new server stack without breaking.
Optimize existing Skripts / plugin configs for lower CPU/RAM usage — replace heavy loops with event-driven logic, reduce unnecessary broadcasts, consolidate repeated tasks, etc.
Do NOT delete or overwrite any existing player data, economy balances, warps, homes, or custom mechanics unless explicitly approved by me.
If an existing feature is too heavy to keep as-is, propose a lightweight replacement or rewrite before making changes.
D. Optimization & Extras
Recommend and install lightweight optimization plugins (e.g., FarmControl, Chunky for pre-generation, etc.) — only if they genuinely help sustain player load.
Configure basic anti-cheat (e.g., Vulcan or GrimAC) if not already covered.
Set up automatic backups (via plugin or cron script).
E. Documentation
A short README covering:
How to safely restart the server
How to update plugins without breaking configs
How to restore from backup
Basic LuckPerms command cheat-sheet
List of preserved features and where their configs live
Deliverables
[ ] Fully operational survival server on my host, ready for public launch
[ ] Plugin audit report from the reference server
[ ] Migration report: list of preserved features + what was optimized vs. replaced
[ ] All configs tested and documented
[ ] Stress-test proof or benchmark screenshot
[ ] Restart / update / backup README
[ ] 7-day post-launch support (bug fixes & minor tweaks)
Requirements
Proven experience setting up Paper/Purpur servers for 100+ concurrent players
Strong knowledge of Skript (reading, debugging, optimizing existing scripts is mandatory)
Comfortable with Linux VPS management (SSH, screen/tmux, systemd service)
Fluent English or Indonesian communication
Attention to detail: you must ask before deleting any existing feature or player data
Budget & Timeline
Budget range: Will be discussed via PM
Timeline: Will be discussed via PM
Payment: Milestone-based (50% upfront, 50% after delivery + test)
Audit & Replicate — Join the reference server (IP provided via PM), identify what plugins, configurations, and mechanics they use to achieve that level of polish, and replicate the relevant setup on my server.
Build from Scratch — Set up a complete survival-mode server from zero, optimized for 100–200 concurrent players with zero lag spikes.
Preserve & Optimize Existing Features — Several custom features and systems already exist on my current server and must be preserved, not deleted. Your job is to migrate, refactor, or optimize them so they run lighter and more stable on the new stack.
Scope of Work
A. Reference Server Investigation
Join the target server (IP sent via PM) and document what plugins / systems create the smooth gameplay experience.
Identify their anti-cheat, economy, chat, permission, world-protection, and QoL plugins.
Provide a written report of findings + recommendation on which ones fit my server vision.
B. Core Server Setup
Install and configure Paper (or Purpur if you recommend it for 100–200 players) on my VPS/dedicated host.
Install, configure, and test:
EssentialsX (chat, economy, teleport, warps, kits)
WorldEdit (build team tools)
LuckPerms (permission hierarchy)
WorldGuard (spawn protection & region flags)
Fine-tune spigot.yml, paper-global.yml, paper-world.yml, bukkit.yml:
View distance, simulation distance, entity limits, mob spawning
Tick timings, async settings, chunk loading
JVM flags (G1GC tuning, heap size, etc.)
Run a stress test / benchmark simulating 100+ players (or show proof of past high-population setup).
C. Existing Feature Preservation & Optimization
Audit my current server (configs, Skript files, plugin data) and identify which features must be kept.
Migrate or refactor existing custom features so they work on the new server stack without breaking.
Optimize existing Skripts / plugin configs for lower CPU/RAM usage — replace heavy loops with event-driven logic, reduce unnecessary broadcasts, consolidate repeated tasks, etc.
Do NOT delete or overwrite any existing player data, economy balances, warps, homes, or custom mechanics unless explicitly approved by me.
If an existing feature is too heavy to keep as-is, propose a lightweight replacement or rewrite before making changes.
D. Optimization & Extras
Recommend and install lightweight optimization plugins (e.g., FarmControl, Chunky for pre-generation, etc.) — only if they genuinely help sustain player load.
Configure basic anti-cheat (e.g., Vulcan or GrimAC) if not already covered.
Set up automatic backups (via plugin or cron script).
E. Documentation
A short README covering:
How to safely restart the server
How to update plugins without breaking configs
How to restore from backup
Basic LuckPerms command cheat-sheet
List of preserved features and where their configs live
Deliverables
[ ] Fully operational survival server on my host, ready for public launch
[ ] Plugin audit report from the reference server
[ ] Migration report: list of preserved features + what was optimized vs. replaced
[ ] All configs tested and documented
[ ] Stress-test proof or benchmark screenshot
[ ] Restart / update / backup README
[ ] 7-day post-launch support (bug fixes & minor tweaks)
Requirements
Proven experience setting up Paper/Purpur servers for 100+ concurrent players
Strong knowledge of Skript (reading, debugging, optimizing existing scripts is mandatory)
Comfortable with Linux VPS management (SSH, screen/tmux, systemd service)
Fluent English or Indonesian communication
Attention to detail: you must ask before deleting any existing feature or player data
Budget & Timeline
Budget range: Will be discussed via PM
Timeline: Will be discussed via PM
Payment: Milestone-based (50% upfront, 50% after delivery + test)
Related categories:
PHP
Linux
WordPress
Apache
VPS
Game Development
Documentation
Minecraft
Performance Tuning