Upgrade Checklist

1.0 Private Server Upgrade Checklist

This is not a guaranteed template, but an operation sequence to reduce the risk of server explosion and data damage.

minimum process

Backup → Stop the service → Save a copy of the settings → Upgrade → Verify → Keep the rollback.

Data layer anchor point

Hierarchy	content	border
Confirm information	The current version of the official server docs is 0.7.2; the configuration table includes RESTAPIEnabled and RESTAPIPort. REST API is the officially supported server management port.	The docs will be upgraded after 1.0 goes online; 1.0 server fields cannot be claimed before the upgrade.
Strategy inference	1.0 is a major version update, and private server upgrades involve the superimposed risk of changes in setting fields, changes in Global Palbox switch default values, and complete Mod failure; it should be executed according to "Backup first, then upgrade, Mod deactivation and re-verification".	Applicable to dedicated servers and host mode; not applicable to official servers. Counterexample: If the 1.0 server field is fully backwards compatible, only the Mod risk holds.

Source: Official server docs (checked on 2026-07-06); after 1.0 goes online, use the upgraded docs to do a setting diff (setting difference) and then write back.

Before upgrade (backup four-piece set)

Back up world files
The only carrier of world terrain, base and guild data; the first thing to roll back the bottom line. open Backup player files
The rescue object in the case of character data disappearing; it is prepared separately from the world file and is indispensable for rollback. open Backup configuration file: `PalWorldSettings.ini` and startup parameters
When checking settings diffs after an upgrade, you need to know where the old values came from. open Record the current server version number and Mod list
Incident troubleshooting and rollback require knowing "which version to upgrade from." open Announce the server suspension window and stop players from writing
During the upgrade period, players cannot continue to enter and exit, causing half-write. open

Upgrading

Upgrade and start with naked server first
Mod is the highest risk source on the day of 1.0. Let’s eliminate the variables first. open Check Global Palbox import/export switch
Transfer rules affect player restart and retention strategies. open Check CrossplayPlatforms and player limit
Cross-platform and the number of people will directly affect whether players can enter the server. open

Verification (five small server verifications)

Live login, movement and transfer
Just seeing the process start does not mean that the player can play it. open Check base work, palbox and chest
After upgrading, make sure the core assets are readable and writable. open Trigger archive and confirm archive placement
Only if the timestamp of the archive directory is updated, it means that the write link is normal. open Exit and re-enter to confirm that the progress is still there
Being able to play and being able to save are two different things; losing progress after re-entry is a typical symptom of half-writing. open Long-running observations: memory, crashes and logs
Some problems only appear after continuous operation. Please run an observation period before starting the server. open Restore mods item by item and log failed items
Opening it all at once will make the source of the fault indistinguishable; uninstalling the Mod also risks damaging the archive, so verify on a backup copy first. open

rollback

Keep the pre-upgrade backup until player acceptance is complete
Don’t clear out the only available fallback point on day one. open Record version, setting differences and known issues for players
This result is required for subsequent patching, FAQ, and mod compatibility tracking. open

Acceptance criteria

Status	Can the server be opened?	Reason
Only complete backup	It cannot be opened to the outside world.	This only means that it can be rolled back, and it has not yet been verified that players can play it.
Login to naked server successfully	Only suitable for small-scale testing.	Mod, Palbox, cross-platform and base information have not yet been verified.
All checked and completed	Player acceptance can be entered.	Still need to keep a list of rollback points and known issues.

Incident handling: character information disappeared/required to seriously injure the character

After upgrading, if the player logs into the server and sees "Create New Character", or the character level, backpack, and Palbox are reset to zero, the first principle isSave the scene first and then troubleshoot. Doing it in the wrong order (create corner first, retry first) will make salvageable data unsalvageable.

order	action	why
1	Stop the server immediately and stop all players from writing.	If the half-written state continues to operate, the damage surface will only expand.
2	Don't create new roles.	The new character profile may overwrite the old player profile, which is the most common secondary damage.
3	Completely copy the current archive directory and save the accident scene.	All subsequent investigations will be done on the copy, and the official information will remain frozen.
4	Check on the dungeon whether the player file and the world file are complete or misaligned.	"The file exists but has not been read" and "the file is damaged" are two problems with different processing paths.
5	If the cause cannot be located, roll back to the four-piece backup set before the upgrade.	Bottom line for rollback: It’s better to lose a small amount of progress after the upgrade than to gamble on an unknown fix.

This paragraph does not promise that the file will be saved; third-party archiving tools can only be tested on backup copies and cannot be used as official safe paths.

Other bottom lines

situation	bottom line
Set generator output	It can only be used as a draft; after going online, you still need to check the parameter names and default values according to official documents or actual measurements.
Player acceptance	Five things must be looked at: real-person login, base work, save file placement, exit and re-entry, and long-term operation.

Applicable versionP1 route contract / P2 v2.0 content layer

Updated2026-07-06

SourceSPEC A5 / Official Server Documentation Baseline / A5 wiki Boundary Card

UpstreamConOps current focus: Palworld P2 content-layer rebuild