PalParty

PalParty adds lightweight client-side parties to Palworld. Party members are synchronized through normal global chat and shown in a clickable in-game overlay. Version 0.4.18 uses a separate crash-safe UMG map layer for the live green party dot and player name.

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

In-game interface

Press Y in-game to open or close the clickable overlay. It contains:

• the online-player list with an Nodig uit button;
• an invitation inbox with Accepteren and Weigeren buttons;
• the party roster with leader status and a leader-only Kick button;
• party creation/joining, leaving and marker controls.

Open the native Palworld map with M. PalParty adds a separate non-interactive green dot and name over the map using the replicated live player location. The normal map remains underneath and keeps its controls.

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 invite <code> <player name>
!party accept <code>
!party decline <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. An invitation does not add a player immediately: the invited player must open Y → Uitnodigingen and click Accepteren first.

Map markers

Version 0.4.18 does not edit Palworld's native GetPlayerInfoForMap return value. That native hook caused a reproducible UE4SS crash when the map opened with a party active. Instead, PalParty draws a separate green ● plus the player name over the normal map and reads only the replicated CachedPlayerLocation. Every client that wants to see party markers must have PalParty installed, and the server must keep bAllowClientMod=True.

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 package includes PalParty/Scripts/config.lua. PalParty also has safe settings embedded in main.lua, so a config-path problem can no longer stop the mod from loading.

• Enabled: enable or disable party map markers
• ShowNames: keep names on party markers
• ShowOwnMarker: leave the local player's own marker alone
• ChatConfirmations: send party confirmations to global chat
• Language: auto, nl, en, de, fr or es; auto detects the process locale when available
• Debug: write extra diagnostics to UE4SS.log and PalParty.log
• LogFileName: name of the built-in diagnostic log file

The built-in log is written beside the shimloader configuration when available, or otherwise to %LOCALAPPDATA%\\PalParty.log. It records startup, keybind registration, UI creation, clicks, chat commands, map-overlay renders and caught errors.

To force a language, edit PalParty/Scripts/config.lua in the profile and change the setting, for example Language = "en" or Language = "de". The party commands themselves stay the same in every language.