[V. 2] Server_SlowMotionDeath - Slowers client timescale upon death.

[Klocko²]

Oh yeah, everybody would slow down if the host died.

Pretty sure there was is a console command which slows down the host's timescale but not others, something like ClientCmdTimescale(NumberHere);


EDIT: Yes, I'm pretty sure it is ClientCmdTimescale(NumberHere);
And I think I remember joining a server and showing the host the command, it did not slow us down..
This means that this add-on can be client-side!

[Ad Bot]

[MARBLE MAN]

Pretty sure there was a console command which slows down the host's timescale but not others, something like ClientCmdTimescale(NumberHere);

it'll make everyone lag and glitch up...

[Klocko²]

it'll make everyone lag and glitch up...

They fix up after the timescale is set back to 1

[Wrapperup]

Pretty sure there was is a console command which slows down the host's timescale but not others, something like ClientCmdTimescale(NumberHere);

Reason this isn't going to work on a non-dedicated server, is if the host dies, the script cannot tap in to the original server's timescale. for example: i start a non-dedi server, i set the server's timescale to 2. then the host dies die, which sets his timescale to 0.2 for a few seconds, but when the script tries to get the server's timescale (which should be 2), since the client is the host, it
grabs his current timescale (0.2) leaving him in slow motion. This is why this cannot work properly in a non-dedicated server.

[BlockoBlocko]

Cool, downloaded.

[bambooXD]

Mmmm watcha saaaaay...

oh yea lol the hey sista...

[MARBLE MAN]

Reason this isn't going to work on a non-dedicated server, is if the host dies, the script cannot tap in to the original server's timescale. for example: i start a non-dedi server, i set the server's timescale to 2. then the host dies die, which sets his timescale to 0.2 for a few seconds, but when the script tries to get the server's timescale (which should be 2), since the client is the host, it
grabs his current timescale (0.2) leaving him in slow motion. This is why this cannot work properly in a non-dedicated server.

find a way to get past this?
edit:
if possible

[Port]

Reason this isn't going to work on a non-dedicated server, is if the host dies, the script cannot tap in to the original server's timescale. for example: i start a non-dedi server, i set the server's timescale to 2. then the host dies die, which sets his timescale to 0.2 for a few seconds, but when the script tries to get the server's timescale (which should be 2), since the client is the host, it
grabs his current timescale (0.2) leaving him in slow motion. This is why this cannot work properly in a non-dedicated server.

Store the previous timescale then?

[Chrono]

Or just make it not affect the host.

[lordician]

Or just make it not affect the host.

This would be the best solution i think.

On topic of the add-on itself, this is actually not a bad idea.
I like it.

[Wrapperup]

UPDATE!

This add-on now works in non-dedicated servers! The host's timescale will not be changed upon death if ran on a non-dedi server. If ran on a dedicated server, the host's timescale will be affected on death.

[Wrapperup]

bump

[gr8dayseth]

Is there any way to have both work?