[321]

Hello
I found an error in your Plugin Version can you fix it please:
L 06/29/2010 - 18:18:27: SourceMod error session started
L 06/29/2010 - 18:18:27: Info (map "ze_LOTR_Mines_of_Moria_v4_5") (file "errors_20100629.log")
L 06/29/2010 - 18:18:27: [SM] Native "GetEntData" reported: Entity 30 (30) is invalid
L 06/29/2010 - 18:18:27: [SM] Displaying call stack trace for plugin "zombiereloaded.smx":
L 06/29/2010 - 18:18:27: [SM] [0] Line 935, zr/weapons/weapons.inc::WeaponsIsClientInBuyZone()
L 06/29/2010 - 18:18:27: [SM] [1] Line 256, zr/weapons/restrict.inc::RestrictBuyCommand()
L 06/29/2010 - 18:24:48: Error log file session closed.

[Greyscale]

Why are there weird errors like this..

(Not directed toward you 321, just some notes)

This error is coming from an invalid client index that's being provided by a console command callback.

Is this a sourcemod bug? Maybe he entered the command and disconnected within the same frame? Weird.


321, don't worry about this it is a freak error that shouldn't cause any problems.


EDIT:

Discussed with some other people and we came up with the idea that someone most likely connected to your server with 3rd party software installed on their client and sent the command while connecting. Why someone would send "buy" "rebuy" or "autobuy" while connecting I don't know. They may have been trying to crash your server.

[Annihilator]

Well, I find a lot of this kind of error reports in my logs, but it never crashed my server or made an impact on the game play, so I just ignore it

[rhelgeby]

At the moment I can't see any other reason why it happens. Must be like you suggested, players with plugins/scripts that send the buy command before the connection process is done.

Maybe we should to a IsClientInGame check in restrict.inc:RestrictBuyCommand? Just in case.

[Greyscale]

Yeah we can do that. Just doesn't feel right checking if the client is valid when the SourceMod is the one giving the client.

[rhelgeby]

I suppose the client itself is valid, but the client's entity isn't ready yet.

Added bug 195.