xNul / palworld-host-save-fix

Fixes the bug which forces a player to create a new character when they already have a save. Useful for migrating maps from co-op to dedicated servers and from one dedicated server to another.
MIT License
886 stars 65 forks source link

Lost access to base #139

Closed CdubZzzz closed 5 months ago

CdubZzzz commented 5 months ago

We used this tool, the old Coop host now has his character working. However his palbox says, this belongs to another guild. No longer has his base. Is there a fix for this?

CdubZzzz commented 5 months ago

We fixed it by having the coop host join a guild with another player. Then we kicked the host from the guild, so the other player owned everything. Then we saved and used the script and transferred the world to a dedicated server. Once on the server, the host player joined the guild again and then the other player left the guild. Basically make the server swap, while the host owns nothing. Then give him back the stuff on the server.

CdubZzzz commented 5 months ago

I don't see how to delete this post, there is already a similar post.

xNul commented 5 months ago

Yep, that's the guild bug workaround. It's already known and included in the instructions for co-op to Windows dedicated server. Here, I'll close it for you.

CdubZzzz commented 5 months ago

Yeah, that was the fix. But entering true in Python didn't work. And the host was never in a guild to begin with. But yeah that was the same fix

On Sun, Feb 4, 2024, 1:17 AM Blake Wyatt @.***> wrote:

Yep, that's the guild bug workaround. It's already known and included in the instructions for co-op to Windows dedicated server. Here, I'll close it for you.

— Reply to this email directly, view it on GitHub https://github.com/xNul/palworld-host-save-fix/issues/139#issuecomment-1925652148, or unsubscribe https://github.com/notifications/unsubscribe-auth/BF3SD3GE4HYEOM4GBUPCYQLYR5GZVAVCNFSM6AAAAABCYUIUTWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRVGY2TEMJUHA . You are receiving this because you authored the thread.Message ID: @.***>