kick user plugin issues

[spugh]

I've written a plugin extension to timeout users to not hold up other users in the room. After 3 time outs the user is kicked from the room. When the user is kicked, the plugin's userExit and userKicked method were not called so I added the handling of the exiting of the user at the same time as sending.

Is this how this is supposed to be handled? Or what should I expect?

The plugin needs to know who enters the room and who exits.

[h1280]

I just did a test.

If a user is kicked by "kickUserFromRoom" neither userExit method nor userkicked method will get called.

If a user is kicked by "kickUserFromServer" userExit method will get called but not userkicked method.

It looks like a bug to me!

I have extensions that are having trouble cleaning up users. I thought that userExit will always get called when users leave the room. Now I know the cause.

Teresa could you confirm this?

[tcarr]

I have not used "kickUserFromServer" myself. I do use "kickUserFromRoom". Checking my code and logs, I see that my userKicked method isn't getting triggered either. My method that does the kicking was already set up to clean up details before the player got kicked, so I'm not sure whether it calls userExit or not. I do remember having to add a check to my userExit method to return if the player had already been marked as gone from the game, because otherwise in some circumstances an infinite loop was being triggered; that might not have anything to do with the kicking however.

Thanks for the bug report!

[spugh]

I found a similar report (4/2/2008 from Sankar, I think it's #5418).

I also did some more testing and have the same problem with the Language Filter kick/evict. Neither userExit nor userKicked get called.

Did find that if the client does a leave room request when receiving the evicted from room event, that the userExit gets called in the plugin extension. But when the client receives the leave room event, handling of the event may cause errors, because the zone or room may no longer exist by the time it's received.

Any other suggestions on what would work better would be appreciated.

[peter royal]

This is a bug, and has been fixed in the latest development version. Please contact ES4 Support to get a copy of the patch.

We're looking to get 4.0.5 out that will incorporate all the recent fixes as well.