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

Short answer

In most cases the straightforward approach works. The exceptions are specific and listed below.

  • Test it yourself where testing is cheap.
  • Revisit after a major patch if the behaviour changes.
  • Check the version you are actually running before assuming anything is broken.

Each Civilization entry reshuffles the rules enough that habits from the last one quietly stop working. Edge cases are genuinely rare, which is why the simple answer is usually the correct one. Nothing here depends on a setting you are unlikely to have.

Worth knowing alongside this

The awkward part is rarely the step itself, it is knowing which step comes first. It is worth separating what the game does from what players have concluded it does. Testing this yourself takes a few minutes and settles it definitively. A single check up front replaces a lot of guessing later.

The accepted community answer is broadly right and wrong in a specific way that matters here. The mechanic behind it is simpler than the discussion around it suggests. There is no hidden trick here that the game is keeping from you.

What to do instead

Most of the disagreement online comes from people describing different versions of Civilization. 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.

  • Check which version any conflicting advice was written for.
  • Try the straightforward approach before the elaborate one.
  • Stop and reassess after two failed attempts rather than repeating the third.
  • Note the exception cases — they are specific rather than vague.
  • Do not build a routine around an edge case.

The practical answer

If you are coming to this after a long break, the terminology has probably moved on. What follows assumes you are on a current install and have not modified it. The developers have changed their mind about this at least once, which explains the older advice. Where something depends on your platform or region, that is called out rather than glossed over.

Treat anything stated without a version number as provisional. Civilization is not shy about hiding useful information two menus deep, so some of this is simply knowing where to look. Where two approaches both work, the one with fewer moving parts is the one to keep.

When the usual advice fails

The community wisdom on this is roughly half right, and the half that is wrong costs the most time. Screenshots age faster than text, which is why this describes rather than shows. Patch notes move numbers around constantly; the shape of the answer holds even when a specific value shifts.

Most of the disagreement you will find online is two people describing different builds. Half the pages on this topic were written for a build that no longer exists, which is why they stop matching what you see. The short version is near the top on purpose; the reasoning is there if you want to know why.

Why it works this way

It helps to understand why a step exists, because then you can adapt it when your situation is slightly different. Nothing here assumes a particular playstyle beyond wanting the thing to work. None of this needs a paid tool, a third-party launcher or an account on a site you have never heard of.

Where people go wrong

  • Downloading a helper tool for something the game already does in its own menu.
  • Assuming a guide from an older season still describes the current version.
  • Treating a rare edge case as the normal behaviour and planning around it.

Civ 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.

What if none of this works for me?

Then something in your setup differs from the assumption — version, region or platform. Check those three before anything else.

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.

Work through it in the order above and cores palworld 1.0 stops being a question you have to look up again.