Onesync scripts

[Systematic]

Just a quick question,

When you activate Onesync for your server will the scripts still work or be bugged if you don’t optimize them to 33 slots or higher?

[ChieF-TroN]

They break

[Systematic]

well there goes my free time.

[ChieF-TroN]

I would go another step and just fix the code so you dont have to do it twice refer to the cookbook.

GET_ACTIVE_PLAYERS: the replacement for player loops

Originally published at: https://cookbook.fivem.net/2019/06/29/get_active_players-the-replacement-for-player-loops/ Just a quick hint: when writing new client-side scripts in Lua/JS (C# already has the Players list doing exactly this), you can loop through players by using the GET_ACTIVE_PLAYERS native. See below for an example of before/after: Before… for i = 0, 255 do if NetworkIsPlayerActive(i) then local ped = GetPlayerPed(i) – do stuff end…

[Systematic]

Much obliged!

[Flawws]

Couldn’t you make a script which alters the 32 loops?

[Systematic]

Might be possible.

[ChieF-TroN]

Couldn’t you make a script which alters the 32 loops?

Yes, you could have it do thru 255, which is much more cpu intensive when you could just use the solution provided in the cookbook and have it more efficient, and also the solution in the cookbook makes it so you never have to worry about the slot count again. So, if you decide to make your server 500 slots in the future when the non-ai version gets released (assuming it does) then you will not have to worry about editing your scripts again to reflect the new player cap.