This comes up often enough in Elden Ring that it deserves a straight answer rather than a thread to scroll through.

Short answer

Most of the difficulty here is knowing what to skip.

The first attempt should be about understanding the shape of the problem. The mechanic behind it is simpler than the discussion around it suggests. The developers have changed their mind about this at least once, which explains the older advice.

What to do next

Advice written for launch conditions is the most common source of confusion here. Advice that worked for someone else may have depended on something they never mentioned. Two sources disagreeing usually means one of them stopped being updated. A recommendation without a reason cannot be adapted when your situation differs.

Most guides optimise for efficiency, which is not always what you want from a game. Elden Ring is not shy about hiding useful information two menus deep, so some of this is simply knowing where to look. The step people skip is the one that makes the rest work.

When your situation differs

Nothing here depends on a setting you are unlikely to have. Patch notes move numbers around constantly; the shape of the answer holds even when a specific value shifts. Consensus forms early and updates slowly, which is why the top result can be years stale.

  • Do not build a routine around an edge case.
  • Revisit after a major patch if the behaviour changes.
  • Read the whole sequence once before doing the first step.
  • Try the obvious thing before the clever one.
  • Prefer the version with fewer moving parts.
  • Try the simplest explanation before the interesting one.

Common wrong turns

Doing something the slow way once teaches more than doing it the fast way ten times. Older threads are worth reading for the reasoning rather than the conclusions. The right approach depends on where you are, and most advice assumes a starting point it never states. It is worth separating what the game does from what players have concluded it does.

The awkward part is rarely the step itself, it is knowing which step comes first. The accepted community answer is broadly right and wrong in a specific way that matters here. There is a version of this that takes ten minutes and a version that takes an evening, and both are valid.

When the usual advice fails

Half of what gets described as a bug is a design decision people dislike. Small habits compound faster than any single technique. Testing this yourself takes a few minutes and settles it definitively.

Do the cheap check before the expensive one — that ordering alone saves most of the frustration. Edge cases are genuinely rare, which is why the simple answer is usually the correct one. Trying the obvious thing first is underrated and costs almost nothing.

Why it works this way

Where something depends on your platform or region, that is called out rather than glossed over. If something feels harder than described, the difference is usually a missing prerequisite. Knowing what to skip is worth as much as knowing what to do.

Where people go wrong

  • Changing five things at once and then not knowing which one helped.
  • Taking the highest number in a comparison without checking what it was measured on.
  • Reading a summary of the patch notes instead of the patch notes.
  • Treating a rare edge case as the normal behaviour and planning around it.

Elden Ring FAQ

Do I need any mods or third-party tools for this?

No. Everything described here works with the base game on any supported platform.

Is this specific to one platform?

The reasoning is not. Anything that genuinely differs by platform is called out where it comes up.

Why does the community disagree about this?

Because most disagreements are two people describing different versions, platforms or skill levels without saying which.

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.

Come back to the caveats list if it does not work first time — the answer is almost always in there.