Where Is The Logic Banning New Characters For Existing Accounts on Congested Server?

[DragonFlyy]

This actually won't work for world servers that are designated as "Congested" worlds. It is not possible to create characters on those worlds at any time, until SE actively removes the "Congested" designation.

Other worlds might temporarily step in and out of the "Creation of New Characters Unavailable" status, because that status is dynamically assigned and removed based on live login counts. In this case, the above advice (creating a character in off-peak hours) will work.

If a world is marked as "Congested", however, it is blocked from all new characters until SE decides to reverse the decision, which is usually re-evaluted and applied in the next patch.

For years Balmung was designated as Congested. However, around 4am you could create a new character. Congestion is based on currently logged in characters. If your server is so busy that at all times there is a number of players logged in, then yes you can never create a character. However, the congested tag does disappear if the number of people logged in is below the predetermined log in amount. Best place to watch if it opens is https://arrstatus.com/
it auto refreshes and will let you use notifications when a server opens up.

[Valkyrie_Lenneth]

For years Balmung was designated as Congested. However, around 4am you could create a new character. Congestion is based on currently logged in characters. If your server is so busy that at all times there is a number of players logged in, then yes you can never create a character. However, the congested tag does disappear if the number of people logged in is below the predetermined log in amount. Best place to watch if it opens is https://arrstatus.com/
it auto refreshes and will let you use notifications when a server opens up.

No, big C Congested means it's completely locked from all characters until they remove that during maint. There were tons of posts here how Balmung being congested killed the server community cuz no new blood.


There are 2 types of server char locks.

Soft locks that update duri g the day, and hard locks that are applied during maint. Hard locks are always accompanied by a lodestone post.

https://na.finalfantasyxiv.com/lodes...a5f0c567b12427

[Risvertasashi]

From the "Congested Server" web page:

"New characters cannot be created on Congested Worlds."

So:

1) I have an account and I have a character on it that I can log in.
2) I can only play one character on the account at a time
3) If I log out of a character that exists I can log into another one that exists
4) If I log out of a character SE ban me from creating a new character on a 'congested' server.
5) SE define congestion as the number of PLAYERS actively playing, which is totally unrelated to them logging into an existing character OR creating a new one.

So explain to me SE why this ridiculous banning of existing players being able to create a new character on a server they already HAVE characters on.

There's not a particular logic to it, it's just system limitations.

Like how a character can get returner status even if you've been actively playing a separate characters, and how SE has to go to great lengths to make certain cosmetics account-wide, and so on. In a lot of ways, characters are kind of a pseudo-separate-account.

Someone at SE might have went "Yeah logically a person can only log in one character at a time so there's no reason to restrict character creation when they already have one on that server"; their system simply can't distinguish that this is the case vs someone with no characters there.

[Valkyrie_Lenneth]

The logic is likely that they just didn't design granular control over char creation limits.

It's just on or off.

[linayar]

The logic is likely that they just didn't design granular control over char creation limits.

It's just on or off.

They don't need to. They just need a hard limit per world and include 8 slots per account as allowed by the standard subscription in that limit.

[Moonlite]

Just another over site from either 1.0 or 2.0 team. That is probably to much work to fix, but everyone has known it is wrong since 2.0. Just have to use one of the work arounds. We need a FF17 that has taken into account these weird little overlooked issues. It is not game breaking. Just a general QoL that should have been included from the start.