Skip to main content

Server Settings

Changing Settings via AI

The easiest way to change any server setting is to tell the AI what you want:
The AI modifies the correct config files (server.properties, spigot.yml, Paper configs, etc.) and applies changes — usually without needing a server restart.
For changes that require a restart (some server.properties values), the AI restarts the server automatically and lets you know.

Server Defaults

Your server comes pre-configured with these defaults:
Online Mode is off because authentication is handled by the Minekube Connect proxy layer. Players are still authenticated — it is not a cracked server.

Game Rules

Common game rules you can change through the AI. Just describe what you want in plain language: You do not need to remember the exact game rule names. Just describe the behavior you want and the AI translates it.

Configuration Files

The AI can modify any server configuration file. The most common ones:
Core Minecraft server settings: max players, difficulty, game mode, MOTD, world name, spawn protection, PvP toggle, and more.
Spigot-specific settings: entity activation range, mob spawn limits, item merge radius, and performance tuning.
Paper-specific optimizations and features: async chunk loading, anti-cheat settings, gameplay tweaks.
Player access control:

Data Persistence

All your server data is persistent — it survives server restarts and hibernation cycles. This includes:
World files (terrain, builds, player data)
Plugin configurations and data
Skript scripts and variables
Server settings and config files
Operator and whitelist entries
Nothing is lost when your server hibernates or restarts. Your world, plugins, scripts, and all settings are exactly as you left them.