- Home
- Technical Documentation
- Loader architecture
Loader architecture
The parts of DeltaLoader and how they fit together.
Mods siteAPI, catalog
verified download
DeltaLauncherinstalls, switches, starts
starts it
Injectorswinject.exe
loads into the game
stormworks64.exe
swversion.dllshows the DeltaLoader label
your_mod.dllSW_MOD, sw_mod_start(), hooks
| Part | Role |
|---|---|
| Mods site / API | Catalog and downloads (a Modrinth-shaped API). |
| DeltaLauncher | Installs, verifies, switches mods, starts the game, lays out overlays. |
| Injector | Checks the target and loads DLLs into the running game. |
| Version patch | Built into the launcher; shows the DeltaLoader label and is loaded into the game before the mods. |
| Bridge (SDK) | In every mod DLL: connects to the game, checks it, installs hooks. |
| Mapping | Names, addresses, signatures and layouts. The source of everything the bridge knows. |
Principles#
- Fail closed. SHA-256 of the executable and all byte signatures must match, or nothing is delivered.
- No permanent changes. The game's files are not modified. Overlays are journalled and restored.
- No anti-cheat. The loader refuses to attach when an anti-cheat module is present.