Repository navigation
Recipes
m4bwav edited this page Nov 21, 2026
·
1 revision
The order the skill follows:
-
Find the install and build. For Steam the install is
steamapps/common/<Game>and the build id isbuildidinsteamapps/appmanifest_<appid>.acf. -
Scan.
mw.py scan "<install>". Exit 2 means stop: no DLL proxy, injection or memory patching. - Check the EULA or mod policy. Ship patches and your own files, never the game's DLLs or assets.
-
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). -
Decompile before naming a patch target. ILSpy or dnSpyEx on
Assembly-CSharp.dllfor Unity Mono; Il2CppDumper or Cpp2IL for IL2CPP; FModel or a UE4SS header dump for Unreal; gdsdecomp for Godot. - Install the recommended loader and pin its version in the mod's README.
-
Prove it loaded. Run the game, then
mw.py proof "<install>" --mod <Name>. -
Prepare the upload with
publish-preponly when the owner says go. The upload itself needs their account.
python ../../skills/modwright/scripts/mw.py restore bk --verify
python ../../skills/modwright/scripts/mw.py restore bkRestore the backup before asking Steam to verify game files, and never delete saves.
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"modwright 0.1.1 · Repository · Wiki updated 2026-11-21