Speeding up SendUpdate.

[Slendergo]

Wait, so I cant share 1 function but you can share all @nilly's behaviors (+classes) and kithi's source with me?

but the people with access to his behaviours havent given them out to any one publicly i dont believe

[BlackRayquaza]

but the people with access to his behaviours havent given them out to any one publicly i dont believe

But he gave it to people

[Demon]

But he gave it to people

Why does it matter if ossi dude give people nilly code, it's nilly's fault for teaming with ossi dude

and also why does it matter is black dude share ossi stuff it's ossi dude fault for sharing with black dude

[dotskills]

Why does it matter if ossi dude give people nilly code, it's nilly's fault for teaming with ossi dude

and also why does it matter is black dude share ossi stuff it's ossi dude fault for sharing with black dude

How stupid are you?

[Stellar Spark]

uhh lemme list out all the things that can be improved in state management of the server

1.) delta compression (this is not sending the stattypes if they are mirrored on the client ack)
2.) probably better set management (lists are pretty standard but if you're really aching for speed im sure you can do something with arrays)
3.) export less stats
4.) lower tps where it's plausible (too low makes simulation shit itself)
5.) update throttling in castle, WC, nexus, and other high-volume player locations
6.) bitfielding the stats that ARE exported (pretty implausible in TCP)
7.) not using TCP because it's garbage for this

and there's a few others but im tired

note that i didn't rank those in any order just when they popped in my mind

[Demon]

How stupid are you?

Not stupid at all i'm excelling in grades :/

[ZeusAlmighty]

uhh lemme list out all the things that can be improved in state management of the server

1.) delta compression (this is not sending the stattypes if they are mirrored on the client ack)
2.) probably better set management (lists are pretty standard but if you're really aching for speed im sure you can do something with arrays)
3.) export less stats
4.) lower tps where it's plausible (too low makes simulation shit itself)
5.) update throttling in castle, WC, nexus, and other high-volume player locations
6.) bitfielding the stats that ARE exported (pretty implausible in TCP)
7.) not using TCP because it's garbage for this

and there's a few others but im tired

note that i didn't rank those in any order just when they popped in my mind

Reading that list, I think i may have to do some research as I dont know what quite a few of those means. If anyone with time/knowledge that can do this wants to help out, im offering $200 now. Or you can become a developer and get around $100 a month +. Thanks for the list btw Proph

[Slendergo]

Reading that list, I think i may have to do some research as I dont know what quite a few of those means. If anyone with time/knowledge that can do this wants to help out, im offering $200 now. Or you can become a developer and get around $100 a month +. Thanks for the list btw Proph

wow 100 a month xd