BisectHosting Palworld: Change XP Gain Without Editing the Wrong File

01 The current BisectHosting panel path

In BisectHosting Starbase, stop the server, open Settings → Palworld Settings, change XP Rate Multiplier, save if prompted, then start the server. BisectHosting’s current XP-rate instructions ↗ say the field affects both player and Pal XP. Labels may differ in older panels, so match the instructions to the Starbase version you actually use.

Before changing progression, export a backup and record the old value. Discuss the desired pace with your group. Increasing experience may help a returning group, but a larger number is not inherently better; the useful setting is the one that fits your intended playthrough.

02 What ExpRate changes, and how to edit it manually

Pocketpair identifies ExpRate as the experience multiplier. For a manually managed installation, it belongs inside the existing OptionSettings=(...) content in the active PalWorldSettings.ini. For example, changing the existing entry to ExpRate=2.000000 expresses a 2× multiplier; it is an example preference, not an optimization recommendation.

Edit the relevant Pal/Saved/Config/LinuxServer/PalWorldSettings.ini or WindowsServer/PalWorldSettings.ini. Do not edit only DefaultPalWorldSettings.ini and expect an existing server to adopt the change. Do not replace the entire OptionSettings line with this one token: you would discard other values. The configuration path and parameter are documented by Pocketpair ↗.

03 The multiplier changed back after restart

On managed hosting, the panel can generate configuration from its own saved fields. Prefer its documented XP field instead of making conflicting edits through both the panel and raw files. After stopping, saving and restarting once, read the active file or panel value again. If it reverts, identify the generating source with support rather than repeatedly editing DefaultPalWorldSettings.ini.

For a manual server, check that you edited the running instance’s directory, not an old installation. Look for a duplicate ExpRate entry, an incomplete OptionSettings line or a file saved to the wrong OS directory. Record the original configuration and change one field at a time; a whole downloaded template can introduce several unrelated differences at once.

04 Verify future XP, then plan your rollback

1. Record the configured value and a player’s current XP.
2. Restart cleanly and perform a repeatable activity with comparable conditions.
3. Check that future experience follows the intended pace; do not compare unlike tasks or promise a fixed XP award.
4. Check a Pal’s progression too, because the host documents a shared multiplier.
5. If the pace is wrong, restore the previous setting and restart again.

Lowering the multiplier does not automatically remove levels already earned. Reverting player progress requires restoring an earlier world/player snapshot, which can also remove everyone’s later changes. Agree on that tradeoff before using a backup as a rollback. For a full export procedure, see saving a BisectHosting world.