Configuration with Palworld - Palworld RCON/Admin Password Issues

[Anthony]

System Information

Field	Value
Operating System	Linux - Ubuntu 22.04.3 on x86_64
Product	AMP ‘Decadeus’ v2.4.8.0 (Mainline)
Virtualization	QEMU_KVM
Application	Palworld
Module	GenericModule
Running in Container	No
Current State	Ready

Problem Description

Issue

I have scheduled tasks on the Palworld server I run which are suppose to do various tasks via RCON, such as broadcast the restart schedule and broadcast restart warning messages via RCON, save prior to restart using RCON, then shutdown the server using RCON. Sometimes it works, but most of the time it does not. So I have the same scheduled task stop/start the app as a backup method. I can connect to RCON just fine and it mostly works when I use it via a terminal. It is just AMP scheduled task of sending RCON commands do not work most of the time.

I don’t know if this is related, but I cannot use /adminpassword in game either. The password works fine for RCON terminal, but not in game.

Any help?

Reproduction Steps

• Configured RCON Passthrough
• Used RCON Passthrough
• Configured RCON Scheduled Tasks

[YehnBeep]

Experiencing this too. Restarting the AMP instance fully (not just the Palworld app, the actual AMP controller) gets RCON working again temporarily.

So the problem seems to be AMP side. At some point, even though the Palworld server’s RCON works when connecting manually, AMP won’t do anything RCON related after a certain amount of time passes or perhaps other conditions happen.

Also, this topic has been indexed by search engines; if anyone has a solution, it would likely help others that might come searching about the same issue.

[Romaq]

A potentially relevant note: The Dedicated Server does NOT appear to read PalWorldSettings.ini. Change the password to your heart’s content… your change will simply be ignored.

The password the server actually reads is in WorldOption.sav. The world-around is to use something like https://pal-conf.bluefissure.com to make sure what you THINK your server is set to and what your server is ACTUALLY set to according to WorldOption.sav is the same thing… and then to BOTH. This should be considered a bug in my opinion, and I’d really like the Devs to fix this, preferably by renaming WorldOption.sav to WorldOption.bak and ignoring the damned thing henceforth. Could anyone please-dear-gawd pass this on to them?

[Greelan]

Delete WorldOption.sav to solve it

[Romaq]

Thank you, but when it wasn’t there, I couldn’t have over 15 pals in a base. Should I try again and see if the base pal limit is fixed? I’m ok with doing that, I just find the configuration situation horribly astonishing.

[Greelan]

I haven’t seen anything to suggest the base issue has been fixed. The only other alternative is to manually edit the .sav to match the settings you need.

Yes, Palworld is dumb

[Romaq]

Thank you. As I suspected it’s best to use a tool to read one, edit, keep both in sync to upload both. It would be a joy to come across a game where running it as a dedicated server wasn’t so completely… “astonishing.”