Bukkit

http://pastebin.com/1gt1cEeS

(Sorry it is upside down because my hoster´s console handles it like that)

I found this error while looking into my console. If you need further information on it like debug mode,... please tell me what exactly and i will look for it asap. But atm it is to late here in germany to find out.
I just thought you would like to know about it (and i might have forgot it tomorrow ;) )

What version of CraftBukkit are you running this on? I see obfuscated class references which shouldn't happen in CraftBukkit. Also, the "Unknown source" shouldn't occur either since PlayerActivity is compiled with debug information and that implies there is some custom class loader that is discarding that information at load.

Without more details, I'm left guessing at the root cause.

Assuming somehow a player has quit that does not generate a PlayerQuitEvent or is no longer able to be identified by the name it had at last activity (not display name, that's irrelevant), I've added a check for such a situation in an alpha build of version 4.2.1a0: https://github.com/EdGruberman/PlayerActivity/blob/master/dist/PlayerActivity.jar?raw=true

Give that a try and please let me know if a log entry occurs like the following:

Idle status requested to be published for player no longer present: <Player>

See if you can associate any related activity to the player it occurs for if so.

I am getting the message: Idle status requested to be published for player no longer present: [RedPower]

I am using MCPC+ which Ports Bukkit to the Forge API. Build #244 with CB 1.4.7 R1.0

[RedPower] is the "fakeplayer" of a mod that i as i found out just now haven´t given the permission playeractivity.track.* in PEX. <- This was the right permission to deny checking for this "player"?

Sry but does the permission node to ignore a player have to be: - playeractivity.track

or negate it to - -playeractivity.track (using PEX)

This is the syntax to negate the permission in a PEX configuration file:

- -playeractivity.track

See if that helps you with this issue.

There seems to be a lot of weird things going on for what it's worth. I'll see if I can setup a MCPC+ test with RedPower myself to reproduce and identify root cause. But my hunch is RedPower is doing some shady things that the MCPC+ port might be complicating.

I can't guarantee everything will work as expected as my focus in CraftBukkit support, but again I'll see if I can find some time to at least poke it all. I'm curious at a minimum.

Thank you i will test the permission node asap. This issue is not really important because your plugin works fine. It seems to be one of the consequences you have to live with when using Bukkit and Forge together :D It is really nice from you to keep working on the issue. Take your time.