Satisfactory Content Forge

Prüfe vor der Installation, ob die konkrete Version dieser Mod deinen Dedicated Server und die Spielversion unterstützt. Eine ficsit.app-Listung allein ist keine Kompatibilitätszusage.

Installation und Erfolgskontrolle

  1. Lies die Originalbeschreibung, prüfe SML-Version und Abhängigkeiten und sichere deinen Spielstand.
  2. Stoppe den Server und wähle die Mod im Satisfactory-Mod-Bereich deines Dashboards. Prüfe Quelle und Versionsnummer.
  3. Installiere erforderliche Client-Mods in passenden Versionen. Starte den Server und kontrolliere Protokoll, Verbindung und modabhängige Inhalte.

Entfernen und Updates können Spielstände verändern. Behalte ein Backup der funktionierenden Kombination. RAM-Bedarf lässt sich nicht zuverlässig aus dem Namen einer einzelnen Mod ableiten.

Veröffentlichte Versionen

  • 2026.4.582 · Spielversion >=491125 · SML beim Projekt prüfen

    Veröffentlichte Ziele: LinuxServer, Windows, WindowsServer

  • 2026.3.570 · Spielversion >=491125 · SML beim Projekt prüfen

    Veröffentlichte Ziele: LinuxServer, Windows, WindowsServer

  • 2026.3.509 · Spielversion >=491125 · SML beim Projekt prüfen

    Veröffentlichte Ziele: LinuxServer, Windows, WindowsServer

  • 2026.3.497 · Spielversion >=491125 · SML beim Projekt prüfen

    Veröffentlichte Ziele: LinuxServer, Windows, WindowsServer

  • 2026.3.485 · Spielversion >=491125 · SML beim Projekt prüfen

    Veröffentlichte Ziele: LinuxServer, Windows, WindowsServer

Originalbeschreibung des Mod-Autors
KMods Logo
Discord   Patreon
ficsit.app   Multiplayer: Supported

k-mods.com   KDataForge Documentation

KDataForge lets pack authors rebalance existing Satisfactory content or create recipes, items, buildings, gameplay tags,
and more in YAML. You do not need to write code or cook Unreal assets.


What KDataForge does

KDataForge is a reflection-based runtime content editor. Put .yml files in <GameFolder>/FactoryGame/DataForge/;
KDataForge applies them at startup. It can edit reflected properties on class default objects and data assets, register
gameplay tags, generate items, buildings, recipes, and schematics, or patch spawned actors while the game runs.

See the documentation for player setup, the full YAML grammar, developer APIs,
and task-based tutorials. The public
KPatchwork DataForge directory contains
maintained compatibility-pack examples.


YAML editing
  • Edit any reflected property on any class default object: numbers, texts, arrays, maps, structs, object references
  • 25 property operations: set, multiply, clamp, append_unique, update_where, replace_refs, and more
  • Target class defaults, single data assets, or all assets of a class at once
  • Reference classes by their short name (e.g. Desc_Water) instead of the full asset path
  • Conditional documents: apply only for certain game versions, installed mods, or existing classes
  • Trace every applied change with debug logging: per file (debug: true), per pack, or globally (KDF.Debug 1 /
    -KDFDebug), each op logged with its before/after values
Content creation
  • Create new items, resources, buildings, recipes, schematics, research trees and unlocks from YAML: no editor, no
    cooking
  • Generated content is savegame-stable: deterministic id-based classes plus a tombstone manifest mean your saves
    load cleanly even after packs change or disappear
  • Rename ids safely with pack redirects: so old saves keep working
  • Register existing classes (e.g. hidden schematics from other mods) without generating anything
  • Go beyond the preset types with type: class: generate a class from any parent (equipment descriptors,
    categories, other mods' classes, …), C++ or Blueprint
  • Ship your own 2D images (PNG/JPG/TGA/BMP) in a pack and use them as item or building icons: loaded at runtime, no
    cooking
Gameplay tags and runtime actor patches
  • Register new gameplay tags at runtime from YAML; add/remove/clear tags on any tag container property
  • applyToSpawnedActors: true re-applies your values to every actor instance the moment it spawns: even values that
    saves or archetypes would normally override
Content packs and session loading
  • Group files into packs with a pack.yml manifest (name, version, priority, dependencies) for deterministic load order
    across packs and files
  • /kdf reload rescans and reapplies reloadable YAML changes; frozen registrations, irreversible world changes, native
    CDO helpers, and cold data still require a session restart
  • /kdf report prints a full load report with warnings and errors
  • Broken files do not stop other packs: KDataForge reports an error and skips the affected file, document, or operation
Mod integration
  • Create real PrimaryDataAsset instances from YAML: e.g. new KAPI cleaner items or RefinedR&D boiler/heater/turbine
    data assets
  • Edit any mod's existing data assets with plain cdo documents (single asset, all assets of a class, or by
    gameplay tag)
  • Create or edit curves with type: curve: UCurveFloat and UCurveVector, including interpolation, tangents,
    defaults, and extrapolation
  • Auto-rescan: KAPI and RefinedR&D (RefinedPower / FicsitFarming) are notified after the initial load, without
    KDataForge requiring those mods
