Report a bug — Elden Ring for Archipelago

🛑 First: are both halves from the same release? The apworld and the client DLL are a hash-matched pair. A mismatched pair does not fail at the door — it connects and behaves subtly wrong, and every bug it produces is unreal. If they came from different releases, redownload both and see if it survives. Known issues also lists the by-design behaviours that get reported as bugs.

Release tag *

The tag you took both halves from, e.g. v0.4.0. 🛑 Not the number the client prints — several builds have shipped under one version string, so the tag is the answer and the printed version is not.

What happened, and what you expected instead *

Concretely. "The Region Lock for Caelid arrived and the graces did not light" beats "region unlocking is broken" — the second one sends whoever reads it looking in the wrong place first.

Can you make it happen again?

If yes, the steps. If it happened once and you cannot reproduce it, say that — it is useful information and not a reason to skip reporting.

Your yaml *

The whole file, not the lines you think matter. Options interact, and the ones that turn out to matter are usually not the ones anybody suspected.

Client log

The file is <your Elden Ring install>\log\archipelago-<today>.log — one per day, and every launch starts a line reading SESSION START. 🛑 This is NOT ModEngine's log and NOT the Archipelago client console. Those two get sent often and neither contains a single line from this mod, so triage stalls on a follow-up. If what you are about to paste has no SESSION START in it, it is the wrong file.

Paste the whole thing. The log is appended across sessions, so an older session's errors sitting above the current one send triage down a dead end — this page trims to the last SESSION START for you and tells you if it did.

Was the DLC in play? *

enable_dlc is ON in the apworld's own defaults and OFF in the shipped template, so "I did not turn it on" does not settle it. Check the yaml you pasted above.

Anything else loaded?

These change the answer. RandomizerHelper.dll in particular is the most common cause of "my checks send but I never receive anything", and matt's "Add dll mod" launch path does not read our me3 profile — which is why AP items can show up as telescopes.

thefifthmatt's randomizer (enemies / starting class) Seamless Co-op Other mods through me3 Launched through something other than the shipped ap.me3 profile

Spoiler log

Say whether you have it. For anything about where an item ended up, the spoiler is not supporting evidence — it is the only thing that can settle the question. It is too big to paste here; attach it to the issue, or say you can send it.