How to edit dropped-item maximum on a Palworld server?

Too many items on the ground and your server gasps? Set a proper dropped-item cap and take back control. In 5 minutes: change, save, restart, done.

Prerequisites

• Access to your Oxygenserv panel (username and password)
• Palworld server installed on Oxygenserv
• Know how to stop/start the server from the panel
• Optional: FTP access (FileZilla) if you prefer manual file edits
• A backup of PalWorldSettings.ini before changes

Detailed steps

1. Stop the server cleanly
   Log in to the Oxygenserv panel and open the Console or Dashboard. Click “Stop”. Wait for the log to confirm the process ended (e.g., “Server stopped”). Avoid force stop unless it hangs for ~60 seconds. Editing while running can cause your changes to be overwritten on next start.
2. Use the server settings editor to set the cap
   Go to “Files” then “Config Files” and open “Server Settings”. Find the DropItemMaxNum field (numeric). Enter a value between 0 and 10000 (example: type 1000). Click “Save” to persist the change. If that field isn’t available, use the manual edit in the next step.
3. Manually edit PalWorldSettings.ini if needed
   Open Pal/Saved/Config/WindowsServer/PalWorldSettings.ini via the file manager or FTP. Locate the line starting with OptionSettings=. Inside the parentheses, add or change the pair DropItemMaxNum=1000 (replace 1000 with your value), e.g., OptionSettings=(...,DropItemMaxNum=1000,...). Save the file. If the key already exists, do not duplicate it—replace the value to avoid the setting being ignored at startup.
4. Restart to apply
   Back to the Console, click “Start”. Watch the logs: when you see “Server started” and no config errors, you’re set. If the value resets, you likely edited the wrong file (do not edit DefaultPalWorldSettings.ini) or you have duplicate keys inside OptionSettings. Fix and restart again.
5. Test in-game and fine-tune
   Join the server and throw multiple stacks to simulate clutter. Watch performance and check if older items get cleared once the cap is reached (expected behavior). If you notice lag, lower DropItemMaxNum by 200–300 steps. If items vanish too aggressively, raise it gradually and restart between tests.

Tips & optimization

Start with 800–1200 for 10–20 players; go 1500–2000 for heavy farming, but monitor CPU/RAM. Avoid >3000 unless you’re confident—performance tanks fast. Pair it with a sensible lifetime, e.g., DropItemAliveMaxHours=0.5 to 1.0 to curb clutter. Keep a backup of PalWorldSettings.ini and your exact OptionSettings=... string to quickly reapply after updates. Change one setting at a time and test during peak hours.

FAQ

I can’t find DropItemMaxNum in the panel. Now what?

Edit Pal/Saved/Config/WindowsServer/PalWorldSettings.ini directly. In the OptionSettings= line, add DropItemMaxNum=... inside the parentheses, comma-separated. Example: OptionSettings=(...,DropItemMaxNum=1200,...). Save and restart.

My value resets after restart

You likely edited the wrong file (don’t touch DefaultPalWorldSettings.ini) or have duplicate DropItemMaxNum entries in OptionSettings. Stop the server, keep only one occurrence with your value, save, restart. Also confirm you clicked “Save” in the panel editor.

Do I need to restart for it to apply?

Yes. Palworld reads these settings on startup. Change, save, then restart. Without a restart, the new cap won’t be active.

You’ve just stabilized performance and your server’s economy. Keep tweaking smartly and you’ll stay smooth even when loot rains down.

Related articles

• Optimum configuration of a Palworld server: the PalWorldSettings.ini file
• How do I add mods to a Euro Truck Simulator 2 server?
• How do I connect to a 7 Days to Die server using Telnet?