Chat and console commands
Command Where Effect
/kdf report chat Prints the load report: packs, applied documents, ops, warnings, errors
/kdf reload chat (host or dedicated-server administrator) Restores captured baselines, rescans packs, and reapplies reloadable changes in this process
/kdf config dump [PackRef] chat Lists pack settings, defaults, effective values, and hot/cold mode
/kdf config set <PackRef>:<Id> <Value> chat (host or dedicated-server administrator) Stages one pack setting
/kdf config apply [PackRef] chat (host or dedicated-server administrator) Saves pending settings and reloads hot changes where supported
/kdf editor chat; host-local UI Requests the in-game editor: browse content, author packs, edit properties live, undo/redo, and export changes to YAML
/kdf sound <PackRef> <Id> chat (local player) Previews one generated sound on this machine
/kdf debug on|off chat Flips global debug logging (same switch as KDF.Debug); bare /kdf debug toggles the current state
KDF.Editor console Same as /kdf editor
KDF.Reload console (host/server) Same reload operation as /kdf reload; logs its summary
KDF.Config.Dump [PackRef] console Lists pack configuration fields and values
KDF.Config.Set <PackRef>:<Id> <Value> console Stages one pack setting
KDF.Config.Apply [PackRef] console Saves pending pack settings and handles hot/restart behavior
KDF.Sound <PackRef> <Id> local console Previews one generated sound locally
KDF.Debug 1 console (or -KDFDebug) Global debug logging: one [KDF DEBUG] line per applied op, including editor edits
KDF.ApplyToAssets [PathFilter] console (UE editor builds only) Applies loaded YAML directly onto editor assets and marks packages dirty
/kdf-reflection [options] chat (host/server) Starts time-sliced export; no options enables assets, functions, flattened classes, ZIP, and 1024px PNGs
/kdf-export [options] chat alias Alias of /kdf-reflection
KDF.DumpReflection [options] console (host/server) Starts export with core defaults below; output defaults to FactoryGame/KMods/ReflectionExport/
KDF.ValidateReflection [--out <dir>] console Checks runtime reflection contracts and basic completed-export checks

Reflection export for Pack Manager

Run after world begins play:

KDF.DumpReflection --assets --functions --flattened

Bare KDF.DumpReflection exports core reflection data, textures and the ZIP; functions,
data-asset/curve indexes and flattened classes require their explicit flags. Bare /kdf-reflection
enables the full profile shown above. Supplying any chat option uses only the options supplied.

Options: --out <dir>, --mounts /Game,/Plugin, --assets, --asset-cap N, --functions,
--flattened, --widgets (widgets skipped by default), --budget-ms N (default 8),
--batch-size N, --families name:/Script/Module.Class,..., and client-only override --force.
--image-max-dimension N caps the largest exported texture side in pixels; default 1024,
accepted range 1 to 4096.
--pack remains accepted for compatibility; ZIP packaging is always enabled.
Automated runtime QA can pass -KDFReflectionAutoExport=<dir>; it waits for BeginPlay and runs the full
--assets --functions --flattened profile. Add -KDFReflectionAutoExit to close the game cleanly after export.

Output contains manifest; class, struct, and enum NDJSON; subclass, asset, and native/Blueprint
indexes; indexes/textures.json; PNG files below images/; linter-compatible
catalog/instanced_classes.json; JSON Schema; optional flattened classes;
and one <ISO-date>.kdfdata ZIP. In desktop editor open Datapacks, import generated archive,
then bind imported game-data pack to project; Pack Manager exposes it as datapack reflection section.
Loose files serve development/debugging. Texture selection scans reflected non-widget class defaults recursively.
This retains descriptor, item, recipe, and schematic icons while excluding material-only maps, widget-only
decoration, unreferenced helpers, and dynamic render/media textures. Selected textures are indexed with Asset
Registry tags, image path/export status, and without applying --asset-cap; --assets enables indexes for other
asset classes. All exported images are deterministic PNG; cooked BC/BC7 data is decoded before writing.
Images exceeding the configured --image-max-dimension cap use a proportionally scaled image or
cooked mip. The cap does not upscale images. Missing or unreadable higher mips can produce smaller
output even when the source fits within the cap. Records retain source and exported dimensions plus
resized. Cooked-decode and GPU-readback fallbacks warn when using a lower mip than requested;
the raw platformMipPng path does not. Stripped/virtual/unsupported payloads keep an explicit
per-asset error. Each encoded PNG is limited to 4 MiB (4,194,304 bytes). Larger previews are not
written; their texture metadata remains indexed with status: error, errorCode: encodedImageTooLarge,
and an increased image error count. Reduce --image-max-dimension and rerun the export to retry.
Exporter
attempts to load every previously unloaded registry asset under selected mounts in bounded batches using
quiet/no-warn load flags, including UWorld map assets; failures remain in manifest.json.failedLoads.
Garbage collection is requested through engine safe points rather than called inside exporter ticker.
Properties whose constructors produce changing GUIDs, timestamps, seeds, transient object names, runtime command
lines, or uninitialized bytes are zero-normalized and marked defaultVolatile: true; stable defaults stay intact.
Blueprint-authored member names and serialized FName values use deterministic casing. Native type casing is
recovered from reflected C++ property types when Unreal's global FName registration order changed its display form.
Transient runtime textures are excluded because they have no portable asset identity and their pixels can change
between processes.

