Prepare a finished game mod for release by checking packaged files, arranging the required folder structure, writing installation instructions and credits, and drafting a video-led announcement. Includes versioning and platform-specific packaging guidance for user-controlled publishing.
Package and release a finished game mod. Covers the pre-release lint (no game files, decompiled code or leaked keys), README and install steps, credits and AI disclosure, versioning, where to upload (Nexus Mods, Steam Workshop, Thunderstore, mod.io, GitHub releases), and the post with a video. Use when the user wants to ship, share, upload, release or post a mod.
Review the instructions the agent will receive before you install.
um publish check ./MyMod --game "<game install folder>"
.env files.FUN_/DAT_/sub_ names, "Decompiled with" headers), large
engine archives, absolute user paths, a missing README, fal assets without credit.Fix every FAIL. Resolve each WARN deliberately. For example, AoE2 data mods do ship a modified .dat, which
is the platform's norm.
| Platform / loader | Package |
|---|---|
| tModLoader | Build → .tmod; publish from the in-game Mod Sources menu (Steam Workshop) |
| BepInEx / Thunderstore | zip with manifest.json, icon.png (256×256), README.md, plugins/<Mod>.dll; dependency strings like BepInEx-BepInExPack-5.4.2100 |
| Nexus Mods | zip laid out as it installs (Data/... for Bethesda, BepInEx/plugins/..., ue4ss/Mods/..., ~mods/*.pak) |
| AoE2 DE | the official mod site (ageofempires.com/mods) or the in-game uploader; data mods include resources/_common/dat/... |
| Steam Workshop | the game's own uploader or SDK tool |
| Minecraft | Modrinth / CurseForge jar with fabric.mod.json / neoforge.mods.toml |
| ROM hacks / GameMaker | patches only (BPS/IPS/xdelta), never the modified game file |
A Nexus mod with options gets a FOMOD installer: see the FOMOD tutorial and STEP's FOMOD guide. Nexus Mods' own modding wiki covers the rest of their site's conventions.
fal_manifest.jsonl lists them);Use semver in the manifest/build file, name the supported game version, and keep a changelog. When the game updates, re-run the in-game test scene before bumping.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Prepare generated or hand-drawn artwork for a game's required file layout, dimensions, colors, and transparency. Create sprite sheets, assemble animation frames, and render 3D models into consistent views for use as game images.
Create game assets through fal.ai, including sprites, textures, 3D models, sound effects, music, voices, and video clips. Guides consistent visual variations, file conversion, model selection, and generation records so assets can be traced and regenerated.
Launch and control a real game to verify mods through screenshots and logs. Automate menus, keyboard and mouse input, and repeatable test scenes, with guidance for connecting an agent to game state through a JSON bridge.
Investigate an installed game before making a mod. Identify its engine, available mod loaders, save locations, anti-cheat protection, and compatibility issues, then record a practical approach and unresolved questions in MODDING_PLAN.md.
Research game modding methods and tools across public websites and archived pages. Recover information from dead forum links, compare reports, and produce findings with source URLs, version details, credibility notes, and clearly identified gaps.
Build mods that combine content or gameplay from different games. Choose between content ports, two games exchanging data, embedded game engines, or rewritten rules, with clear integration plans and checks against the original behavior.