The OneSync EAP and you

FiveM Announcements
90

I have already modified everything unfortunately I still have the problem

91

Are you using Linux by any chance?

92

yes why? ^^

93

And you are running the latest version?

94

I use the version of December 15

95

Hmm, could you please make a screenshot and provide some reproduction steps, that would be neat.

96

screenshots of? I do not see what I can capture to show you that it does not work ^^

97

Or some way of proofing this is actually the case.

98

20181217183745_1
20181217183745_11904×1042 276 KB
it’s in French sorry ^^

1 Like
99

it’s set some parameters were not set for the 64 thank you and sorry for disturbing

1 Like
100

There are going to be loads of resources iterating 0,31 (or 1,32 I suppose?) that are going to be “broken” with OneSync. I think this is the first of many posts about this that will be inbound.

1 Like
101

■■■■■■■: Error while running the system event handling function for the ■■■■■■■ resource:

Error running system event handling function for resource ■■■■■■■: citizen:/scripting/lua/scheduler.lua:41: Failed to execute thread: Execution of native 000000002f7a49e6 in script host failed.
stack traceback:
        [C]: in upvalue '_in'
        citizen:/scripting/lua/natives_server.lua:405: in function 'TriggerClientEventInternal'
        (...tail calls...)
        rconlog_server.lua:12: in upvalue 'handler'
        citizen:/scripting/lua/scheduler.lua:219: in function <citizen:/scripting/lua/scheduler.lua:218>
stack traceback:
        [C]: in function 'error'
        citizen:/scripting/lua/scheduler.lua:41: in field 'CreateThreadNow'
        citizen:/scripting/lua/scheduler.lua:218: in function <citizen:/scripting/lua/scheduler.lua:182>
InvokeNative: execution failed: Argument at index 1 was null.
102

Yeah i got the same error

103

Doing what exactly? Provide a repro instead of “hurr durr” I get an error. Same goes for you @Morgan_Braco

Explain what you did (i.e. what you entered into the rcon), what you expected it to do and provide reproducible steps. Otherwise this error is simply due to your own mistake and not a OneSync issue.

104

its an ESX issue, not a OneSync. I’m aware of that.
It happens when i install ESX and then run the server

2 Likes
105

in the ■■■■■■■ script I modified this client side:`AddEventHandler(‘rlUpdateNames’, function()
local names = {}

for i = 0, 31 do
    if NetworkIsPlayerActive(i) then
        names[GetPlayerServerId(i)] = { id = i, name = GetPlayerName(i) }
    end
end

TriggerServerEvent('rlUpdateNamesResult', names)

end)`

and this server side: ■■■■■■■({ msgType = 'serverStart', hostname = 'lovely', maxplayers = 64})

But the error is always present at every connection of the players

1 Like
106

Is there anyway to do this with Zap? When i try to set the server player amount it resets back to 32.

107

Screenshot_2
I get this every time in like 3 mins

3 Likes
108

Afaik zap only offers 32 slots maximum, you’d have to contact them to make arrangements.

Please verify that doesn’t normally happen, seems like a pretty generic error to me.

1 Like
109

i get this error when a second person tries to join the server, has anyone gotten this error ? Screenshot_52

2 Likes