Skip to content

Recipes

m4bwav edited this page Nov 21, 2026 · 1 revision

The safe modding workflow

The order the skill follows:

  1. Find the install and build. For Steam the install is steamapps/common/<Game> and the build id is buildid in steamapps/appmanifest_<appid>.acf.
  2. Scan. mw.py scan "<install>". Exit 2 means stop: no DLL proxy, injection or memory patching.
  3. Check the EULA or mod policy. Ship patches and your own files, never the game's DLLs or assets.
  4. Back up. mw.py backup <out> <saves folder> <each file you will touch> --build <buildid>. Saves often live outside the install (AppData/LocalLow/<Company>/<Game>, Documents/My Games).
  5. Decompile before naming a patch target. ILSpy or dnSpyEx on Assembly-CSharp.dll for Unity Mono; Il2CppDumper or Cpp2IL for IL2CPP; FModel or a UE4SS header dump for Unreal; gdsdecomp for Godot.
  6. Install the recommended loader and pin its version in the mod's README.
  7. Prove it loaded. Run the game, then mw.py proof "<install>" --mod <Name>.
  8. Prepare the upload with publish-prep only when the owner says go. The upload itself needs their account.

Undo a mod

python ../../skills/modwright/scripts/mw.py restore bk --verify
python ../../skills/modwright/scripts/mw.py restore bk

Restore the backup before asking Steam to verify game files, and never delete saves.

Point proof at a log elsewhere

SMAPI writes its log under %APPDATA%, which proof does not search. Pass it with --log (not tested: needs a real SMAPI install):

python skills/modwright/scripts/mw.py proof "C:/Games/Stardew Valley" --mod MyMod --log "%APPDATA%/StardewValley/ErrorLogs/SMAPI-latest.txt"

Clone this wiki locally