SMMODS
Active WIP

Starminer modding is not fully stable yet. Use SMMODS and mod packages at your own risk, and bring questions to the official Starminer Discord in modding-discussions.

Wiki entry

Getting started with Starminer mods

StarminerBridge owns the official manifest schema, examples, validation scripts, and package rules. This page turns those rules into the first public portal entry.

Modder setup

Start from the StarminerBridge manifest pattern or one of the verified official examples. Work against a copied Starminer install when testing mods locally.

powershell -ExecutionPolicy Bypass -File .\tools\Starminer.NewMod.ps1 -Name MyMod
powershell -ExecutionPolicy Bypass -File .\tools\Starminer.ValidateManifests.ps1 -Root ".\MyMod"

Runtime profile

The manager installs the pinned UE4SS runtime profile required by StarminerBridge and mirrored by this portal.

GET /api/v1/runtime/latest.json

Mods depend on starminer.bridge; they do not bundle UE4SS.

Package contract

A Starminer mod package contains exactly one top-level mod directory or a root-level manifest.

ExampleMod/
  manifest.json
  Scripts/
    main.lua
  Binaries/
    Win64/
      ExampleMod.dll
  Paks/
    ExampleMod-WindowsNoEditor.pak
  Config/
    ExampleMod.ini

Manifest basics

The first portal API tracks the fields needed by the manager before install.

  • Stable lowercase id matching ^[a-z0-9][a-z0-9._-]{1,63}$.
  • Semantic version such as 0.1.0.
  • Target Starminer game build.
  • Entrypoints for ue4ss-lua, ue4ss-cpp, or pak.
  • Explicit load ordering through loadAfter.

Dependencies

Official DataTable pak mods should declare the bridge dependency in both manager metadata and the package manifest.

{
  "dependencies": {
    "starminer.bridge": ">=0.1.7-dev-preview"
  },
  "loadAfter": [
    "starminer.bridge"
  ]
}

Validation

Run local validation before uploading a ZIP to the portal.

powershell -ExecutionPolicy Bypass -File .\tools\Starminer.ValidateManifests.ps1 -Root ".\MyMod"

Portal validation will reject absolute paths, traversal paths, unexpected executable locations, failed antivirus scans, disallowed file signatures, archive content policy violations, mismatched manifest metadata, and archives that cannot be hashed safely.

Publish path

  1. Create a free modder account when accounts are enabled.
  2. Build a versioned ZIP from the official DataTable template or an existing official-track mod.
  3. Upload the package and manifest metadata.
  4. Wait for validation and review.
  5. Published versions appear in the catalog and manager API.

The public upload flow accepts reviewed ZIPs and sidecar metadata from verified modder accounts, then routes them through validation and moderation before catalog publication. The manual importer remains an operator fallback for controlled maintenance and recovery.

Troubleshooting

  • If the manager says a mod is incompatible, compare the mod's targetGameBuild with the runtime profile build.
  • If a mod needs a bridge update, install the latest starminer.bridge version before enabling the mod.
  • If a package is rejected, check for absolute paths, .. traversal paths, missing manifest fields, or unexpected executable locations.
  • If a mod does not load, confirm the manager enabled it in ILLSpace/Binaries/Win64/Mods/mods.txt.
  • If UE4SS does not start, use the runtime profile to confirm the required files are in ILLSpace/Binaries/Win64.