Skip to main content
Most integrations should continue to use their framework’s normal loaded/spawn lifecycle. Creator’s API is for resources that specifically need to open selection or know whether the player is still in the selection scene.

​
Server: OpenCharacterSelection

Use the optional force behavior only when you deliberately want to reopen selection for a player who is already active:
The function fails safely instead of stacking another selection session. Reasons can include states such as an already-open selection or an already-active character. Do not call this from an untrusted client event without your own server-side authorization.

​
Client: IsSelectionSceneActive

Useful for UI resources that should stay hidden while the player is choosing/creating a character. Example:

​
Framework lifecycle is still the primary integration surface

Normal resources should keep following the expected RSG player-loaded lifecycle. Creator completes it after appearance, final position and world readiness are resolved.
Read Character lifecycle before changing third-party HUD/inventory/medical code.

​
Spawn admin command

This is an administrator feature, not an API for players to submit coordinates. See Spawn locations.

​
Security model

Client/NUI data is a request. Character identity, slot entitlement and final spawn authorization are server decisions. That same rule should apply to your integrations: if your resource opens character selection or grants a special flow, authorize it on the server first.