[Bug] Client skips onResourceStop/onClientResourceStop

[0xMxh]

Summary

On FiveM for GTAV Enhanced, client-side onResourceStop / onClientResourceStop never fire when a resource is stopped or restarted. The client remounts scripts with no stop handlers in between. resource.rpf is often re-downloaded into the Enhanced servercache. Server-side onResourceStop on the same shared script works normally.

Issue type

Client

Repro rate

Always

Server build version

FXServer-early-access b110 win32

OS

Windows 11

CPU

No response

GPU

No response

RAM

No response

Storage type

None

Connection type

None

ISP and bandwidth

No response

DxDiag

No response

Network graph

No response

Platform

None

OS version / distribution

No response

CPU

No response

RAM

No response

Using txAdmin?

None

Hosting provider

None

Machine type

None

/perf endpoint output

No response

DDoS protection

No response

ulimit -n value (Linux only)

No response

Docker Compose file (Docker only)

No response

Steps to Reproduce

1. Run FiveM for GTAV Enhanced.
2. Add a minimal resource test with only:

fxmanifest.lua
  fx_version 'cerulean'
  games { 'gta5', 'gta5enhanced' }
  shared_script 'shared.lua'

shared.lua
  print(('[%s] loaded in %s'):format(
    IsDuplicityVersion() and 'SERVER' or 'CLIENT',
    GetCurrentResourceName()
  ))

  AddEventHandler('onResourceStart', function(resourceName)
    if resourceName ~= GetCurrentResourceName() then return end
    print(('[test] START on %s'):format(IsDuplicityVersion() and 'SERVER' or 'CLIENT'))
  end)

  AddEventHandler('onResourceStop', function(resourceName)
    if resourceName ~= GetCurrentResourceName() then return end
    print(('[test] STOP onResourceStop on %s'):format(IsDuplicityVersion() and 'SERVER' or 'CLIENT'))
  end)

  AddEventHandler('onClientResourceStop', function(resourceName)
    if resourceName ~= GetCurrentResourceName() then return end
    print(('[test] STOP onClientResourceStop on CLIENT'))
  end)

3. Start the server, join with the Enhanced client.
4. Open BOTH: server console + client F8.
5. Run ensure test, START appears on server and in F8 (expected).
6. Run stop test then ensure test.
7. Observe:
   • Server console: STOP onResourceStop fires (works).
   • Client F8: no STOP, START / loaded run again immediately (broken).

Expected Behavior

Normally, onResourceStop and/or onClientResourceStop should fire on the client when the resource is stopped.

Actual Behavior

Nothing happens — those events never fire, and START runs right after.

Evidence

F8 excerpt:
Downloading file resource.rpf to .../FiveM for GTAV Enhanced/servercache/...
[CLIENT] loaded in test
[CLIENT] loaded in test
[CLIENT] loaded in test
(no STOP lines)

Server onResourceStop for other resources still completes normally (server-side only).

Additional Context

No response

[Jose76Tron]

Can confirm this does happens

[wolfram-cfx]

Thanks, we are looking into this. So the client resource does not receive its own onResourceStop and onClientResourceStop before it is erased? Because restarts of resources are just deletion of the resource and recreation.

[0xMxh]

Yes, exactly. On the client, the resource being stopped/restarted never receives its own onResourceStop / onClientResourceStop. Example: if I create an entity on the client and try to delete it in the stop handler, it is not deleted.

[Tikozaal]

same when i ensure any scripts :

ensure admin
[21:06:25] [ info] [citizen-server-i] Stopping resource admin
[21:06:25] [ info] [citizen-server-i] Stopped resource admin
[21:06:25] [ info] [citizen-server-i] Starting resource admin
[21:06:25] [ info] [citizen-server-i] Starting resource admin
[21:06:25] [ info] [citizen-server-i] Started resource admin
cfx> ensure boombox
[21:07:18] [ info] [citizen-server-i] Stopping resource boombox
[21:07:18] [ info] [citizen-server-i] Stopped resource boombox
[21:07:18] [ info] [citizen-server-i] Starting resource boombox
[21:07:18] [ info] [citizen-server-i] Starting resource boombox
[21:07:18] [ info] [citizen-server-i] Started resource boombox

[0xMxh]

Indeed the script starts twice, there are two or three problems with the launch and stop of a script !

[Gogsi]

A fix for this bug has been implemented and is available in August 11 Patch. Please try again and let us know if the issue persists. Thanks for your help!

[Tikozaal]

It works perfectly