[siosios]

its not that hard to get the newest version and remove the networking and some other lines of code refering to it and have your own no sockets version guys.

sio

[CS:S*]

Originally Posted by myzombie CS:S*, perhaps you can send the nosocket version that I've sent you to KHALIK ;)

done

[vertexshader]

After KAC was added to plugins and updated to 1.2.0.3, socket version, me and one guy were disconnected (not in same time and at diff map) with this msg

Disconnect: Your client has failed to reply to a query in time. Please reconnect or restart your game.

OS: Win 7 x64

Protocol version 7
Exe version 1.0.0.34 (cstrike)
Exe build: 12:47:15 Aug 26 2009 (3945)

Metamod:Source version 1.8.0-dev
Build ID: 670:daed02c52b13-dev
Loaded As: Valve Server Plugin
Compiled on: Oct 29 2009
Plugin interface version: 11:7
SourceHook version: 4:4

SourceMod Version: 1.3.0-dev
SourcePawn Engine: SourcePawn 1.1, jit-x86 (build 1.3.0-dev)
SourcePawn API: v1 = 4, v2 = 3
Compiled on: Nov 23 2009 05:42:21
Build ID: 2865:f3551d6b1300-dev

[Kigen]

Originally Posted by vertexshader After KAC was added to plugins and updated to 1.2.0.3, socket version, me and one guy were disconnected (not in same time and at diff map) with this msg OS: Win 7 x64 Protocol version 7 Exe version 1.0.0.34 (cstrike) Exe build: 12:47:15 Aug 26 2009 (3945) Metamod:Source version 1.8.0-dev Build ID: 670:daed02c52b13-dev Loaded As: Valve Server Plugin Compiled on: Oct 29 2009 Plugin interface version: 11:7 SourceHook version: 4:4 SourceMod Version: 1.3.0-dev SourcePawn Engine: SourcePawn 1.1, jit-x86 (build 1.3.0-dev) SourcePawn API: v1 = 4, v2 = 3 Compiled on: Nov 23 2009 05:42:21 Build ID: 2865:f3551d6b1300-dev

That is a perfectly normal message. It just means his client failed to reply to a query in 30 seconds from when it was issued. All that happens is that he is kicked from the server and all he has to do is rejoin.

[vertexshader]

But why me? I was playing on the same machine at which is server started - still testing and this is rly strange to be kicked. What's the reason to fail? Btw I noticed that after the update typing "quit" to shutdown the server doesn't give anymore clear shutdown. Got Win 7 default "...has stopped working" screen and this means cannot use restart after crash bat file. The errors are not logged See the screenshot:

[IMG]http://img687.**************/img687/4871/srcdshutdownerror.th.png[/IMG]

[rautamiekka]

Originally Posted by vertexshader But why me? I was playing on the same machine at which is server started - still testing and this is rly strange to be kicked. What's the reason to fail? Btw I noticed that after the update typing "quit" to shutdown the server doesn't give anymore clear shutdown. Got Win 7 default "...has stopped working" screen and this means cannot use restart after crash bat file. The errors are not logged :| See the screenshot:

The issue stays even after reboot ? You could also try this:

1) Shutdown the computer
2) Deattach the power cable
3) Wait for 10 minutes
4) Without the power cable attached, try to start the computer
5) Wait for 5 seconds
6) Again without the power cable attached, try to start the computer
7) Wait for 15 seconds
8) Attach the power cable, start the computer and your Server

This method is called Electricity Reset after which there is absolutely no power left in the computer, thus getting rid of anything left behind in memory and busses.

[Kigen]

Originally Posted by vertexshader But why me? I was playing on the same machine at which is server started - still testing and this is rly strange to be kicked. What's the reason to fail? Btw I noticed that after the update typing "quit" to shutdown the server doesn't give anymore clear shutdown. Got Win 7 default "...has stopped working" screen and this means cannot use restart after crash bat file. The errors are not logged See the screenshot: [IMG]http://img687.**************/img687/4871/srcdshutdownerror.th.png[/IMG]

This is because KAC hooked the command "quit". This should be fixed in future releases once SourceMod 1.3 becomes the stable version for SourceMod. If you are using a 1.3-dev version then the next update to 1.2.0 should correct this issue as I've ported the command hook code to use a new native in SourceMod 1.3 which will allow me to hook all commands without having to Reg*Cmd() them all.

https://bugs.alliedmods.net/show_bug.cgi?id=4048

[Dirton]

Hi, Kigen!
I'm not at all disappointed that you ignored my last question, but perhaps you could look into this one.
I've noticed that since I started to use KAC 1.2 beta with Anti-WH ON the Death beam plugin stopped working, it loads without error, but KAC seams to block that beam. As the result many players complain on this.
Could you please add some check to bypass the death beam to the masses and still use Anti-WH feature?

[vertexshader]

Originally Posted by rautamiekka The issue stays even after reboot ? You could also try this: 1) Shutdown the computer 2) Deattach the power cable 3) Wait for 10 minutes 4) Without the power cable attached, try to start the computer 5) Wait for 5 seconds 6) Again without the power cable attached, try to start the computer 7) Wait for 15 seconds Attach the power cable, start the computer and your Server This method is called Electricity Reset after which there is absolutely no power left in the computer, thus getting rid of anything left behind in memory and busses.

LoL u get me, I'm "not" good at wires Nope, I forcefuly cleaned the memory at 5GB cached limit (Win 7 has some weird issue btw, like Vista - Superfetch is disabled but still eating memory). Btw I ran new instance from backup archive and it was ok but after adding KAC and restrict weps plugin and other 2-3 approved this occured again.

Kigen, why "quit" command must be hooked?

[Kigen]

Originally Posted by Dirton Hi, Kigen! I'm not at all disappointed that you ignored my last question, but perhaps you could look into this one. I've noticed that since I started to use KAC 1.2 beta with Anti-WH ON the Death beam plugin stopped working, it loads without error, but KAC seams to block that beam. As the result many players complain on this. Could you please add some check to bypass the death beam to the masses and still use Anti-WH feature?

I'm pretty sure the reason why that Death Beam plugin is not working is because it is extremely outdated. Because its outdated its conflicting with other stuff. It would be pretty simple to update it.