That's exactly where the issue lies and it's rather arbitrary. The dev teams are constantly doing brief maintenances to keep from the world overloading and crapping out, which is why I'm baffled that they removed the inactivity boot. "All World's Maintenance" every seven days just to keep the proverbial hamsters on their wheels, but they don't lighten the load the poor hamsters are hauling. It's very strange.
I too haven't had much issue with world cap queues, but if you hearken back to when Yoshida first answered this question; he did make a statement that the character creation restriction was to pre-empt the congestion and overload issue.
So look at it this way, your maximum occupancy is 200 (theoretically) and 250 people are trying to log on. So you put an auto-restrict on new occupants at say 150. Now think about how 50 of those occupants are actually afk and not actively playing the game. Hence, constant creation restriction.
I too haven't had much issue with world cap queues, but if you hearken back to when Yoshida first answered this question; he did make a statement that the character creation restriction was to pre-empt the congestion and overload issue.
So look at it this way, your maximum occupancy is 200 (theoretically) and 250 people are trying to log on. So you put an auto-restrict on new occupants at say 150. Now think about how 50 of those occupants are actually afk and not actively playing the game. Hence, constant creation restriction.
What a colossal waste of time and energy.
