Spielerando

Companions vanish from the party, or too many load in after the limit changed

Saving only the current party loses everyone who stayed behind at camp, and saving a longer party than the game now allows breaks the screen. Here is the list to keep, and how to tidy a party that no longer fits on load without losing anyone.

Why this works

Two records of the same fact will one day disagree, so let one of them be the truth and make the other follow. An ordered list says who is in and who comes first, and everything else can be worked out from it, whatever the limit has become.

When not to use it

Do not trim automatically when losing a companion would hurt the story, such as one who carries a plot. Ask the player who stays, or keep the plot character fixed. The rule is only fair for interchangeable helpers.

In the full entry

  • What to build, step by step
  • Starting values and the reason for each
  • 3 common mistakes and the fix
  • 28 lines of example code with 3 checks that pass
  • How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "Companions vanish from the party, or too many load in after the limit changed" (read_entry rpg-party-roster-and-limit) in my game. Build it step by step, and show me how you checked that it works.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP