How to Merge Elden Ring With Dark Souls
A focused prompt and prototype plan for the elden ring dark souls mod idea.
01 / Combination notes
Elden Ring and Dark Souls are close enough in combat language that the interesting merge is about structure and pacing rather than surface features. Elden Ring offers open routes, mounted travel, and broad build experimentation; Dark Souls suggests dense interlocking spaces, shortcuts, and deliberate checkpoint placement. A pass-through mod can keep an open region but build a smaller network of looped legacy dungeons inside it.
Combat remains stamina-based and animation-led, while route design creates the feeling that a distant door, elevator, or bridge will eventually reconnect to safety. The prototype should use original enemies and level geometry to test one question: how does open exploration change when shortcuts and compact spaces provide the strongest sense of progress?
02 / Merge instruction pack
A prompt built for this combo
You are merging two games into one playable build. Base game: Elden Ring Merge in: Dark Souls Goal: keep Elden Ring's open exploration and build flexibility while injecting Dark Souls-style interlocking dungeons, shortcuts, checkpoint tension, and compact encounter spaces Steps: 1) design one open approach and one looped dungeon; 2) add a checkpoint with a meaningful shortcut; 3) preserve stamina combat and build choice; 4) place three enemy roles around route information; 5) test death, reload, and shortcut discovery Output: a runnable exploration-and-combat scaffold with original map diagrams, enemy placeholders, and setup instructions
Use this as a starting brief. Add your engine version, target platform, and a request for original placeholder assets before you run it.
03 / Combo-specific cautions
What can go wrong in this merge
Because these games are mechanically related, it is easy to add features without deciding what the merge actually changes. Focus on spatial structure: open travel should lead into dense, looping spaces with shortcuts that alter future attempts. Do not make every area equally punishing or every reward a stat increase. Checkpoint placement needs to respect both open-world travel and close dungeon loops, with a clear reason to return. Stamina, hitboxes, and animation timing should stay consistent across outdoor and indoor spaces. Use a small number of enemy roles and original graybox geometry to validate routes before polishing. The guide is about systems and level design, not distributing copied assets, maps, or modified files.