Client Respawn v1.6 - Page 2

Ricky · 03-12-2006 , 06:06

My experiences with both functions are the same. They both cause that glitch 1 out of 10 if you're getting spawnraped but the ghosts disappear after the round ends. If you keep rounds short it won't be too much of a problem. If you're on a fy/aim map or tdm, you've got ghosts everywhere, players complaining, big mess.

T(+)rget · 03-12-2006 , 09:57

Check this out: Basic Respawn

I gave an example how to do it correctly until AMXX fixes the user_spawn native.

twistedeuphoria · 03-12-2006 , 19:20

That spawning method works, however, it does not avoid the ghost bug if you wait too long to spawn them.

Geesu · 03-12-2006 , 20:34

Word of advice, check if it is a KA map and don't give weapons...

T(+)rget · 03-12-2006 , 22:23

Quote:

Originally Posted by twistedeuphoria

That spawning method works, however, it does not avoid the ghost bug if you wait too long to spawn them.

oO you on about that proper method? If so what was the delay time you put in?

twistedeuphoria · 03-13-2006 , 02:47

15 seconds was the time I tried this time, however, I've tried shorter lengths as well with other setups.

T(+)rget · 03-13-2006 , 07:29

Ok try this:
set a task of 0.5 to set the RESPAWNABLE flag, then your new task for spawning the client with DispatchSpawn and the iuser1 = 0.

Ricky · 03-13-2006 , 07:36

This method might prevent the spawn-glitch but would it prevent the lag-glitch too?

T(+)rget · 03-13-2006 , 07:38

I've been using this method for ages, seen no lag or glitch. The glitch though I have a fast task, but I believe its tied to DEAD_RESPAWNABLE something in the engine more than likely checks if this is set and if not, will fully remove the body so to speak.

Ricky · 03-13-2006 , 07:42

So you finally decided to share that with us here