Folder and start scripts
Run the JAR from a dedicated folder with a heap that fits your allocation.
Prepare the folder and memory
Create a writable folder, such as NusaServer. Put the official distribution inside and rename it to nusa-paperclip.jar to use these examples. Avoid system folders or synchronization tools that can lock world files.
Heap is memory managed by Java. -Xms1G selects a 1 GiB initial heap and -Xmx2G a 2 GiB maximum. These are initial-check examples, not production sizing. Leave memory outside the heap for the OS, native allocations, buffers, panel, and other processes. Do not set Xmx equal to the entire container limit.
Windows: start.bat
Save this beside the JAR:
@echo off
cd /d "%~dp0"
java -Xms1G -Xmx2G -jar nusa-paperclip.jar --nogui
pauseDouble-click it or run it from a terminal. pause keeps errors visible after Java exits. Replace java with a quoted full executable path if necessary.
Linux: start.sh
#!/usr/bin/env sh
cd -- "$(dirname -- "$0")" || exit 1
exec java -Xms1G -Xmx2G -jar nusa-paperclip.jar --noguiRun chmod +x start.sh, then ./start.sh. A service or terminal session manager can keep it running after SSH disconnects. Preserve the working directory and use a dedicated service account.
Stop cleanly
Enter stop in the console or /stop in game with administrative access. Wait for Java to exit. Do not close the window or kill the process while it saves. Continue with first startup.