Server Sync

Pro

Server Sync links your Minecraft server to LK Creator and pushes your generated packs directly — no manual download, no FTP client. It backs up what’s there, uploads, extracts and reloads the plugin, and tells you what the server answered.

Two ways to connect

SFTP / SSH

Host, port, username, and either a password or an SSH key. Works with any host that gives you SFTP access. On the first successful connection LK Creator remembers the server’s host key fingerprint, so a later change is caught instead of silently accepted.

Both live in Settings → Connections, where you can save up to 10 server profiles and test each connection before using it. Credentials are stored encrypted.

What a deploy does

Connect

LK Creator opens the connection with the profile you picked and resolves the destination folder for your plugin. You can override that folder per profile if your setup isn’t in the default location.

Back up

The current contents of the destination are backed up first, so there’s always something to roll back to.

Upload and extract

The pack is transferred and unpacked on the server.

Reload

If you enabled it, the plugin is reloaded and the server’s own answer is shown back to you.

Automatic reload, with the server’s answer

Enable Reload the plugin automatically on the profile and set your RCON port and password (the RCON host defaults to the server host). After each deploy the plugin is reloaded and you see what the server replied — ItemsAdder reports how many items it loaded, so you know the pack is live in-game and not merely uploaded. You can also override the reload command if your setup needs a different one.

A failed reload never undoes a deploy that worked. If the reload can’t run — wrong RCON password, port closed, no password saved — the pack stays deployed and you get a message telling you to reload it yourself.

Real progress

The deploy screen shows the stage it’s actually on (connect, backup, upload, extract, reload) and the bytes transferred, not a fixed animation. With large packs you can tell whether it’s moving or stuck.

Server status before you deploy

Each server profile shows whether it’s online, its version and how many players are connected, read before you touch anything. The status comes from a ping to the game port (25565 by default, per profile); if that fails and you have RCON configured, it falls back to asking the server directly.

Wait until the server is empty

Optional, per deploy: tick Wait until the server is empty and LK Creator checks the player count every 30 seconds and only deploys once nobody is connected, so the reload doesn’t lag anyone mid-session. It gives up after 15 minutes — and when it does, it reports the timeout without having touched your server.

Deploy history and rollback

Every deploy is recorded: when it ran, which pack, how it ended, and what the reload replied. Statuses are running, success, failed and rolled back. From that history you can roll back to any point, not just to the most recent deploy.

Only the last 2 backups are kept on the server, so rolling back to an entry older than that has nothing left to restore. The rollback tells you instead of restoring the wrong thing.

Deploy from your history

Any pack in your generation history can be deployed straight from there — no need to generate it again first. The pack file still has to be on our side: once its download window has passed and the file is cleaned up, the deploy asks you to regenerate instead.

Which plugins you can deploy to

Deploy targets ItemsAdder, Oraxen, Nexo and CraftEngine. MythicCrucible and HMCCosmetics packs can be generated and converted, but not deployed automatically — download those and install them yourself.

Good to know

Server Sync is Pro. On the Free plan you can always download your files and upload them manually. See Free vs Pro.
For large packs or a major migration, deploy to a staging server first.
Pair it with the Validator to confirm a pack is clean before you send it.