Hum...Bugs

[Ragarnok]

Hi, i own a Gmod server, and i have several bugs, that i am the only one to have, first the Smoke grenade, when i launch one i have
entities\ttt_basegrenade_proj\shared.lua:44: attempt to compare nil with number

Second thing, if i idle for 10 seconds i die(YES i have set the ttt_time_idle to 400...)

[phoenixf129]

Hmm, have you got CSS mounted correctly? It sounds like that might be a issue, also, try updating your TTT to latest, as the gmod update could have broken sometihng in the previous releases.

[Ragarnok]

I will disable some addons to see if it's a conflict problem, but that would be.... impossible ?

[Bad King Urgrain]

Is that error in yellow or blue text? Do you also get it with the incendiary grenade?

Make sure you're setting ttt_idle_limit. But even so, the default time is 180 seconds, so I'm not sure you're being killed by the idle check.

[Ragarnok]

Only the smoke (error in yellow), and i've already said, i've put ttt_idle_limit to 400

[Bad King Urgrain]

No, you said you put ttt_idle_time at 400, which does not exist.

Anyway, the error occurs in code common to all grenades, so it's odd that it would be specific to the smoke grenade.  Either way, I've added some protection that will prevent it from occurring in future TTT versions.

Thinking about it, both issues seem like they could be network-related, with values on your client getting desynced or otherwise faulty. I don't have a solution for that, but you might see it affecting other areas as well.

[Ragarnok]

WHen i die, it says Automated Message: Blablablabla.
And the errors are the same for every grenade, the difference is that with the smoke grenade, i don't see the smoke.

[Bad King Urgrain]

Ah, the grenade thing makes a little more sense then. I'll tweak the networking for grenades and the idle check so it deals with slow connections (and perhaps packet loss) better. The idle check thing appears to be a gmod bug where it ignores the default I've set if it doesn't receive the idle limit from the server for whatever reason. Rather than the 300 seconds it should default to, it could take action immediately after ten seconds. I've added a workaround for that which should fix it.

[Ragarnok]

Weird, my connection is good... And my ping is too.