Upcoming Handling Functions

[Maccer.]

Okay, so, lately there's been some resurgence of the works regarding the handling functions by Flobu and MrHankey. There's been debate about whether it should be client-side, server-side or both. Talidan, and lil_Toady have said this should be server-side, so flobu disabled client-side handling. I respectfully disagree, I think it should be both, since this is perfectly syncable client-side, and it could be server-side at the same time. Keep in mind, these handling functions are per-entity: meaning each vehicle element can have it's own handling. Each vehicle element is individual.

And plus, client-side handling allows quicker changes, and not all handling information needs to be synced. It's kind of like the client-side createVehicle ; only for showcasing. And handling is already hackable without any handling mods, so we can weed out the protectionism. And plus, the handling mod allows the restoration of the default handling.

setElementVelocity is client-side, is that justified? I think the same argument could be applied with the handling functions. And plus, I use setElementVelocity for a boost key... client-side. And it's synced alright.

Your thoughts, people?

Edited April 2, 2010 by Guest

[robhol]

The problem is here that if you set handling at one client, that car will still have the previous handling settings for everybody else. This causes sync trouble. Therefore, offering "true" client-side functions could cause fairly significant bugs if used improperly.

If there are to be client-side functions, they should at least be like a proxy for server-side functions - then again that's not really secure. Giving a client access to global server settings of any kind is just not very smart.

Nope, server's the way to go.

[Maccer.]

I say "let the server owner" beware.

[Dark Dragon]

Talidan, and lil_Toady have said this should be client-side, so flobu disabled client-side handling.

I'm a little bit confused now

In my opinion there is no need for client-side handling functions, having all that synced in all cases reduces confusion to new users or users who just don't know handling functions yet

[lil Toady]

Talidan, and lil_Toady have said this should be server-side, so flobu disabled client-side handling.

he made a typo there

[eAi]

It's about encouraging developers to do things properly. There shouldn't really be any client-side functions that can cause desync. It encourages developers to do things client-side that really should be, then wonder why things don't work correctly.

[karlis]

i understand problems that causes clientside 1, but i need say:

D'OH 1 more thing from 1,000,000 that need anoying triggers between server and client!

[Mr.Hankey]

fedor you can't really compare this with setElementVelocity since every car's velocity is synced to remote players anyway.

[eAi]

i understand problems that causes clientside 1, but i need say:

D'OH 1 more thing from 1,000,000 that need anoying triggers between server and client!

Annoying, yes, but a fact of life. Your server should have the vast majority of your code. Client side code should provide interface and cosmetic elements. If you're sending a lot of data from client to server, you're probably doing it wrong.

[Maccer.]

Talidan, and lil_Toady have said this should be server-side, so flobu disabled client-side handling.

he made a typo there

+1

Me on MSN while chatting with someone on this: "If it's server-side. Each vehicle will have it's own handling data. It will have longer download times. It's just easier to apply all of the data client-side."

[Xierra]

I say we take both.

The GUI and some functions which is Client-side, have more "smooth" experience when using it.

Handlings on Client-side will go always smoothly and will never be affected by anything else.

Server-side is nice but, doesn't look smooth, and also affect the ping. But it affects all people mostly.

Server-side handling is good for all vehicles, but delivers big data all the time, so I think that made lag.

The most important thing is that Client-side delivers smoother data, and doesn't frustrate you by the ping, including myself.

[darkdreamingdan]

To be honest, for consistency's sake, i think perhaps having it both clientside and serverside makes sense. All our functions at the moment display this behaviour, and i think there's no point in debating whether it's right or wrong to make it serverside-only when it's never been a debate in the past.

I understand the point that the client is getting too much control, but it seems annoyingly inconvenient that handling is where we draw the line, when perhaps that's one of the more safer (security-wise) functions.

[Dark Dragon]

the point that it would not be synced properly is indeed invalid. many client side functions cause desync. setGameSpeed for example.

in fact we can just add them for both server and client and if we encounter any problems we can just disable them later. but that's just my point of view

[Xierra]

Ok then, we'll see!