PALWORLDRUN.
SearchSaved
Navigation

CREATE · PACKAGE · VERIFY

Build a reproducible GitHub release

A release workflow can build and attach an archive to a GitHub release, but publishing requires the author's own external authorization. The reference's branded upload action and site tokens must not become a Palworld Run integration by renaming its instructions.

No Palworld Run accountOriginal documentation

Build without a site-specific token

Use your repository's workflow to build a versioned archive and attach it to your own GitHub release. Pin the actions and tool versions you select, keep secrets in the external provider's secret store, and use the smallest permissions that the release job requires. Palworld Run does not use the reference site's publishing action or API credentials.

A reproducible release checklist

  • The tag identifies the exact source revision.
  • The archive contains the tested package and Info.json, with dependencies and original credits.
  • The release includes a hash, game revision, test scope and removal notes.
  • A clean installation of the downloaded release matches the artifact tested before publication.

Connect the release to the catalog

After the author-controlled release exists, submit its real URL and metadata through the website's submission flow. Keep the returned edit token if you need to manage that submission. Public catalog publication and moderation have their own status; exporting an archive or creating an external release cannot stand in for that state.

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

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.

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