Is using SetNWInt bad? I'm planning on using it to share the player's rank between the client and server, so it can be accessed by a function added to the Player's MetaTable. Is there a better way to share an integer between the server and clientside Player metatables?
You shouldn't use SetNWInt when you need something in realtime, at least i had bad experiences with it, but if you need to use it for share values between S/C there won't be a big problem
[QUOTE=gonzalolog;45350751]You shouldn't use SetNWInt when you need something in realtime, at least i had bad experiences with it, but if you need to use it for share values between S/C there won't be a big problem[/QUOTE]
I kind of need it in real time, as this is the base for an admin system. Is there a better way to share rank between server and client?
But i mean for something like sprint bar that uses data per tick, because this would cause a kind of flickering on people with lag, there's when you need SetupDataTable
[QUOTE=gonzalolog;45350810]But i mean for something like sprint bar that uses data per tick, because this would cause a kind of flickering on people with lag, there's when you need SetupDataTable[/QUOTE]
I read on the Wiki that DataTables are preferred. Should I use them anyway?
What kind of data you must share
[QUOTE=gonzalolog;45351064]What kind of data you must share[/QUOTE]
Just sharing an integer.
If you are just wanting to send group ranks to Clients when they first join and perhaps send the rank from Client to Server which will then broadcast it to all Clients; then SetNWInt is perfectly acceptable.
As gonza pointed out, they can be a bit iffy if you're calling SetNWInt extremely frequently - more than once a second.
Sorry, you need to Log In to post a reply to this thread.
