There is a simple version of this and a complete version, and both are below in that order.

Short answer

The direct answer is above the fold; the reasoning underneath is there for when the direct answer does not fit your situation.

The accepted community answer is broadly right and wrong in a specific way that matters here. Testing this yourself takes a few minutes and settles it definitively. If you are coming to this after a long break, the terminology has probably moved on.

When the usual advice fails

The mechanic behind it is simpler than the discussion around it suggests. Nothing here depends on a setting you are unlikely to have. It helps to understand why a step exists, because then you can adapt it when your situation is slightly different. Most of the disagreement online comes from people describing different versions of Elden Ring Nightreign.

Edge cases are genuinely rare, which is why the simple answer is usually the correct one. What follows assumes you are on a current install and have not modified it. It is worth separating what the game does from what players have concluded it does.

Why it works this way

Patch notes move numbers around constantly; the shape of the answer holds even when a specific value shifts. Where two approaches both work, the one with fewer moving parts is the one to keep. Elden Ring Nightreign is not shy about hiding useful information two menus deep, so some of this is simply knowing where to look.

  • Try the straightforward approach before the elaborate one.
  • Test it yourself where testing is cheap.
  • Write down what you changed, so you can undo exactly one thing if it goes sideways.
  • Do not build a routine around an edge case.

The practical answer

There is usually a fast way and a reliable way, and it is worth knowing which one you are choosing. The developers have changed their mind about this at least once, which explains the older advice. Most of the disagreement you will find online is two people describing different builds. The short version is near the top on purpose; the reasoning is there if you want to know why.

Screenshots age faster than text, which is why this describes rather than shows. Half the pages on this topic were written for a build that no longer exists, which is why they stop matching what you see. A single check up front replaces a lot of guessing later.

Worth knowing alongside this

None of this needs a paid tool, a third-party launcher or an account on a site you have never heard of. Treat anything stated without a version number as provisional. Anything that behaves differently on console than on PC is flagged where it matters.

If a step reads as obvious, do it anyway — the obvious ones are the ones people skip and then wonder about. Do the cheap check before the expensive one — that ordering alone saves most of the frustration. Nothing here assumes a particular playstyle beyond wanting the thing to work.

What to do instead

The community wisdom on this is roughly half right, and the half that is wrong costs the most time. The awkward part is rarely the step itself, it is knowing which step comes first. Where something depends on your platform or region, that is called out rather than glossed over.

Where people go wrong

  • Changing five things at once and then not knowing which one helped.
  • Treating a rare edge case as the normal behaviour and planning around it.
  • Assuming a guide from an older season still describes the current version.
  • Copying a setup wholesale from a streamer without understanding what each part does.

Nightreign FAQ

What is the short answer?

It is the paragraph near the top. Everything after it exists for the cases where that paragraph does not quite fit.

Is there a faster method?

Sometimes, at the cost of reliability. Where that trade exists it is described rather than recommended blindly.

Does this work the same on console and PC?

The logic is identical. Menu paths and button prompts differ, and any real difference is flagged above.

Why do other guides describe this differently?

Most were written for an earlier version and never revisited. Compare the steps against what your build actually shows.

If you only take one thing from this: the answer near the top is the part that matters, the rest is context.