[muukis]

Originally Posted by AtomicStryker That isn't a glitch, its actually how the plugin works.

That's the thing I was talking about on my last post on this thread.

What I was worried about was that what happens to the health if you set the health to 500 and then the played grabs a ledge before you restore it back to the previous state. What will be the health the game sets for the player after the rescue from the ledge.

[AtomicStryker]

I dont set the health to 500, its a Display glitch or something from setting someone un-incapped.

And i still dont know the answer to your question, someone would have to test that out.

[Visual77]

Nope, server aint cracked. If you got a server that's pretty much full with janks on night and ppl from europe on day, you would get these errors too

Btw, I diden't have these errors when I compiled with sourcemod 1.2.4
Yesterday night I started compiling every .sp file with 1.4.0
I still think the latest 1.4.0 has something to do with this.

Atomicstryker, I am using this: SetConVarInt(FindConVar("survivor_incap_healt h"), 550);
thus 550 for 1 sec.

I'm actually getting killtimer errors on your pills plugin too, + one one tank plugin.
Maybe a bug with sourcemod 1.4.0?

[AtomicStryker]

Dont know. I use 1.4 to compile against and i have not a single Timer Error in my logs.

[Visual77]

Those errors are harmeless anyway. But could you take a look at this one. There seems to be a hp bug on my server. They end up alive with 550 hp after the charge. This happens very rarely, thats why I only got 3 errors of this in my logs.

L 01/02/2010 - 02:23:30: Info (map "c4m4_milltown_b") (file "errors_20100102.log")
L 01/02/2010 - 02:23:30: [SM] Native "SetEntProp" reported: Entity 17 (17) is invalid
L 01/02/2010 - 02:23:30: [SM] Displaying call stack trace for plugin "l4d2_bulldozercertificate.smx":
L 01/02/2010 - 02:23:30: [SM] [0] Line 130, l4d2_bulldozercertificate.sp::SetPlayerIncapState()
L 01/02/2010 - 02:23:30: [SM] [1] Line 111, l4d2_bulldozercertificate.sp::Reincap()
L 01/02/2010 - 02:29:06: Error log file session closed.

[AtomicStryker]

I do not support versions of my plugin you altered yourself? LOL

[Visual77]

I have not altered your plugin in anyway. Downloaded the sp file, compiled with sourcemod-1.4.0-hg2887. If you're gonna countiune to be like this, acusing me for this and that, do you think I will countinue report bugs of this plugin? Becuase I don't see anyone else reporting sourcemod errors in this thread. Maybe you want it like that, maybe not.

[AtomicStryker]

Originally Posted by Visual77 Atomicstryker, I am using this: SetConVarInt(FindConVar("survivor_incap_healt h"), 550); thus 550 for 1 sec.

Thats what i meant.


Now, from this errorlog you posted the Plugin failed at setting i can say the client-id of the target Survivor CHANGED during the one second between functions.

That can only mean a Charger hit a BOT, a Player joined or swapped Teams and took over the BOT, and when the Plugin tried to set the health back the BOT wasn't there anymore.

Its not fixable. Theres no "Take over Bot" event i could use to hook the changing clientids.

[Visual77]

That still dosen't mean I "altered" your plugin, and I could notice what you ment just by the tone of your voice. That's a completly different plugin I use to make L4D2 more friendly with 8v8.

Back to the plugin, the closehandle/killtimer errors are gone, don't know why they come and go. When a new snapshot is out for 1.4, I will defently update.

About the health not getting restored, it's ok then I guess. Happens like once every blue moon anyway. I think it only happens when the charger
touches 2 or more incapciated survivors while charging one who is alive.
Edit, I decided to remove it for now. Just seems so instable if a charger runs over >2 or more incapciated survivors.

[Skorpion1976]

Unfortunately I needed to remove it too, as my error log consists of nothing but these lines:

L 01/08/2010 - 05:48:55: [SM] Native "KillTimer" reported: Invalid timer handle 68cf18c5 (error 1)
L 01/08/2010 - 05:48:55: [SM] Displaying call stack trace for plugin "l4d2_bulldozercertificate.smx":
L 01/08/2010 - 05:48:55: [SM] [0] Line 53, l4d2_bulldozercertificate.sp::Event_ChargeEnd ()
L 01/08/2010 - 05:48:58: [SM] Native "KillTimer" reported: Invalid timer handle 68cf18c5 (error 1)
L 01/08/2010 - 05:48:58: [SM] Displaying call stack trace for plugin "l4d2_bulldozercertificate.smx":
L 01/08/2010 - 05:48:58: [SM] [0] Line 53, l4d2_bulldozercertificate.sp::Event_ChargeEnd ()
L 01/08/2010 - 05:49:41: [SM] Native "KillTimer" reported: Invalid timer handle 68cf18c5 (error 1)
L 01/08/2010 - 05:49:41: [SM] Displaying call stack trace for plugin "l4d2_bulldozercertificate.smx":
L 01/08/2010 - 05:49:41: [SM] [0] Line 37, l4d2_bulldozercertificate.sp::Event_Charge()
L 01/08/2010 - 05:49:41: [SM] Native "KillTimer" reported: Invalid timer handle 68cf18c5 (error 1)
L 01/08/2010 - 05:49:41: [SM] Displaying call stack trace for plugin "l4d2_bulldozercertificate.smx":
L 01/08/2010 - 05:49:41: [SM] [0] Line 53, l4d2_bulldozercertificate.sp::Event_ChargeEnd ()
L 01/08/2010 - 05:49:44: [SM] Native "KillTimer" reported: Invalid timer handle 68cf18c5 (error 1)
L 01/08/2010 - 05:49:44: [SM] Displaying call stack trace for plugin "l4d2_bulldozercertificate.smx":