How to use Universal Modder for your first mod

Your first session in six steps

1. Back up a single-player test save

   Make a separate copy of your saves and the files you plan to change. Use a disposable offline or single-player test profile. Write down how to restore it before starting.

2. Match the game and loader versions

   Record your game edition, exact build, operating system and loader version. Open a sourced case if one exists. Treat missing or different versions as pending verification, rather than assuming compatibility.

3. Pick one small, observable goal

   Start with a modest text, recipe or cosmetic change that your game’s documented mod route supports. Define what you should see in game and avoid a multi-game mashup for your first attempt.

4. Prepare a prompt, then request a plan

   Use the homepage tool to record your setup and goal, or adapt the example below. Ask the agent to inspect sources, name uncertainties, list intended file changes and wait for your approval before editing.

5. Build one change and test locally

   Approve a bounded plan, then review the changed files. Build if the chosen route requires it. Launch the test profile, check the intended behavior, and keep the loader/build logs. Report what you observed, including failures.

6. Keep the evidence and prove recovery

   Record the versions, changed files, test result and unresolved issues. Disable the test mod and confirm the original state returns. If it does not, restore the backup before adding more changes.

A starter prompt you can adapt

Replace every bracketed field with your own details. Share only the local paths needed by your agent; do not paste passwords, keys or private files.

I want to make one small mod for my legally owned local game.
Game and edition: [game / edition]
Exact game build: [version or unknown]
Operating system: [OS]
Mod loader and version: [loader / version or unknown]
Goal: [one small visible change]
Test profile and backups: [what is backed up and how to restore it]

First, review the available Universal Modder skills and relevant upstream field notes. Check whether the documented game build and loader match mine. Mark unknown compatibility as pending verification.

Propose the smallest testable plan, intended file changes, required tools, any service costs, success criteria and rollback steps. Ask me about missing information. Wait for my approval before editing files, installing tools, launching paid services or changing game data.

After approval, make one change at a time. Distinguish a successful build from an in-game test. Record logs, exact versions, observed behavior and anything that remains unverified. Work only in my offline or single-player test setup.