There will be a cap on the maximum number of users per world. We are trying to devise an automated approach so that when the game reaches saturation it will create a new world.
Here's a hypothetical situation...
Say you set it at 700 players.
And 700 players join.
Player 701 joins, and is sent to a new world.
No one else joins for a week.
Suggestion: Set it so that when one world is full, another one is created, but it won't start until there are at least 300 (400?) players. Once it reaches that number, a customary e-mail goes out saying the world is ready, and the 24 hour prep time begins.
Of course, what happens if that magic number is not reached for X days, or ever?
Actually the generation of the world [and the script that would drive it] is the easy part. the formulas at the heart of it otherwise are the tricky part [say the ones that determine the optimum player count for the world in real time, as opposed to setting a fixed number which may need to change as more airports are added or updated]. odds are there'd be a flag for something like if no public worlds < 66% full OR no public worlds < 1/2 finished. boom. new world else nothing. As odds are, given the choice between a world that's
mostly full, and a world that's
mostly not full they'd choose the emptier one [ceteras paribus].
We're not going to be dictatorial and kick you automatically from world X to world Y when X is "full". we'll just cut off new players from a world when it's "actually" full and let them congregate otherwise to their choosing.
