Skip to main content
Turn on Config.Debug = true temporarily, reproduce one clean sequence, then read both the server console and client F8 around that attempt.

​
Version checker says the package is outdated

Creator checks the current public RCO Identity release once at startup. If you see:
install the complete latest RCO Identity package rather than replacing only one resource. If the remote check is unavailable, RCO prints a warning and continues normally. A failed version request by itself should not stop selection or appearance.

​
Version mismatch between Creator and Appearance

If you see:
Creator and Appearance came from different releases. Replace both with the matching files from the same RCO Identity package. Do not silence the warning by manually changing only the version field in an old fxmanifest.lua.

​
Selection never opens

Check these first:
  1. rco-appearance started successfully before Creator;
  2. the correct framework core started before both RCO resources;
  3. the stock multicharacter/vorp_character resource is not still running;
  4. your database/storage initialization completed;
  5. the player’s framework session/identifier is actually ready.
Cold-start problems on VORP are especially sensitive to startup/lifecycle timing; do not “fix” them by firing the selection event repeatedly from the client.

​
Selection opens twice

That means two entry points/resources are trying to own the same flow. Creator rejects duplicate/opening sessions, so find the other caller instead of adding delays. Typical causes:
  • stock selector still ensured;
  • third-party selector still listening for framework login;
  • custom resource calling OpenCharacterSelection again on a normal login event.

​
Character ped is missing or floating in the selection scene

Test at high FPS and test every configured slot. Selection actors are scene entities, not normal gameplay peds; attachment/scenario readiness can reveal timing bugs that never appear at 60 FPS. Current seated preview slots use controlled anchor/pose handling to reduce scenario placement variance. If one slot still looks wrong, include the affected slot number and a screenshot/video.

​
New character gets stuck between Creator and spawn

Separate the stages:
The last successful line in debug output usually tells you which system actually failed.

​
Spawn selector does not appear

Check the configured selector mode and whether the character is being forced to Last Position for a special state such as jail. A new-character-only mode will intentionally skip the full selector for existing characters according to the configured flow.

​
Edited config spawn but nothing changed

Existing spawn locations are database-backed after the initial seed. Use /rcospawns for live changes. See Spawn locations.

​
HUD / inventory starts too early or twice

Do not immediately add a custom RCO event to the HUD. First verify that the resource is listening to the normal framework lifecycle only once. Creator is designed to finalize that lifecycle after the character is actually spawned. See Character lifecycle.

​
Medical/death state is wrong after login

On RSG, verify the character’s persisted dead/health state and any custom RestorePersistedDeath bridge. On VORP, avoid adding RSG-style health handling into Creator; VORP Core owns that lifecycle.

​
Player has the wrong number of slots

Follow the resolver order in Character slots. Check Discord/custom slot configuration and the final slot cap configured by your build.

​
/rcospawns permission denied

Grant the ACE or update your custom CanManageSpawns rule:

​
What to send support

Include:
  • installed RCO Identity version and any version-check warning;
  • framework (RSG/VORP);
  • new or existing character;
  • exact sequence from connect to failure;
  • server debug lines for that attempt;
  • client F8 lines for that attempt;
  • whether the issue happens after a resource restart, full server restart or both;
  • names of any third-party multicharacter/spawn/medical resources still involved.