- summary: Whether the character was created, and broadly why not.
- area: Game.Character.Management
- confidence: 0.88
Whether the character was created, and broadly why not.
- Kind enum
- Area Game.Character.Management
- Named by beta
THE OUTCOME OF A CHARACTER CREATION. Only CREATE_OK means the character exists.
CREATE_ERROR_INVALID_NAME is the one that carries detail: the companion
NameCompliance member says which naming rule was broken. Every other value
is the whole story on its own.
EXPECT VALUES YOU DO NOT KNOW. This enum has grown twice since the reference build - six values became eight, then nine - and the newer ones have no published names. Treat any value other than CREATE_OK as a refusal, show the server's own message if you have one, and do not switch exhaustively on it.
Not sent on its own — it is a member type of CharacterCreationResultEvent, never sent alone. proven
Used by
Values
| Value | Number | Meaning |
|---|---|---|
CREATE_OK | 0 | The character was created. The name is the reference build's, matched by NUMBER. Values 0-5 are present on every dumped build; the enum has only ever GROWN (6 values through 3.4.18.19, 8 from 3.5.3.1, 9 from 3.6.10.10), which is what makes the low numbers safe to carry across. No dumped client distinguishes one value from another, so only the NUMBER is proven. |
CREATE_ERROR_NO_REASON | 1 | Refused, and the server gives no reason. The name is the reference build's, matched by NUMBER. Values 0-5 are present on every dumped build; the enum has only ever GROWN (6 values through 3.4.18.19, 8 from 3.5.3.1, 9 from 3.6.10.10), which is what makes the low numbers safe to carry across. No dumped client distinguishes one value from another, so only the NUMBER is proven. |
CREATE_ERROR_INVALID_NAME | 2 | Refused because of the name; read the companion reason for which rule it broke. The name is the reference build's, matched by NUMBER. Values 0-5 are present on every dumped build; the enum has only ever GROWN (6 values through 3.4.18.19, 8 from 3.5.3.1, 9 from 3.6.10.10), which is what makes the low numbers safe to carry across. No dumped client distinguishes one value from another, so only the NUMBER is proven. |
CREATE_ERROR_TOO_MANY_CHARACTERS | 3 | You already hold as many characters as this account allows. The name is the reference build's, matched by NUMBER. Values 0-5 are present on every dumped build; the enum has only ever GROWN (6 values through 3.4.18.19, 8 from 3.5.3.1, 9 from 3.6.10.10), which is what makes the low numbers safe to carry across. No dumped client distinguishes one value from another, so only the NUMBER is proven. |
CREATE_ERROR_NOT_ALLOWED | 4 | Creation is not permitted for this account right now. The name is the reference build's, matched by NUMBER. Values 0-5 are present on every dumped build; the enum has only ever GROWN (6 values through 3.4.18.19, 8 from 3.5.3.1, 9 from 3.6.10.10), which is what makes the low numbers safe to carry across. No dumped client distinguishes one value from another, so only the NUMBER is proven. |
CREATE_ERROR_NEW_PLAYER_NOT_ALLOWED | 5 | Creation is not permitted for a new player on this server. The name is the reference build's, matched by NUMBER. Values 0-5 are present on every dumped build; the enum has only ever GROWN (6 values through 3.4.18.19, 8 from 3.5.3.1, 9 from 3.6.10.10), which is what makes the low numbers safe to carry across. No dumped client distinguishes one value from another, so only the NUMBER is proven. |
Recovered with score 205, confidence 0.88, margin 205 over the runner-up. A margin close to the score means nothing else came near; a thin margin means a decoy nearly won. Members recovered: 6 of 9.
Aucun avis à afficher.