factorio-mod-dev

Document Factorio mod structure and verify code with layered checks.

17|16|Updated Feb 27, 2019
One-click install
npx skills add https://github.com/jodli/CreativeMod --skill factorio-mod-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: factorio-mod-dev
Source: https://github.com/jodli/CreativeMod/tree/main/.pi/skills/factorio-mod-dev
Command: npx skills add https://github.com/jodli/CreativeMod --skill factorio-mod-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Factorio mod development for projects like creative-mod often involves time-consuming debugging of data and control stage errors, version porting challenges, and inconsistent verification processes that slow down iteration and introduce regressions.

Core Features & Use Cases

  • Comprehensive Mod Reference: Documents the creative-mod repo layout, key internals like runtime storage and event systems, and prototype naming conventions to eliminate guesswork during development.
  • Layered Verification Pipeline: Provides full documentation for the verify.py tool, including static analysis, load gate checks, and headless behavior assertions to catch bugs early in the development cycle.
  • Use Case: A developer porting the mod to a new Factorio version can use this skill to follow the documented porting workflow, run verification checks at each stage, and debug silent control-stage crashes using the provided RCON troubleshooting steps.

Quick Start

Use the factorio-mod-dev skill to debug a silent control-stage crash by running the verify.py load command and checking the factorio-current.log file for errors after the mod's checksum line.

Frequently Asked Questions about factorio-mod-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a silent control-stage crash in a Factorio mod?

To debug a silent Factorio mod control-stage crash, run the verify.py load command and inspect the factorio-current.log file for errors appearing after the mod's checksum line. This isolates hidden runtime failures during the data or control stages.

What is the best way to port a Factorio mod to a new 2.x game release?

Porting a Factorio mod to a 2.x release requires following a documented porting workflow, running layered verification checks at each stage, and validating behavior through static analysis and headless assertions to prevent regressions.

How does layered verification work for Factorio mod regression testing?

Layered verification for Factorio mod regression testing combines static analysis, load gate checks, and headless behavior assertions to catch bugs early. This reproducible pipeline validates mod stability before pushing new releases.

How do I set up a GitHub Actions release pipeline for Factorio mod development?

Setting up a GitHub Actions release pipeline for Factorio mod development involves integrating a standardized verification workflow that runs static analysis and load gate checks to ensure reproducible builds before publishing.

Can I use this workflow for debugging data stage errors in any Lua Factorio mod?

This workflow targets debugging data and control stage errors specifically for the creative-mod project in Factorio 2.x. It provides structured references for internal mod structure, runtime storage, and event systems to accelerate iteration.

Why does my Factorio mod fail verification after porting to a new game version?

Factorio mod verification failures after version porting often stem from outdated prototype naming conventions or runtime storage changes. Checking the documented internal mod reference and running load gate checks helps identify these regressions.