PALWORLDRUN.
SearchSaved
Navigation

CREATE · PACKAGE · VERIFY

Mod author documentation

Choose the smallest change that solves the mod's purpose, identify its game records, and test on the side where it runs. Package the result with dependencies, compatibility evidence, credits and removal instructions.

No Palworld Run accountOriginal documentation

Define a testable change

Write down one observable result: the existing behavior, the intended new behavior and where it must run. A client-only visual change and a server-authoritative rule need different evidence. Choose a format only after that requirement is clear.

Use the exact record

Search the ID catalogs by label or internal identifier. Inspect the group and player-reference link before editing: boss, test, scenario and ordinary species records can share display labels. Store the identifier and source revision with the mod.

Release with evidence

  • Build a minimal version and record a clean-install test.
  • Declare every framework and other mod required to reproduce the result.
  • Package only the required files, preserve third-party licenses and credits, and explain how to remove the change.
  • Publish on the author-controlled destination; link the actual release rather than implying the website hosts a mirror.

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

Palworld mod documentation

Find the game identifiers, installation guides and authoring references needed to use or release a mod. Follow the route for your loader and platform, then verify the installed result and keep a removal path.

Open document

Palworld Run data and API reference

Document the data actually published by Palworld Run, including schemas, stable identifiers, version metadata and limitations. Source-site API endpoints, private credentials, scanning claims and write operations cannot be carried over as if the new site operates them.

Open document

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