First startup and connection

Startup sequence

Run the script from the server folder. Paperclip may download runtime components; allow network access and time to finish.
A licensed distribution verifies authorization before opening worlds. Follow license setup if it stops here. Later files may not yet exist.
Read the Minecraft EULA. If the owner agrees, change eula=false to eula=true in the generated eula.txt, then start again.
Wait for the server-ready message. A live Java process alone does not prove startup is complete.

Generated files

File or directory	Purpose
`server.properties`	Minecraft settings, including port and world name
`eula.txt`	The owner’s EULA acceptance
`nusa-global.yml`, `nusa-world.yml`	Nusa configuration
`plugins/`	Plugin JARs and data
`logs/`	Operating logs; review and redact before sharing
World directories	Worlds/dimensions loaded by your configuration
`config/`, `bukkit.yml`, `spigot.yml`	Existing Paper/Bukkit/Spigot configuration

Existing Nusa config files are preserved. Missing keys use implementation defaults; deleting the files is not an update procedure.

Basic connection settings

While stopped, review server.properties:

server-ip= normally stays empty; follow your panel allocation when applicable.
server-port=25565 is the standard game port; use a different allocated port if needed.
level-name=world names the main world.
online-mode=true validates accounts for a directly accessible server. Proxy authentication requires a correctly secured forwarding setup.
view-distance and simulation-distance affect load; measure before tuning.

See the Paper properties reference for further details.

Test and stop

Use a 1.21.11 client. On the same machine, localhost:25565 works if the port is unchanged. Remote players need the assigned reachable address and port; a local address is not an external connection address.

Test movement, inventory, block interaction, leaving, and reconnecting. Run stop and check for save errors. Continue with setup or connection troubleshooting.