10x summons

10x Summons

Ten spirits from every ash. Anywhere on the map. As often as you like.

Spirit ashes are supposed to be your allies, but the game only ever lets you have a handful, only at a rebirth monument, and only once per monument. This lifts all three limits at once — and it does it entirely from memory, so it changes nothing on your disk and stacks with the mods you already run.

This is the DLL rewrite of the original 10x Summons. Same idea, none of the file editing.

What it does

• []Ten spirits from every ash. A one-creature ash gives ten. A four-creature ash still cycles through all four — just ten of them.[/]

  []Summon anywhere. No rebirth monument, no "you cannot summon here". Rebirth monuments stop mattering entirely: a summon made standing on one behaves exactly like a summon made in open field.[/]

  []Unlimited resummons. The once-per-monument rule is gone, and so is the pause between summons. Press the ash again and a fresh set appears immediately.[/]

  []Your spirits stay. They no longer vanish the moment you walk away from where you summoned them.[/]

  []No waiting for the summon animation. The long transformations are replaced with the ordinary quick appearance.[/]

  ---

  Requirements

  • []ELDEN RING 2. 6. 2. 0. The version is checked at startup — on anything else the mod stands down and writes why, instead of misbehaving.[/]

    []Elden Mod Loader or ModEngine 2.[/]

    []Offline, single player. The mod disables itself completely if it finds EasyAntiCheat in the process. Do not use it online.[/]

    Installation

    Elden Mod Loader — drop both files into

    ELDEN RING\Game\mods\

    ModEngine 2 — put both files with your other external DLLs and add the DLL to your config:

    external_dlls = [ "er10x.dll" ]

    Keep er10x.ini next to er10x.dll.

    ---

    Settings

    Four of them, in er10x.ini, read once when the game starts.

    • []summons — how many, 1 to 10[/]

      []multiply — whether that number is a multiplier or a flat count[/]

      []summon_anywhere — the monument rules, on or off[/]

      []unlimited_resummon — instant resummoning[/]

      Every option is explained inside the file itself, including why it exists and what it costs.

      ---

      Compatible with your other mods

      Nothing on your disk is modified. Not regulation.bin, not a single map, not your save. The mod only rewrites its own process's memory.

      That has a practical consequence worth spelling out: ashes added by other mods are multiplied too, without this mod knowing their names. It reads the chains out of the game's own tables, so whatever an ash is made of, it gets ten of it.

      Six small code patches handle the permission to summon. Each is found by a byte signature verified to occur exactly once, and each is checked byte-for-byte before anything is written. If the game updates, or if another mod got there first, the patch refuses itself and says so in the log rather than writing somewhere plausible.

      For the curious: how the limits actually work

      Ten is the engine's number, not a preference. The game reserves each player a band of exactly ten character slots for summons. The start of that band and its length are both constants inside the allocator. Asking for forty gets you ten — and costs the game the work of preparing thirty requests it will refuse. That is why the cap lives in the mod rather than being left to the engine.

      Why "summon anywhere" needs code and not a param edit. Permission is decided by one function, and its whole test is three clauses: you must be carrying a marker effect that only a monument's own script applies, and the manager must remember a monument you have not already summoned at. Blanking the monument table gets you "almost everywhere" because it widens a finite list; it cannot remove the requirement to be standing at one.

      The Mimic Tear is hard-coded. The game decides "this request is a Mimic" once per request, by looking for one specific row in the request list. Drop that row — the obvious way to remove its blob stage — and the branch that copies your equipment is never reached. You get ten default-loadout humanoids. The row has to stay and be rewritten instead.