Package, Test & Publish a Mod

Replace dependency identities and revision with values verified for your release. Keep PackageName to ASCII letters and digits for broad package-tool compatibility.

{
  "ModName": "Example Runtime Utility",
  "PackageName": "ExampleRuntimeUtility",
  "Thumbnail": "thumbnail.png",
  "Version": "1.0.0",
  "DebugMode": false,
  "MinRevision": 82182,
  "Author": "YourName",
  "Dependencies": ["UE4SS"],
  "Tags": ["Utilities", "UE4SS"],
  "InstallRule": [
    {
      "Type": "Lua",
      "Targets": ["./Scripts"]
    }
  ]
}

The server rule is separate even when it deploys the same source. This makes client and server intent machine-readable.

{
  "InstallRule": [
    { "Type": "Lua", "Targets": ["./Scripts"] },
    { "Type": "Lua", "IsServer": true, "Targets": ["./Scripts"] }
  ]
}

1. 01

   Stage a clean release candidate

   Create a fresh package folder outside the development tree. Keep Info.json at root and include only final runtime files, documentation, and referenced artwork—never build caches, logs, source-only assets, or secrets.

2. 02

   Author or generate Info.json

   Write the manifest directly or use Mod Uploader’s local-package mode as a template. Select the real Lua, Paks, LogicMods, or PalSchema layout without creating a Workshop item.

3. 03

   Inspect every package claim

   Set a stable PackageName, real Version, minimum tested revision, dependencies, tags, and exact install types. Add separate server rules only when the server artifact was actually tested.

4. 04

   Zip the portable artifact

   Place Info.json at the archive root and confirm every InstallRule target exists inside the zip. The archive should not depend on a storefront-owned folder or metadata file.

5. 05

   Upload and review on PalMods

   Upload the final zip, review the detected manifest fields and scanner results, then complete the human metadata: summary, description, compatibility, save impact, permissions, requirements, and removal notes.

6. 06

   Test what users will receive

   Install the uploaded artifact in a clean setup with only declared dependencies. Verify first install, update, disable, removal, client/server behavior, and the logs users will need for support.

PalMods treats manifest values as reviewable suggestions, preserves explicit author choices, and shows conflicts instead of silently guessing.

• Clean-package install

  A separate clean game can install and run only the release artifact plus declared dependencies.

• Update tested over prior public version

  The new Version redeploys, settings migrate or preserve correctly, and stale files do not survive unexpectedly.

• Client/server matrix tested

  Every claimed side and platform was actually run, including mismatched-client behavior and server restart where relevant.

• Persistence and removal tested

  New world, copied existing world, save–exit–reload, disable, uninstall, and dependency removal have documented outcomes.

• Package contents audited

  No credentials, personal paths, source-only assets, editor cache, crash dumps, or unrelated executables are included.

• User documentation complete

  Requirements, loader, supported revision, install, configuration, conflicts, removal, support/log location, license, and change notes are present.

The claims in this guide were checked against these current references. Primary sources are marked first.