PalParty

PalParty adds lightweight client-side parties to Palworld. Party members are kept in sync through normal global chat and shown using Palworld's native player map data.

Requirements

Palworld Steam on Windows
Thunderstore Mod Manager or r2modmanPlus
unreal_shimloader
Server setting bAllowClientMod=True
Every player who wants party features and map markers must install this package

The dedicated server does not need this client display mod. Players without the mod can still join and play, but they cannot use party commands or see party markers.

Commands

Use these in the normal Palworld global chat. Use !party, not /party, because Palworld treats slash commands as admin commands.

!party create <code>
!party join <code>
!party list
!party kick <player name>
!party leave
!party toggle
!party help

Example:

!party create Vikings
!party join Vikings
!party list

The player who creates the party becomes leader. Only the leader can use !party kick <player name>. The mod writes chat confirmations when a party is created, joined, left, or a player is kicked.

Map markers

The mod keeps the party player's native map transform and player name. The marker is refreshed through Palworld's map function, so the position follows the game's own map refresh rate. Open or refresh the map if a marker has not appeared yet.

Important limitation

This is a client-side party protocol. Party membership is synchronized through chat and is not server-authoritative. A player who does not have the mod cannot be added to the roster, and a kicked player can use !party join <code> again if the leader allows it. A future Windows server package could make membership authoritative.

Configuration

The config file is installed as PalParty/Scripts/config.lua in the active profile.

Enabled: enable or disable party map filtering
ShowNames: keep names on party markers
ShowOwnMarker: leave the local player's own marker alone
ChatConfirmations: send party confirmations to global chat
Debug: write extra diagnostics to UE4SS.log