Beginner Windrose server admin guide for new owners

This beginner Windrose server admin guide walks you through everything you need to do in your first day of running a Windrose server: picking the right plan, getting players connected with an invite code, organising your files, configuring backups, adding mods safely, and avoiding the mistakes that cost new admins their world. It is written for people who have just rented a server and want a clear, technical checklist rather than a marketing tour.

Prerequisites

• An active Windrose server plan (Explorer 4 GB through World Architect 18 GB on PLAYERTICK)
• Access to the PLAYERTICK control panel
• A copy of Windrose installed on your PC for testing the connection
• An SFTP client such as FileZilla or WinSCP for file uploads
• A text editor that handles Unix line endings, like VS Code or Notepad++
• A Discord account if you want community support via the PLAYERTICK Discord

Step 1 — Choose a plan that matches your player count

The biggest mistake new admins make is under-buying RAM, then blaming the host when chunks load slowly or mods crash on startup. Match your plan to realistic peak players, not the average:

If you plan to install mods at all, skip Explorer. Modded Windrose worlds use considerably more memory than vanilla because every loaded mod adds entities, recipes, and persistent world data. A 4 GB box can boot a small modpack but will struggle the moment a second player joins and starts loading new chunks.

Tip: it is cheaper to upgrade than to downgrade. Start one tier higher than you think you need for the first month, then drop down once you have real player numbers.

Step 2 — First boot and the invite code

Windrose servers on PLAYERTICK do not use a traditional IP and port for player connections. On first startup, the server generates an invite code that players paste into the game client. This is the single most important thing to grab from your control panel after the first launch.

1. Log in to the control panel and open your server
2. Click Start and wait for the console to settle (look for the line confirming the world has loaded)
3. Copy the invite code shown in the server overview or console output
4. Share it only with people you trust — anyone with the code can join

To connect from the game:

1. Open Windrose
2. Go to Play → Connect to Server
3. Paste the invite code and confirm

If the code does not appear after a successful boot, restart the server once. The code is generated during world initialisation, and a partial first boot can skip that step.

Step 3 — Learn your file layout

Use SFTP from day one. The web file manager is fine for quick edits, but SFTP is faster for bulk changes and lets you keep local backups of your config.

A typical Windrose server directory looks roughly like this:

/home/container/
├── server/                # core game files
├── world/                 # your saved world data
├── mods/                  # server-side mods (if used)
├── config/                # mod and server config files
├── logs/                  # rotating log files
└── backups/               # local backups (host-managed)

The two folders you will touch most often are world/ and config/. Treat server/ as read-only unless you know exactly what you are changing — overwriting a binary or core asset will brick your install and force a reinstall from the panel.

Connecting over SFTP

Your panel will list the SFTP host, port, and username. Use your panel password.

# Example FileZilla quick-connect
Host:     sftp://nl-01.playertick.com
Port:     2022
User:     yourpaneluser.serverid
Password: <your panel password>

Always download a copy of any file before editing it. If a config change breaks the server, you want a one-click rollback rather than guessing what a default value used to be.

Step 4 — Configure backups before you need them

Backups are the single setting that separates a server you can recover from one you cannot. PLAYERTICK plans include automatic backups, but you should still verify the schedule and add a manual backup before any major change.

A sensible backup policy for a small community server:

• One automatic daily backup retained for 7 days
• One manual backup before installing or updating any mod
• One manual backup before letting a new admin near the world

Take a manual backup from the panel any time you are about to:

• Install or remove a mod
• Edit a config file you do not fully understand
• Run a world-wide command (resets, regen, mass deletions)
• Update the server to a new game version

If you ever need to roll back, restore from the panel, then restart the server. Do not try to merge a backup with a live world by hand — Windrose stores world state in a way that does not tolerate partial overwrites.

Step 5 — Tune day-one server settings

After the first boot, a config directory will exist with the defaults the game wrote on startup. Stop the server before editing anything; live edits will be overwritten when the server saves.

Common values worth reviewing on a fresh install:

• Server name — make it recognisable in your panel and in-game
• Player slot limit — set this no higher than your plan's recommended player count
• PvP toggle — decide before opening to players; flipping it later causes drama
• Difficulty — pick one and stick with it for the season
• Auto-save interval — leave at the default unless you have a specific reason to change it

A minimal example of the kind of configuration file you will edit (your real filenames may differ between game updates):

server_name = My Windrose Server
max_players = 10
pvp_enabled = false
difficulty = normal
autosave_minutes = 5

Save the file with Unix (LF) line endings. Windows-style CRLF endings will silently break some parsers and leave you with a server that boots but ignores your changes.

Step 6 — Install mods the safe way

Windrose supports server-side customisation and modding through file uploads. The safe workflow is the same every time:

1. Stop the server from the panel
2. Take a manual backup
3. Upload the mod files to the mods/ directory over SFTP
4. Upload any required config files to config/
5. Start the server and watch the console for errors
6. Test with one client before sharing the invite code

If the server fails to boot:

• Read the last 50 lines of the log — most mod load failures name the offending file
• Remove the most recently added mod and try again
• Check the mod's documentation for required dependencies or framework versions
• Verify that the mod is built for your current server version

Warning: never install a mod a player sends you privately without checking its source. Server-side mods run with full access to your world files.

Keep a plain text file on your local machine listing every mod, its version, and where you downloaded it. When a mod update breaks the server six months from now, you will need that list.

Step 7 — Day-to-day admin habits

The owners whose servers stay healthy do small things consistently:

• Restart the server once a day during off-peak hours to clear memory
• Check the console for warnings after every restart, not just errors
• Review backup retention weekly so you know your safety net is real
• Keep a changelog of every config or mod change with the date
• Rotate or archive logs before they fill the disk on smaller plans

A simple changelog format that pays for itself the first time something breaks:

- date: 2026-04-20
  change: Increased max_players from 10 to 15
  reason: New community members joining
- date: 2026-04-22
  change: Installed exampleMod v1.4.2
  reason: Requested by players for extra recipes
- date: 2026-04-23
  change: Rolled back exampleMod to v1.4.1
  reason: 1.4.2 caused crash on world load

Troubleshooting

If a fix is not obvious from the logs, open a support ticket with the exact timestamp of the failure, the last 100 lines of console output, and a list of any changes you made in the previous 24 hours. That is what staff need to diagnose the problem quickly.

Next steps

• Read the PLAYERTICK guides hub for game-specific tutorials as they are published
• Bookmark the status page and subscribe to incident notifications
• Join the PLAYERTICK Discord to ask other Windrose admins for advice
• Set up a private staff channel for your own community before opening to the public
• Document your mod list and config changes in a shared place so a co-admin can take over if you are away