playerActivated

Context: sessionmanager, client-side, with no documented arguments. Use this as a notification from that provider, not a universal guarantee that your framework’s character, inventory or permissions have loaded.

// client.js, in a resource using the stock sessionmanager environment.
on('playerActivated', () => {
  console.log('[Session observation] Provider activation notification received.');
});

Do not infer a permanent account identity or assume this hook is emitted by every custom spawn/session system. For ped-dependent work, verify the actual ped state or use the documented spawnmanager event when spawnmanager is the provider. For framework data, use that framework’s own readiness contract.

Keep initialization idempotent and handle resource restart separately; registering a listener after the notification already occurred does not replay it. A production feature should not depend on an undocumented strict ordering between this hook and sessionInitialized.

Source: official sessionmanager resource manual . Related: resource lifecycle and stock-event contexts.