Quote:
L 06/15/2009 - 05:40:51: [afk_manager-compat.smx] [AFK Manager] RUNNING TIMER #1
L 06/15/2009 - 05:40:51: [afk_manager-compat.smx] [AFK Manager] RUNNING TIMER #2
L 06/15/2009 - 05:40:51: [afk_manager-compat.smx] [AFK Manager] CheckSamePosition - Checking Player Positions: Client: 1 Old Angle: -2336.031250 -2288.999511 68.031250 New Angle: -2336.031250 -2302.479980 95.703720
L 06/15/2009 - 05:40:51: [afk_manager-compat.smx] [AFK Manager] RUNNING TIMER #1
L 06/15/2009 - 05:40:51: [afk_manager-compat.smx] [AFK Manager] RUNNING TIMER #2
L 06/15/2009 - 05:40:51: [afk_manager-compat.smx] [AFK Manager] CheckSamePosition - Checking Player Positions: Client: 1 Old Angle: -2336.031250 -2302.479980 95.703720 New Angle: -2336.031250 -2302.479980 95.703720
|
Hmm somewhere along the lines it seems like it is running the timer twice... As you can see from the timestamps.
Just as a question, when you restart the server for example and for example it's on the first map and no one has connected/disconnected or been kicked etc. and you join can you see if the plugin works properly and maybe try and disconnect/reconnect a few times and then maybe try kicking yourself etc and see if it starts acting up.
I'll have to take a look into it, however either 2 timers are running or it's somehow looping the check twice I'd say. Will need to track it down.
I'd assume at this point maybe timers are not being closed properly at some point so there are some random timers running around possibly.
The weird part in your log file is this:
Quote:
L 06/15/2009 - 05:40:06: [afk_manager-compat.smx] [AFK Manager] AFK_Initialize - AFK Plugin Initializing!
L 06/15/2009 - 05:40:06: [afk_manager-compat.smx] [AFK Manager] AFK_Initialize - Finished Reseting Clients!
L 06/15/2009 - 05:40:06: [mapconfigs.smx] Executing map specific config: plr_pipeline.cfg
L 06/15/2009 - 05:40:40: [afk_manager-compat.smx] [AFK Manager] Event_PlayerTeam - Client: 1 joined team: 2
L 06/15/2009 - 05:40:40: [afk_manager-compat.smx] [AFK Manager] Event_PlayerTeam - Client: 1 joined a team and does not have a valid timer? Re-Initializing client
L 06/15/2009 - 05:40:40: [afk_manager-compat.smx] [AFK Manager] InitializePlayer - Initializing client: 1
L 06/15/2009 - 05:40:40: [afk_manager-compat.smx] [AFK Manager] InitializePlayer - Creating AFK timer for client: 1
L 06/15/2009 - 05:40:40: [afk_manager-compat.smx] [AFK Manager] ResetPlayer - Reseting arrays for index: 1
L 06/15/2009 - 05:40:40: [afk_manager-compat.smx] [AFK Manager] Event_PlayerSpawn - Client spawned: 1
L 06/15/2009 - 05:40:40: [afk_manager-compat.smx] [AFK Manager] ResetPlayer - Reseting arrays for index: 1
L 06/15/2009 - 05:40:40: [afk_manager-compat.smx] [AFK Manager] InitializePlayer - Initializing client: 1
L 06/15/2009 - 05:40:40: [afk_manager-compat.smx] [AFK Manager] InitializePlayer - Creating AFK timer for client: 1
L 06/15/2009 - 05:40:40: [afk_manager-compat.smx] [AFK Manager] ResetPlayer - Reseting arrays for index: 1
L 06/15/2009 - 05:40:40: [afk_manager-compat.smx] [AFK Manager] Event_PlayerSpawn - Client spawned: 1
L 06/15/2009 - 05:40:40: [afk_manager-compat.smx] [AFK Manager] ResetPlayer - Reseting arrays for index: 1
L 06/15/2009 - 05:40:41: [afk_manager-compat.smx] [AFK Manager] Event_PlayerSpawn - Client spawned: 1
L 06/15/2009 - 05:40:41: [afk_manager-compat.smx] [AFK Manager] ResetPlayer - Reseting arrays for index: 1
L 06/15/2009 - 05:40:41: [afk_manager-compat.smx] [AFK Manager] Event_RoundStart - Round Started
|
notice it creates a timer twice it seems and hasn't closed a timer. I don't know if you remembered what happened at that point whether someone had disconnected and then reconnected? It doesn't look like it changed maps...
Have you made sure this is not a bug in the latest dev release of 1.2.1 which it seems like you are using? have you tried the stable version?
The only other thing I can think of is that you joined a team and it spawned a timer and then the PostAdminCheck maybe kicked in afterwards... (massive delay for some reason?) and then it ran the Initialize again. OnClientPostAdminCheck. I currently in the Initialize function don't check for any active timers. I guess I could.