Your vote requested for 2.0 feature: Clientside puffs enabled by default

[Uwe L. Bendoverson]

Either way, the puff and the shrapnel are now in wildly different places, causing things to be worse off than if you simply had the puff spawn by the server's command.

I could see the shrapnel spawning late (if it's set up in such a way that only the server can control spawning of those), but I don't see how they'd be in wildly different places unless the puff moves around on it's own.

As yet another addon that I did not mention (I'm sorry... argh), only bullet puffs with +NONETID are predicted. Anything else will not be, no matter what the setting (prediction on or off).

So that basically solved Ijon's concern.

[Cruduxy]

While at it you guys should enable autorun and mouselook by default!

[Kara Kurt]

While at it you guys should enable autorun

Hell yeah, most newbies have no clue why everyone else moves faster with their "hey how you move this fast xD", at least with that there's a better chance they score a flag that they missed by an inch because too fucking god damn slow!

[Uwe L. Bendoverson]

Or have it so if someone doesn't run for nearly an entire map, it just says in bold letters on the screen: "THERE'S A SHIFT/CAPSLOCK KEY FOR A REASON!".

Just kidding... Or am I?

[Ijon Tichy]

Either way, the puff and the shrapnel are now in wildly different places, causing things to be worse off than if you simply had the puff spawn by the server's command.

I could see the shrapnel spawning late (if it's set up in such a way that only the server can control spawning of those), but I don't see how they'd be in wildly different places unless the puff moves around on it's own.

Hitscan check hits player on client and spawns on the player for the client, but misses the player on the server and so keeps going, presumably to hit a wall and spawn there for everybody else, including the server.

And yeah the NONETID thing should help, assuming BulletPuff subclasses don't have that flag (edit: by default). If they do, then things will still desync for the reasons discussed above.

edit2:

(if it's set up in such a way that only the server can control spawning of those)

The client never spawns server-side things of its own accord. If the client tried to spawn things, it'd cause horrible desyncs constantly, not just from simple latency issues, but from the fact that the client doesn't keep track of the server's RNG, is not guaranteed to know TIDs, is guaranteed to not know health values for anything not a player (and even then only sometimes), ACS variables, and most probably some other shit that escaped my mind.

[Uwe L. Bendoverson]

The client never spawns server-side things of its own accord. If the client tried to spawn things, it'd cause horrible desyncs constantly, not just from simple latency issues, but from the fact that the client doesn't keep track of the server's RNG, is not guaranteed to know TIDs, is guaranteed to not know health values for anything not a player (and even then only sometimes), ACS variables, and most probably some other shit that escaped my mind.

I'm aware. I just meant that if puffs are still spawned serverside, but predicted clientside, the clientside predicted puffs would not spawn the shrapnel, the shrapnel will spawn later when the server tells the client to spawn the shrapnel by the server's instance of the puffs.

I hope that makes sense.

[Watermelon]

Note that I would like to sync the RNG's between the client and server if using compat_oldrandom. That way predicted shots should still look okay minus touchy desyncs.

[Torr Samaho]

Note that I would like to sync the RNG's between the client and server

This would be the only correct solution, but unfortunately is quite difficult to achieve with our C/S setup.

if using compat_oldrandom

I don't think that this restriction would make the undertaking that much easier, but considerably less useful.