There is a simple version of this and a complete version, and both are below in that order.
Short answer
In most cases the straightforward approach works. The exceptions are specific and listed below.
Testing this yourself takes a few minutes and settles it definitively. Trying the obvious thing first is underrated and costs almost nothing. The useful part of any answer is the part that tells you what to do differently.
What to do instead
Nothing here depends on a setting you are unlikely to have. The accepted community answer is broadly right and wrong in a specific way that matters here. Screenshots age faster than text, which is why this describes rather than shows. Knowing what to skip is worth as much as knowing what to do.
Advice written for launch conditions is the most common source of confusion here. Where two approaches both work, the one with fewer moving parts is the one to keep. Doing something the slow way once teaches more than doing it the fast way ten times.
What to do next
Most guides optimise for efficiency, which is not always what you want from a game. Do the cheap check before the expensive one — that ordering alone saves most of the frustration. It is worth separating what the game does from what players have concluded it does.
- Note the exception cases — they are specific rather than vague.
- Write down where you started, so you can describe the problem if you need help.
- Note which version you are on before comparing against anything written elsewhere.
- Prefer the version with fewer moving parts.
- Check which version any conflicting advice was written for.
What you can skip
Consensus forms early and updates slowly, which is why the top result can be years stale. Nothing here assumes a particular playstyle beyond wanting the thing to work. The step people skip is the one that makes the rest work. A recommendation without a reason cannot be adapted when your situation differs.
The interesting question is usually why the obvious approach fails. The right approach depends on where you are, and most advice assumes a starting point it never states. Edge cases are genuinely rare, which is why the simple answer is usually the correct one.
The practical answer
A method that works but cannot be explained tends to stop working without warning. Small habits compound faster than any single technique. The first attempt should be about understanding the shape of the problem.
If a step reads as obvious, do it anyway — the obvious ones are the ones people skip and then wonder about. If something feels harder than described, the difference is usually a missing prerequisite. The mechanic behind it is simpler than the discussion around it suggests.
Where to start
There is usually a fast way and a reliable way, and it is worth knowing which one you are choosing. There is a version of this that takes ten minutes and a version that takes an evening, and both are valid. Advice that worked for someone else may have depended on something they never mentioned.
Where people go wrong
- Testing on a modified install and reporting the result as normal behaviour.
- Ignoring the platform-specific note and then wondering why the steps do not line up.
- Copying a setup wholesale from a streamer without understanding what each part does.
Elden Ring FAQ
Why does the community disagree about this?
Because most disagreements are two people describing different versions, platforms or skill levels without saying which.
Is this specific to one platform?
The reasoning is not. Anything that genuinely differs by platform is called out where it comes up.
Is this still accurate after the latest Elden Ring update?
The method is; individual numbers may not be. If a value on your screen differs, trust the screen and keep the sequence.
Is there a faster way to do this?
Usually, and it usually trades reliability for speed. Which one you want depends on whether you plan to repeat it.
If you only take one thing from this: the answer near the top is the part that matters, the rest is context.