A franchise can make a world larger until the world becomes harder to enter.
The problem looks administrative at first.
More games mean more places, more characters, more history.
The map gains another coast. The chronology gains another war. The box art gains another familiar name.
Expansion looks like generosity.
But a setting isn’t only the material it contains.
It’s also the path by which that material can be read.
A world with one doorway can be entered.
A world with sequels, prequels, remakes, side stories, alternate continuities and reference books starts to require a floor plan.
Keep adding. Keep revising. Keep assuring everybody that no prior purchase has been wasted.
The franchise has a respectable reason for all of it.
A new entry needs a way in.
A sub-series needs room to become more than an appendix.
A reboot needs freedom from a numeral that has begun to resemble a warning label.
Growth makes access possible.
Lore has an equally respectable objection.
A prior claim doesn’t stay meaningful merely because later work hasn’t deleted it.
If every contradiction becomes a branch, every branch a provisional tier, and every tier a later invitation, chronology stops being a record.
It becomes a form of customer service.
The trouble starts with counting, which ought to be the easy part.
Resident Evil is commonly described as about ten core numbered games.
Or as nearly thirty titles, once the spin-offs are let into the room.
Its publisher’s own reported line folds the original Resident Evil 2 and its remake into one entry.
One convention finds a sequel history.
Another finds a family of retail objects.
Neither count has managed to make the other disappear.
An entry count is already an interpretation.
Tomb Raider makes this inconveniently plain.
One reference excludes a full retail remake when numbering the series, and the exclusion is what produces the number.
The figure looks like a fact.
The rule behind it is doing all the factual work.
Sub-series stage the same argument in a different costume.
A publisher can report Mega Man as one line, though Classic, X, Zero, ZX, Battle Network and Star Force carry their own casts, numbering and genre inflections.
Large military shooter brands do the same. Distinct sub-brands, different lead studios, separate visual identities, one reporting roof.
The commercial answer is tidy.
One recognizable roof, many rentable rooms.
The lore answer is much less interested in the lease.
There’s a cost to treating all those rooms as one house.
Mega Man X is set generations after the Classic series, and has its own cast and numbering.
Filing it as merely another instalment flattens the distance that made it distinct.
There’s a cost to breaking it off, too.
It makes a publisher’s combined line look like a clerical error.
And turns a loose continuity link into a border checkpoint.
Dormancy has the same false cleanliness.
A long gap between numbered entries is evidence of dormancy.
It is not proof of cancellation.
A franchise can pause long enough for its absence to acquire a mythology, then return and invoice that mythology as anticipation.
Reboots promise a cleaner entrance by making the past negotiable.
They do it in at least three incompatible ways.
Doom began as a numbered sequel, was restarted, and eventually arrived unnumbered.
It returned to the fast combat of the originals rather than continuing the game before it.
It reset the project and the public numbering without making earlier entries vanish.
Tomb Raider rebooted once, then rebooted again by reusing the original title outright.
God of War kept the numbering, the protagonist and the continuity, and reimagined nearly everything about how the game plays.
Three cases. One useful word covering all of them.
Three completely different demands made of the old work.
A reboot boundary is not a line drawn after the fact. It’s part of the new work’s meaning.
Does the numeral reset?
Does the protagonist survive?
Does the old chronology remain history, or persist only as a set of borrowable gestures?
Those are different invitations, even when they arrive in the same black box under the same logo.
Worlds have their own source problem, separate from the counting one.
Hyrule Historia gave Zelda an official three-branch timeline from outside the games.
Then a later entry’s directors declined to place it, keeping its position open to the players’ imagination.
The official map supplies the branches.
Its newest country refuses an address.
That isn’t necessarily a failure of lore.
Dark Souls runs a repeating fire cycle with no fixed calendar at all.
Halo stretches across a hundred thousand years of prior history before its main setting even begins.
One world withholds the measuring stick.
Another supplies an extravagant one.
Scale and readability are not the same property.
Halo at least gives its uncertainty a name.
Settled published material is core canon unless the developers say otherwise.
Unconfirmed drafts, marketing campaigns and merchandise copy are apocrypha. Effectively canon until proven otherwise.
That’s more honest than pretending every loose thread is already tied.
It’s also an oddly demanding kindness.
The reader now has to remember not only what happened, but which tier it happened on.
Other systems multiply a world without multiplying one settled past.
An imported world state carries a player’s prior decisions forward, so the continuity is personal rather than published.
Another game placed much of its early lore in cards outside the playable game entirely, on a website and a companion app.
One turns continuity into a carried record.
The other makes the archive part of the door.
Then a crossover arrives, and the map acquires a tempting false bridge.
A raid can bring one numbered world’s characters and lore into another’s, though the two share no geography and no history.
It may be canon to its host, a guest appearance, or a question the event deliberately left bounded.
It does not secretly weld two continents together.
The case for expansion is strong.
It gives the newcomer an unnumbered beginning, the neglected sub-series a future, and the returning player another way to inherit a place.
It lets a world stay inhabited instead of preserved behind the authority of an ending.
The cost is that entry order becomes an argument.
Internal chronology can locate a story.
A recommended reading order can offer a route through it.
Neither is the other.
A published guide, a developer policy, an interview and a fan wiki’s cross-referencing all make claims with different authority.
Calling all of them “the canon” is efficient in roughly the way a locked door is efficient.
The case for coherence is strong as well.
A declared boundary lets a scene keep its consequence.
A source tier makes an uncertainty visible instead of laundering it into trivia.
A finite chronology can be read without requiring a private seminar in franchise accounting.
Its cost is a smaller future.
The reboot becomes suspect because it discards history.
The side story becomes disposable because it complicates the line.
An ambiguity becomes an error because nobody supplied a footnote.
A world is made readable by refusing some of the rooms it could have built.
One instinct protects legibility. The other protects membership.
Every franchise old enough to have this problem has already chosen, usually without saying so.
What kind of reader does a world’s growth make impossible?