Games · Dark Souls 3
Dark Souls 3 Modding with DSMapStudio
Dark Souls 3 Modding with DSMapStudio
Dark Souls 3 is one of the calmest games to mod with DSMapStudio: it doesn't get format-breaking patches, so v1.11.1 reads the current build with none of Elden Ring's version drama. The one rule that isn't a tool setting and will cost you an account if you ignore it: modded Dark Souls 3 must be played offline.
Play offline — the DS3 anti-cheat will soft-ban you
⚠️ Never play modded Dark Souls 3 online. DS3's anti-cheat flags modified game files and issues a soft ban that drops your account into a penalty matchmaking pool — effectively cut off from the normal online community. Launch modded DS3 in offline mode every time.
DSMapStudio writes edits to your project's mod output, not over the game files, so keeping a clean baseline is easy: launch modded DS3 through ModEngine2 offline, and restore a clean regulation.bin (or keep a separate unmodded install) before reconnecting for vanilla online.
Compatibility
No patch minefield. DS3 never shipped the format change that broke Elden Ring at 1.12, so v1.11.1 handles the current build directly — you won't normally see "Unknown DCX format" on DS3. If you do, it's one file another tool re-saved incompatibly, not a game-wide issue; re-extract it from a clean install with UXM.
Setup, in order
- Install DSMapStudio — release build, VC++ x64 + .NET 7, extracted outside
Program Files(installation guide). - Unpack with UXM Selective Unpack —
param/msgfor params and text, plusmap,chr,assetfor the Map Editor. - New Project → Game Type: Dark Souls III, Game Directory on the unpacked files (first project setup).
- Verify —
EquipParamWeaponshows named rows.
Dark Souls 3 at a glance
| Detail | Dark Souls 3 |
|---|---|
| Game Directory (Steam) | steamapps\common\DARK SOULS III\Game\ |
| Executable | DarkSoulsIII.exe |
| Unpack tool | UXM Selective Unpack |
| Main param file | regulation.bin (in the Game folder) |
| Online with mods | ✗ — soft-ban risk; play offline |
| Map ID example | m30_00_00_00 = High Wall of Lothric |
| Runtime mod loader | ModEngine2 |
What you can edit
DS3 mods are mostly param edits in regulation.bin. The structural point worth knowing if you came from Elden Ring: DS3 uses a single ItemLotParam, not Elden Ring's map/enemy split — so older DS3 tutorials that reference one drop table are correct. Common tables: EquipParamWeapon (damage, scaling, requirements), ShopLineupParam (vendor stock), NpcParam (enemy HP/stats) and AtkParam (attack damage) for enemy mods, SpEffectParam and Magic for status and spells, EquipParamProtector for the lightest fashion edits. Workflow: Param Editor hub; bulk changes: CSV export/import.
The Map Editor opens DS3's areas — High Wall of Lothric, Undead Settlement, Irithyll, each a separate map ID — for placing enemies and objects with unique entity IDs. The 3D viewport needs a Vulkan 1.3 GPU; Intel integrated graphics are limited to params and text.
Merging and troubleshooting
Two mods both editing regulation.bin overwrite each other unless you do the row-level CSV merge — method in the DS3 merge guide. DS3-specific snags: penalty matchmaking means you played modded online (restore a clean install for online play); a black Map Editor is the Intel GPU limit (Low Requirements build); won't open at all is a runtime/download issue.
Set for DS3? Install, create your project, keep modded play offline, head to the Param Editor hub.
Watch it in action
Community video guides this article draws on — credit to their creators.
