Palworld Guilds: Shared Bases, Pals and Player Progress
See what a Palworld guild shares, what to confirm before joining, and which official server settings control guild and base limits.
You will need
- Access to the Palworld multiplayer world
- Agreement about who can use shared guild bases and storage
A Palworld guild is the game’s way to give friends shared access to bases and some base resources. Joining one does not mean every character detail becomes shared, and the official server guide does not document every personal-save rule. Before building together, agree on which bases and stored items everyone can use, and check the current game before moving a Pal or leaving a guild.
This guide separates the sharing rules current player guides describe from the limits Pocketpair documents for dedicated servers. It does not claim a hands-on test of guild transfer, leaving, or kicking behavior.
What a Palworld guild shares#
Think of a guild as a shared base group inside one multiplayer world. Current guides describe members using the guild’s bases, production stations, storage, and Pals assigned to those bases. That is different from saying every player’s character, inventory, or complete Pal collection becomes one shared account.
| Area | Safe way to think about it | Evidence boundary |
|---|---|---|
| Guild bases and structures | Members can work from the group’s shared bases | Community guides describe this behavior; Pocketpair’s server docs expose the base limit, not a full access matrix |
| Base workers and production | Other members may interact with Pals assigned to guild bases and the resources they produce | Keep Pals you want private out of shared base slots; confirm the current UI before moving them |
| Personal Pal storage | Treat each player’s regular Palbox roster as personal unless the game clearly shows a guild-sharing feature | Current guides distinguish personal storage from base workers; exact edge cases are not fully specified by official docs |
| Levels, technology, map and inventory | Do not assume another member’s progress or belongings transfer to you | Official configuration docs do not define these character-level rules; guides vary in detail |
| The world save | Everyone plays in the same world, but a co-op host or server still owns the save location | A guild does not move the world file to every member’s device |
The Palworld.tools guild guide and Palworld Database’s create-and-join guide explain everyday guild interactions, while Gamers.Wiki’s guild roles and leaving guide separates shared base assets from personal progress and flags several unresolved edge cases. These are secondary guides. Pocketpair’s official server configuration reference covers configurable limits, but it does not publish a complete list of what a player keeps after leaving or being removed.
Join only after agreeing on shared access#
For a friends’ world, have the group decide whether members should build under one guild before anyone places a base. The current guides describe inviting a player from the in-game interaction while everyone is in the same world. The menu wording may differ by platform or update, so check the prompt shown in your current build instead of relying on an old screenshot.
Before accepting, agree on three practical points:
- Which bases are shared? Members may have access to guild structures and base work, so do not assume a building is private just because one person placed it.
- Which Pals can be assigned to base work? Keep a Pal in personal storage if you do not want it used at a shared base, and check what the current game lets other members do.
- Who can make large changes? Pick a simple rule for moving structures, using shared materials, and changing server settings.
The v1.0.4 notes fixed a previous co-op issue where a joining player might not enter the host’s guild, along with a chest-permission issue. Pocketpair’s v1.0.5 notes list no later guild-specific change in the notes checked for this guide. If a current session behaves unexpectedly, first confirm that everyone has the same game build and is in the intended world before changing save files.
Keep personal progress and guild access separate#
The word progress can mean several things: a shared base, a player’s level, their Technology unlocks, explored map, inventory, or the Pals they have captured. A shared world does not prove that every one of those records is shared between guild members.
Use a cautious rule for important items: treat character inventory and personal progression as belonging to the individual until the current game explicitly shows otherwise. Keep a separate world backup before testing unusual membership changes. Do not leave or remove a member to discover what happens to their base Pals or character records; the exact retention and rollback behavior is not fully documented in Pocketpair’s public configuration guide.
For a group deciding whether to share one base or let each player build separately, Palworld for two covers the scheduling and shared-base conversation for a duo. If you are still choosing between co-op and a dedicated world, the multiplayer overview explains who keeps the world running and where its save lives.
Check the guild and base limits on a dedicated server#
Pocketpair’s current configuration reference lists GuildPlayerMaxNum for the number of players in a guild. It does not state a default value or range there, so do not assume that a familiar number from an old guide applies to your server.
The same reference is more specific about BaseCampMaxNumInGuild: its documented default is 4 bases per guild, with a maximum of 10. Pocketpair warns that raising the base count increases processing load. This is a per-guild base limit; it is not the guild’s member limit and does not mean every server performs the same at the maximum.
Pocketpair’s separate PvP configuration example shows GuildPlayerMaxNum=4 and BaseCampMaxNumInGuild=2. Those are values in that example, not published defaults for every server. Do not use them as a shortcut when comparing a co-op world, a PvE server, and a PvP server; ask which active configuration the administrator is actually using.
If your group is larger than the active member limit, ask the server administrator what GuildPlayerMaxNum is set to and whether they can change it. A self-hosting administrator can review the active server configuration. On a rented server, check the host’s available settings or ask support before planning around a higher value. A dedicated server changes when the world is available; it does not change the game’s guild-sharing rules.
Before someone leaves or changes guilds#
Do not use a live group’s only world to find out what leaving, being removed, or transferring guild leadership does. Pocketpair’s public server reference lists configuration keys, but it does not explain what happens to every member’s character records or structures during those changes. Secondary guides also leave some retention details unresolved, and the results could matter to the whole group.
Before making a membership change, have the owner and the affected player agree on what should happen to structures, base workers, shared materials, and account access. Record the current guild leader and the location of the world save. Ask the administrator to preserve a separate copy through the server’s existing backup process, then confirm who can restore that copy if the change has an unexpected result. A backup file existing is not proof a restore has been tested.
If the real goal is to let one player continue the world elsewhere, separate that transfer question from guild membership. A guest’s guild status does not give them the whole co-op save folder. Our Palworld save-transfer guide documents a tested Steam co-op-to-dedicated-server route and its limits; it is not a generic co-op-to-co-op handoff or a guide to what a departing guild member retains.
Until the group has a verified route, avoid deleting the old world, moving the only copy, or promising that a removed member will keep specific Pals or progress. Confirm the intended result in a disposable copy or leave the membership unchanged.
Make the guild decision before the base gets busy#
One guild is the simplest arrangement when everyone trusts the group to use shared bases, workers, and storage. Separate guilds may suit a community that wants clearer ownership boundaries, but confirm the interactions you need in your own build before choosing that structure. Avoid using guild membership as a substitute for a backup or as a promise that a departing player’s assets will transfer cleanly.
If the main problem is that the co-op host cannot keep opening the world, compare the options in the Palworld multiplayer guide. A server can keep the world running outside one player’s game session, while guild membership and personal progress remain game-level decisions for your group to check. See Game Hosting’s Palworld page for current plan and availability information if you are comparing managed hosting.
Quick answers
How do you join a guild in Palworld?
Join the same multiplayer world, then have a guild member invite you through the in-game player interaction. Confirm the guild name before using shared bases or storage; exact prompts can vary by platform and build.
Do Palworld guild members share Pals?
Current player guides distinguish Pals assigned to a guild base from Pals kept in an individual Palbox. Treat base workers as shared access and check the live game before moving any Pal you want to keep private.
What is the Palworld guild player limit?
Pocketpair documents a GuildPlayerMaxNum server setting but does not publish its default or range in the current configuration reference. Ask the server administrator which value the world uses.