Verdict. Not competitors: layers. Mod loaders put code into a game. Universal Modder is the workflow on top that tells an agent which loader fits, installs it (with your OK), writes the mod against it, and checks it in game. Every worked example uses a community loader.
Comparison
Universal Modder vs mod loaders (BepInEx, UE4SS, tModLoader…)
If you've modded before, this is the mental model: the loader is the runtime, universal-modder is the developer.
| Universal Modder | BepInEx, UE4SS & mod loaders | |
|---|---|---|
| Role | Workflow, tools and knowledge for the agent | Runtime that loads mods into the game |
| Scope | Any engine (12 playbooks) | One engine or game each |
| Who uses it | Your AI agent | The game, at launch |
| Examples | — | BepInEx/MelonLoader (Unity), UE4SS (Unreal), tModLoader (Terraria), SMAPI (Stardew), Fabric/Forge (Minecraft), SKSE (Skyrim), REFramework (RE Engine), ScriptHookV (GTA V) |
| Installs into the game folder | No (asks before installing a loader) | Yes |
| Needed at play time | No | Yes |
Pick Universal Modder if
- You want an agent to build a mod for the loader.
Pick BepInEx, UE4SS & mod loaders if
- You're installing someone else's mod: you need only the loader.
Using them together
The project credits tModLoader, ScriptHookV, ReShade, Fabric, BepInEx, Harmony, UE4SS, REFramework, SKSE and others as the foundation it stands on. The skill's rule: if the community already has a loader, use it instead of inventing a hook.
Frequently asked questions
Does Universal Modder install BepInEx or UE4SS for me?
The agent can, but asks first, and tells you what it added to the game folder and how to remove it. It also checks the loader's current release instead of installing from memory.