OPERATE
File manager
Browse, create, upload, and edit exposed files without racing the game process or damaging recoverable world data.
Files & Backupsv0.212 MIN
Save or stop the game before editing files
Save or stop the game and create a fresh backup before changing files it owns at runtime.
Navigate the exposed filesystem
The breadcrumb starts at the exposed root, which is intentionally narrower than the entire container filesystem.
Confirm the path before opening similarly named configuration filesAlways verify you are browsing the correct directory before making changes.
Use the editor only for supported text contentThe file editor is designed for safe text files; avoid binary or application-owned data.
Treat hidden files and generated manifests as application-owned stateGameplane manages internal metadata; changing these can break recovery and snapshot operations.
Create and upload content
New folders, new files, and uploads operate in the currently open directory.
Use valid names and verify the breadcrumb before confirmingEnsure the path is correct and the name follows the game's file naming conventions. Names can't contain "/" or be "." or ".."; a rejected name shows an inline error and Create stays disabled.
Include the correct extension and avoid accidental replacementAlways include the proper file extension to prevent overwriting or creating incompatible files.
Verify upload size, type, provenance, and ownership after completionConfirm the uploaded file has the expected size, format, and permissions. Uploaded files and mods are written group-readable, so the game process (same fsGroup, different user ID) can read them.
Delete folders from the tree (v0.3.0)Folder rows carry a delete button (shown on hover or focus on desktop, always visible on mobile). After a confirmation, deleting a folder permanently removes it and everything inside it. A folder holding dot-prefixed (hidden) entries is refused.
Edit safely and recover
Apply one concern, restart only when required, and validate Events and game logs before continuing.
Make one logical change at a timeIsolate each modification so you can identify which change caused a problem if needed.
Restart the server only after verifying the changeTest and validate changes before restarting the game to minimize downtime.
Review Events and logs immediately after changesCheck the console and system logs to confirm the change took effect and no errors occurred.
SAFE FILE CHANGE
01 01 Confirm breadcrumb and selected path
02 02 Save/stop and back up world or configuration data
03 03 Change one concern, restart if needed, validate logs, restore on failure