[ script:es_extended] [ERROR] Server Callback not registered, name: esx_job_creator:checkAllowedActions, invoker resource: esx_job_creator
[ script:es_extended] [ERROR] Server Callback not registered, name: esx_job_creator:getMarkers, invoker resource: esx_job_creator
[ script:es_extended] [ERROR] Server Callback not registered, name: esx_job_creator:getMarkers, invoker resource: esx_job_creator
[ script:es_extended] [ERROR] Server Callback not registered, name: esx_job_creator:checkAllowedActions, invoker resource: esx_job_creator
i always get this error but i don´t no why and what that is… pls help me.
The server file did not start. It either errored, or is not set to run in the fxmanifest.lua
this is the only error that occurred, but what do you mean by the fxmanifest?
The fxmanifest.lua file is required to declare every file that the resource will use, and it is set to declare where that file should be used, server or client. I highly doubt the issue lies in the fxmanifest, I would suggest ensuring the resource after the server is fully started and nothing is printing to the console, and verifying the resource starts properly.
[script:esx_job_creat] SCRIPT ERROR: @esx_job_creator /server/database.lua:39: attempt to call a nil value (global ‘format’)
this is the only other error i get
Fix that error, and then test the resource.
how do i fix the error i have never seen the error in my life
Resolve what “format” is supposed to be, then make it that.
what exactly should I change there
You need to call the namespace that the “format” function is inside of, which is “string”, so you need to call “string.format” not just “format”.
EDaniel
December 8, 2023, 8:10pm
11
How exactly do I write that in there
You need to call “string.format” instead of just “format”, so highlight the word “format” and the replace it with “string.format”…
EDaniel
December 8, 2023, 8:11pm
13
i’m sorry but i don’t have much knowledge about scripting yet
EDaniel
December 8, 2023, 8:23pm
14
i can’t thank you enough it worked but now i have one little thing that is giving me headaches and that is this:
Provide the lines of code that errors indicate are in the stack trace. Provide context code around the line as well when possible, so like 5-10 lines before the erroring line, and 5-10 lines after the erroring line.
Without your code, people are left having to try to find the code and then they end up with stuff like this
Where the github doesn’t even have as many lines of code as your file so there’s absolutely no way to deduce the issue.
The issue is on line 477 of your skinchanger file