Runtime export prepares output in a sibling .<output-name>.kdf-export-<id>.stage directory,
then publishes generated files individually with the new archive last. Do not import or modify the
destination until completion. Before publication it saves affected previous files beneath
.<output-name>.kdf-export-<id>.stage.backup/previous/ and records destination, archive,
previousFiles, newFiles, and newDirectories in that backup's recovery.json.
A publication error attempts rollback and retains recovery files. Process crashes can require
manual rollback; there is no automatic restart recovery.

The sibling .stage.backup.committed marker records completed publication and is removed after
backup cleanup. It does not prove artifact validity or a complete remaining backup. A missing marker
can also mean its write failed after successful publication. Stop all writers, preserve copies of the
destination and all matching transaction artifacts, inspect journal/logs, and validate before recovery.
To roll back, first verify every previousFiles backup exists; remove only destination newFiles,
remove only empty newDirectories deepest first, then copy previous/ files back to their matching
relative paths, restoring the previous archive last. Keep backup sources intact, compare restored
bytes, and validate the previous complete export before deleting recovery artifacts. If no previous
complete export existed, verify prior state and export afresh into a new empty directory.
See
runtime publication and recovery
for path checks and incomplete-backup handling. Runtime transaction names differ from metadata-merge
.<output-name>.kdf-merge-<id>.stage and .backup directories; their recovery procedures differ.

Shipping builds often strip reflection metadata. Generate supplement from modding editor:

UnrealEditor-Cmd.exe FactoryGame.uproject -run=KDFReflectionMetaExport -out=C:\Temp\KDFMeta
UnrealEditor-Cmd.exe FactoryGame.uproject -run=KDFReflectionMetaExport `
  -runtime=C:\Path\ReflectionExport `
  -supplement=C:\Temp\KDFMeta\metadata.supplement.json `
  -out=C:\Path\ReflectionMerged

Merge runs natively inside Unreal; no Python files enter mod or .kdfdata packages. Add -force only to replace
an existing merge output directory. Known limits: unloadable assets appear in manifest.json.failedLoads; registry
indexing caps non-texture
classes, while asset loading itself covers every selected registry entry; full output can be large. Merge tool
always rebuilds ISO-named .kdfdata ZIP.

Acceptance commands:

KDF.ValidateReflection --out C:\Path\ReflectionExport
python -m pip install jsonschema
uv run --project Scripts --locked python Scripts/Mods/KDataForge/Tools/validate_reflection_export.py `
  C:\Path\ReflectionExport-1 --compare C:\Path\ReflectionExport-2

KDF.ValidateReflection checks live FactoryGame reflection contracts, authored struct member names,
and deterministic default ExportText/ImportText samples (up to three per property kind). For the
completed export it checks required-file presence, native/Blueprint mapping, basic consistency of
optional settings/icon indexes and the cold-property catalog, and the presence of exactly one
.kdfdata archive.

Run the Python artifact/package validator for emitted-schema
validation of exported JSON documents and NDJSON records, PNG integrity and texture-index consistency,
and available settings/icon/cold-property catalog checks. It verifies the archive's ISO filename,
sorted entries, ZIP CRCs, inclusion of every generated file, and byte-for-byte agreement between each
packed entry and its loose file. ZIP entries and indexed image paths must use safe relative paths
contained within the export directory; traversal paths are rejected. The validator rejects symlinks
and Windows reparse points anywhere in the loose export tree, including unrelated custom entries.
Unrelated regular custom files outside images/ may remain outside the archive.
It also checks numeric integer schemaVersion: 1 and mirrors the editor's archive
inspection gates: source archive at most 2 GiB, at most 20,000 entries, at most 4 GiB expanded,
manifest.json at most 1 MiB, and each PNG within the 4 MiB preview limit.
Runtime acceptance alone does not validate ZIP contents, images, or every record against the schema.
The editor can compact source archives larger than 512 MiB and rejects installed output that still
exceeds its 512 MiB cache cap. Python PASS does not predict compacted-cache success or prove every
desktop editor import gate; confirm acceptance through the desktop editor's Import game data.
With --compare, Python validates both exports and compares
SHA-256 hashes of loose files, excluding .kdfdata archives and normalizing manifest.json with only
generatedAt removed.


Technical
  • Reflection-based property engine: supports every reflectable UObject property type, including Blueprint structs and
    PrimaryDataAssets
  • Fixed stage pipeline (tags → assets → localization → CDO changes → content → validation)
  • Vanilla value snapshots power editor diffs, undo support, and changes-only export
  • Extensible C++/Blueprint handler API for other mods (IKDFDataEditorHandler)
  • Dedicated server compatible

Requirements
Dependency Link
SML ficsit.app

Questions, bugs, or suggestions?
Join the Discord or support us on Patreon
Discord Patreon
ficsit.app k-mods.com
KDataForge Documentation

Quellen und Hilfe