I’ve got a central framework script, and about 4 or 5 resources that use it as a dependency defined in the fxmanifest. When I connect the first time, everything works fine, when I disconnect and rejoin, the scripts that are dependant on the framework stop. There’s nothing in the console nor the client log.
1 Like
also experiencing this issue.
What’s the framework you are using? Is there anymore detailed info about the issue?
the framework is custom built for my server. I cant see any errors on neither the client nor the server logs. When I remove the dependency definition from the fxmanifest.lua, the scripts dont unload, but the framework wont always start before the scripts that are dependent on it.
Well, maybe this is a load order issue. Is your framework one of the first resources to start? Could you show me how the resources are being initialized?
server.cfg:
…
ensure framework
exec resources.cfg
…
resources.cfg
start [dependencies]
start [scripts]
start [luxart]
start [maps]
start [audio]
start [vehicles]
start [weapons]
start [eup]
start [radio]
I should mention that framework lays within the [scripts] folder as well, I’m not sure if that makes any difference.
How you have it is fine. Nicely organized. 
However, you could change the ‘start’ to ‘ensure’. I would recommend this since they are slightly different. ‘ensure’ will start the resource if it’s not running and restart the resource if it’s already running while ‘start’ only starts it if it’s not running and doesn’t do anything else. Try this for both “[dependencies]” and “[scripts]”
i’ll give it a try and let you know. thanks for the tip
1 Like
The issue still appears to be persistent.
Well I would need more details about the issue then. Possibly to even see the source of the Framework to see how it works. My only guess that I can think of is that there’s something wrong internally with the Framework that causing this since the tip I gave didn’t seem to do anything. If you’d like, you can send me a message on Disc: Anarchyxd
And if we can resolve the issue I’ll post what the issue was and you can mark it as solved.
As a last resort, both you and @OBSRP could wipe both server and client cache. Server cache is located in the same directory as your resources folder(./cache/files). There’s a chance this could help.