PALWORLDRUN.
SearchSaved
Navigation

CREATE · PACKAGE · VERIFY

Package, Test & Publish a Mod

A release needs a portable package, a truthful compatibility statement and an actual author distribution page. Pocketpair's uploader and package specification describe the official workflow; the website must not imply it has published an archive when it has only exported metadata.

No Palworld Run accountOriginal documentation

Prepare a tested artifact

Build the portable package described in the packaging guide. Run a clean-install check on the intended game revision and side. Include the source author, license, dependencies, known conflicts and the exact observed test scope in the release notes.

Use the official uploader

Pocketpair's uploader requires Steam running with an account that owns Palworld for Workshop publication. Set the Workshop content directory, create the package, place the files and save Info.json. Its local-only creation option avoids initial Workshop registration, but it does not produce a published Workshop item.

Verify before uploading

The uploader checks readable metadata, a valid PackageName and a populated InstallRule. Change Version when updating. Launch the installed package through the game's Mod Management flow and test the behavior before uploading the artifact. A successful metadata check is narrower than an in-game compatibility test.

Publish on the author destination

Choose the intended visibility and complete the Workshop description after upload, or publish a versioned archive on another author-controlled release page. A Palworld Run submission can point to that release, but submitting metadata is not proof of a mirror, scan or external publication.

Sources and verification

The official loader and maintainer documentation were retrieved on October 23, 2026. Examples are explanatory and have not been executed in Palworld by this project. The extended ID snapshot has no verified game-version label. Linked player data uses v1.0.3, while current official news includes v1.0.5.

KEEP BUILDING

Documentation routes

Creating Mods for Palworld.

Develop a reversible change from an explicit requirement. Choose a data edit, Lua behavior or cooked content as appropriate, test a minimal example, then package only the files needed for the release.

Open document

Choose the Right Mod Format

Use a data-edit framework for supported table changes, Lua for runtime behavior, and cooked resources or Blueprint logic when the requirement needs assets or engine content. Distribution and dependencies affect the format decision.

Open document

Create Your First UE4SS Lua Mod

UE4SS Lua mods place their entry script inside a mod's Scripts directory. Begin with visible logging, consult the current hook API, and keep engine-object work on the appropriate thread before adding game behavior.

Open document

Palworld Modding Kit & LogicMods

The community modding kit is a separate toolchain from Pocketpair's package uploader. Verify its prerequisites and game compatibility, then test a minimal cooked LogicMod before importing a large project.

Open document

Create a PalSchema Mod

PalSchema supports structured data edits using JSON or JSONC. Inspect the schema and current record IDs, make one targeted edit, validate it, and test the installed framework before packaging the change.

Open document