Game modding

Build the change the user asked for, in the game they own, and prove it works where they will play it. Preserve the user's saves, settings, and install. Keep each mod in its own folder unless the project already has another layout.

Pin down the result

Restate the behaviour and quality bar before choosing a route. Past requests show what users usually mean. A request for a fix wanted the game itself to behave correctly, not a workaround. A resizable window should have scaled its content automatically, not exposed a manual zoom setting. "New weapons" meant new mechanics and effects, not recoloured existing items. Settings UI was expected to match the game's own art, fonts, and controls. A crash fix was expected to stay scoped to the mod, not change a global game setting. When a cheap tweak and real new behaviour both fit the words, build the real behaviour or explain what it costs.

Ask only when the answer changes the route, such as byte-identical versus working, which platforms, or public versus private release. When a goal is large, such as rebuilding a whole game, offer the smallest milestone that proves progress, such as reaching the main menu, and agree what will demonstrate it.

Keep a MODLOG.md beside the mod. Record the game build and file hashes, the route and why, hook sites with their original bytes, IDs, formats, failures with causes, backups, restore steps, and what was verified and how. It survives context compaction and becomes the README and handoff.

Start from the installed game

Work from the user's install, ROM, or dump, not from devblogs, wikis, or memory. Record the store, app ID, exact build, and executable hashes. Identify the engine and code type from the files; treat detector output, folder names, and extensions as hints and check the deciding fact. Routes and engines lists the tells and community routes for common engines, plus Linux and Proton specifics.

Check for anti-cheat, online modes, DRM, existing loaders, and earlier modifications. If the executable is already cracked or patched, such as a no-CD build, tell the user and keep the original behaviour as the reference. Locate saves, configs, logs, and crash dumps.

Before reversing anything, look for prior art and free information: the game's modding wiki, Nexus, Thunderstore, mod.io, Steam Workshop, GitHub decompilations and loaders, and field notes such as the universal-modder knowledge base. Check loaders' current releases and install steps on their official pages. Also look for shipped linker maps, debug builds, symbol files, script sources, or data files that are real engine output. Treat other people's notes as leads to re-verify; versions move.