sessionInitialized

Context: stock sessionmanager, client-side, with no documented arguments. The notification belongs to session setup. It does not establish a universal point at which every framework has created a character or loaded account data.

// client.js: diagnostic observation, not an authentication decision.
on('sessionInitialized', () => {
  console.log('[Session observation] Session initialization notification received.');
});

Use this for provider-specific integration only after confirming the resource is present. Do not infer that a ped must or must not exist solely from this event, and do not promise a strict ordering against playerActivated that the public contract does not guarantee.

Test joining and restarting your consuming resource independently. A listener added after a one-time notification is not automatically called, so a feature also needs an explicit current-state initialization path where appropriate. Keep that path idempotent instead of giving a loadout or reward every time the resource restarts.

Source: official sessionmanager documentation . See playerActivated, resource lifecycle, and the stock event directory.