onClientGameTypeStop

Context: mapmanager, client-side, argument resourceName. The reviewed implementation dispatches the notification during resource-stop handling, before its own map unloading. It does not promise that every dependent resource has completed cleanup or that a replacement game type is already ready.

// client.js: an observation with an explicit game-type resource filter.
on('onClientGameTypeStop', (resourceName) => {
  if (resourceName !== 'fd_lab_gametype') return;
  console.log('[Game-type observation] Clear only this feature\'s owned state.');
});

Substitute the actual resource name. Make timer/UI teardown safe to call twice and do not depend on another asynchronous tick from a stopped provider. If a feature captures NUI focus, release only the focus it owns; a simple notification handler is not a cross-resource focus coordinator.

Source: pinned mapmanager client . See game-type start, resource lifecycle, and stock contracts.