[DDR Khat]

Originally Posted by Damizean No, the problem may be the client takeovers the bot client slot while connecting, resulting in the real client being kicked because the plugin think it's a bot. Simple to fix: // ------------------------------------------------------------------------ // KickFakeClient() // ------------------------------------------------------------------------ public Action:KickFakeClient(Handle:hTimer, any:Client) {KickClient(Client, "Free slot.");return Plugin_Handled;} change it into // ------------------------------------------------------------------------ // KickFakeClient() // ------------------------------------------------------------------------ public Action:KickFakeClient(Handle:hTimer, any:Client) { if (IsFakeClient(Client)) KickClient(Client, "Free slot."); return Plugin_Handled; }

Read the code where it is used. What we're kicking is sanitized at the point we're calling it

[Number Six]

Originally Posted by AtomicStryker Try looking at the source code? It's mostly self-explaining

Thank you very very much !!!

[Naow]

Originally Posted by DDR Khat Read the code where it is used. What we're kicking is sanitized at the point we're calling it

Do you know if you can fix this bug please? ;)

[DDR Khat]

Originally Posted by Naow Do you know if you can fix this bug please? ;)

Your post makes NO sense.
Your either;
1) Asking for it to boot players constantly for some satanic reason
2) Asking me to fix some bug you've never explained.

[Damizean]

Originally Posted by DDR Khat Read the code where it is used. What we're kicking is sanitized at the point we're calling it

I know where is it called However, I'm talking about the possibility of the existence of a mechanism to override fake client slots with real clients while on spawn time, in order for a newly connected survivor to takeover an existing bot. There's the posssibility this mechanism is fired between the creation and the timer tick event, therefore kicking the real client thinking it's a bot. Just add the extra check (costs nothing and is only tested when necessary) and find out if the bug ever happens again.

[YourEnemyPL]

@DDR Khat. I noticed that "Event_TankSpawn" is triggered twice (versus).

I added some code to chat to everyone about tank hp (ex. "Tank new HP 10000 (default 4000)" ).


This is what we get (7 survivors, hpmulti 0.25):
"
Tank new HP 10500 (default 6000)
Tank new HP 18375 (default 10500)
"

sometimes(when we are fast and deal damage to tank):
"
Tank new HP 10500 (default 6000)
Tank new HP 18069 (default 10325)
"
or
"
Tank new HP 10500 (default 6000)
Tank new HP 17500 (default 10000)
"

Tank have 306,25% (175%*175%) of original hp instead 175% (7surv, hpmulti 0.25)

[cyberloner]

L 06/21/2009 - 03:16:43: [SM] [0] Line 538, /home/groups/alliedmodders/forums/files/4/7/7/4/3/43940.attach::KickFakeClient()
L 06/21/2009 - 03:16:43: [SM] Native "KickClient" reported: Client 7 is not connected
L 06/21/2009 - 03:16:43: [SM] Displaying call stack trace for plugin "l4d_superversus.smx":
L 06/21/2009 - 03:16:43: [SM] [0] Line 538, /home/groups/alliedmodders/forums/files/4/7/7/4/3/43940.attach::KickFakeClient()
L 06/21/2009 - 03:16:43: [SM] Native "KickClient" reported: Client 8 is not connected
L 06/21/2009 - 03:16:43: [SM] Displaying call stack trace for plugin "l4d_superversus.smx":
L 06/21/2009 - 03:16:43: [SM] [0] Line 538, /home/groups/alliedmodders/forums/files/4/7/7/4/3/43940.attach::KickFakeClient()

This happen as well

[mattressfish]

Originally Posted by YourEnemyPL @mattressfish First. I don't get why people quote like that.

Because that's what the QUOTE button is for. It also allows one to link back to every post in the conversation, a feature that doesn't work when you simply type @

Second. Hacked ?? No, you are wrong. We can use source code. And we can do with it what we want (of course we must give the original author credit). I just made some small changes and share with you. If you don't want it, don't download it. Very simple isn't it?

I'm just saying that it seems like everyone posting their own version of the OPs code could make this thread a nightmare to support and/or even understand. Apparently I must be wrong, so don't worry about it.

[cyberloner]

Death toll mission 1st map... the shotgun will be missing. Is that small bugs? or games bugs

[ProBoomer]

No, the problem may be the client takeovers the bot client slot while connecting, resulting in the real client being kicked because the plugin think it's a bot.

Oh.... is the plugin kicked with "Free Slot..." error Because think all players are bots, however this not happens always, only random, but now we know how the fix up

Great