[CFodder]

In Insurgency Co-op mode it moves the bots to spectator, (have it set to move to spec initially then kick), is there a cvar to exclude it applying this to bots?

[Rothgar]

Originally Posted by interactive some errors [SM] Displaying call stack trace for plugin "afk_manager4.smx": [SM] [0] Line 1584, /home/forums/content/files/3/2/0/9/1/151560.attach::Timer_CheckPlayer() [SM] Native "GetEntityFlags" reported: Entity 13 (13) is invalid

Can you replicate this?

What Mod are you running?

Do you run any boys or anything such as Source TV even though they should be excluded.

[Rothgar]

Originally Posted by CFodder In Insurgency Co-op mode it moves the bots to spectator, (have it set to move to spec initially then kick), is there a cvar to exclude it applying this to bots?

It should not be checking bots are you using the version 4 branch?

Otherwise Insurgency might not be creating these as "FakePlayers" like other mods and which can be checked by Sourcemod which they either need to fix or I'll need information on how to detect them as I do not have Insurgency.

[DocReni]

Would it be possible to slay a player versus kick?

[Rothgar]

Originally Posted by DocReni Would it be possible to slay a player versus kick?

I assume you are asking for this to be an option for Spawn AFK'ers? As the full AFK I don't see much sense in it?

[DocReni]

Originally Posted by Rothgar I assume you are asking for this to be an option for Spawn AFK'ers? As the full AFK I don't see much sense in it?

Yes, please!

[Naydef]

Where "AFKM_OnAFKEvent" is defined in the *.inc file? I can't find it. I'm sure that I downloaded afk_manager.inc for v4!

[Rothgar]

Originally Posted by Naydef Where "AFKM_OnAFKEvent" is defined in the *.inc file? I can't find it. I'm sure that I downloaded afk_manager.inc for v4!

Yeah I was wanting to get some feedback from some plugin developers on how they wanted to see this implemented before I made an official publish but the code is currently there in part, may not have full functionality.

Forward is as follows:

/**
 * Called when an AFK event fires.
 *
 * @param name        This is the name of the AFK event.
 *
 * Event Names:
 *
 *        "afk_spawn_move"    - Event fired when a client should be moved to spectator for Spawn AFK.
 *        "afk_move"            - Event fired when a client should be moved to spectator for normal AFK.
 *        "afk_kick"            - Event fired when a client should be kicked.
 *
 * @param client    The client index of the client in the event.
 * @return            Plugin_Continue to complete event.

 */
forward Action AFKM_OnAFKEvent(const char[] name, int client);

If you want to do some testing and provide some feedback I guess I can look at officially releasing the include file. I think I still need to add some code to how to handle other return values though so might also need a new release of the plugin to finalize.

I just don't want to release prematurely and then have it change afterwards and break peoples code.

Previous reference which has information: https://forums.alliedmods.net/showpo...postcount=1693

[Naydef]

Maybe "client" as a first argument(not necessary). I already use this forward to prevent AFK actions for admins. It's already good forward. Also I expect Plugin_Handled to block AFK actions.

[Rothgar]

Originally Posted by Naydef Maybe "client" as a first argument(not necessary). I already use this forward to prevent AFK actions for admins. It's already good forward. Also I expect Plugin_Handled to block AFK actions.

What I guess I am looking for input of is whether there should be different options available for Plugin_Handled/Plugin_Changed/Plugin_Stop etc returns. then an idea of what people think the options should be?

I then also need to know how the AFK Manager should handle those returns, i.e. at the moment I believe Plugin_Stop will kill the timer and the timer will never get recreated until maybe a map change, is that the intended result in every circumstance or should I modify how the plugin handles the forward return scenarios instead like, Plugin_Stop is stop everything forever or until map change or other?, Plugin_Handled resets the timers for instance etc.

These I guess are the real areas that need consideration?