Skip to main content
Modding Guide
PalMods
FrameworkPalworld 1.0Intermediate

PalSchema: Install & Use JSON Mods

Updated

Install PalSchema with the correct UE4SS dependency, understand its package layout, read its logs, and resolve version or stale-loader conflicts.

14 min read Researched for 1.0 Sources included

PalSchema is a Palworld-focused runtime for structured JSON and JSONC mods. It can apply targeted data-table, Blueprint, item, Pal, building, spawn, translation, and other supported edits without asking every author to ship a replacement of the whole cooked asset. Its schema files provide autocomplete and validation for creators, while players receive small, readable packages.

PalSchema is not standalone. It runs as a mod within the specific UE4SS/Palworld runtime documented by its maintainer. Install the dependencies as a matched set; a PalSchema package can be perfectly valid and still fail because the core, generated schemas, or experimental UE4SS build belongs to a different game revision.

01Workshop route

Install a published PalSchema mod

  1. 01

    Read the Required Items chain

    Confirm that the mod declares PalSchema and the expected UE4SS package. Use Subscribe to all rather than searching for similarly named framework uploads.

  2. 02

    Remove incompatible manual copies

    Do not leave an older manual PalSchema folder or UE4SS proxy active beside Workshop-managed versions. Preserve only configuration you intentionally need.

  3. 03

    Enable every layer

    In Options → Mod Management, enable the UE4SS core, PalSchema, and the data mod. Resolve missing or disabled dependencies before saving.

  4. 04

    Save and let Palworld restart

    The official loader deploys each rule to its runtime target. Do not move the PalSchema JSON into a pak or generic Lua folder afterward.

  5. 05

    Verify the framework and edit

    Inspect the current framework log for PalSchema loading the package, then confirm the exact data change in a disposable world or save copy.

02Manual path

Manual PalSchema mod location

RequiresUE4SS (Palworld fork: Okaetsu experimental-palworld)PalSchema
<Palworld folder>/Pal/Binaries/Win64/ue4ss/Mods/PalSchema/mods/ExampleMod

Manual fallback only. The folder should contain the mod’s JSON/JSONC content as packaged by its author; never flatten it unless the release instructions say to.

03Capabilities

What a PalSchema package may change

AreaTypical useImportant caution
Pals and itemsStats, parameters, recipes, and targeted rowsSeveral mods touching the same property can conflict even when both parse.
BlueprintsSupported defaults and structured object propertiesNot a replacement for arbitrary runtime Blueprint logic.
Buildings and spawnsCosts, definitions, tables, and distribution dataWorld-state consequences can persist after the mod is removed.
TranslationsString additions or overridesKeep language keys and encoding intact.
Raw and enumsAdvanced schema-backed editsUse only the shape generated for the current game revision.
04Layer-by-layer

When a PalSchema mod appears to do nothing

  • Correct Palworld revision

    The mod and generated schema target the game build you are running.

  • Matched UE4SS build

    Use the exact Palworld UE4SS variant required by the installed PalSchema release.

  • One PalSchema installation

    An old manual tree is not loading before or beside the Workshop-managed copy.

  • Package folder preserved

    The named mod directory and its category subfolders were not flattened during extraction.

  • Valid JSON or JSONC

    The current log has no parse, schema, enum, or missing-property error for the package.

  • No later conflict

    Test the PalSchema package alone before deciding its edit was ignored.

05Lifecycle

Updates and clean removal

Update PalSchema, its generated schema data, UE4SS, and the mod as a compatibility chain. If a Palworld patch changes the underlying table or property, an old JSON key can become invalid even though the document remains syntactically correct. Read the new log after every game or framework update.

To remove a mod, follow its world-cleanup notes, disable it, restart, and test a backup. Removing a runtime data edit does not guarantee that values already serialized into a save will be reconstructed. Keep PalSchema installed if other enabled packages still depend on it.

06Continue

From using to authoring

AuthoringCreate a PalSchema packageGenerate the correct schemas, make a targeted data edit, validate, live-test, and package it.DependencyVerify the runtime beneath itBuild a clean UE4SS baseline and learn to read a fresh log.RecoveryIsolate a data conflictUse binary isolation and save-safe recovery when several mods touch the same systems.
07Verification

Research sources

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

Primary sourcePalworld Mod Loader — GeneralOfficial loader scope, supported package types, dependencies, client behavior, and Windows server support.Primary sourcePalworld Mod Package specificationCanonical Info.json fields, package layout, InstallRule types, version checks, and validation rules.Primary sourceInstalling PalSchemaMaintainer dependency, development-build, schema-generation, and runtime installation instructions.Primary sourceInstalling PalSchema ModsMaintainer user workflow and package placement for PalSchema mods.Primary sourcePalSchema FeaturesSupported JSON/JSONC edit families, autocomplete, reload, merge behavior, and authoring capabilities.

Comments

Loading discussion...

FAQ

Frequently asked questions

Does PalSchema replace UE4SS?

No. PalSchema runs within its documented Palworld UE4SS environment. Install both through the declared dependency chain or use the exact manual development stack the maintainer specifies.

Can I edit a PalSchema mod with a text editor?

Yes, JSON/JSONC is readable, but creators should use the generated schemas and an editor with JSON schema support. A document can be valid JSON and still target a nonexistent or obsolete Palworld property.

Why does my mod load without changing anything?

Confirm the current game/schema version, read the fresh PalSchema/UE4SS log, then test the package alone. Another mod may overwrite the same property later, or the visible value may already be serialized in the save.

Is PalSchema always more compatible than a pak?

It often reduces whole-asset replacement conflicts by applying targeted edits, but two packages can still change the same field or make incompatible assumptions. Structured merging improves the situation; it does not remove semantic conflicts.