LadyCailinBot

Comment by unusualbob Aha figured out its directly related to if the player is opped. Opped players get a stacktrace, regulars do not.

Comment by Dark_Arc I think it may be trying to load a session that doesn't exist... Though that's just from glancing over it...

Comment by unusualbob Nope, session file definitely exists. Just to make sure I deleted it and it recreated it and still is broken. It only gives me the error while...

Comment by zml2008 I cannot reproduce your error locally. However, I've added some code to the latest CommandBook dev build that will give me more information about what's wrong. Get...

Comment by unusualbob Sorry about the delay getting back to you, here's the new stack. ``` 09:18:32 [SEVERE] Could not pass event PlayerLoginEvent to CommandBook v540-e0b472a org.bukkit.event.EventException at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:427) at...

Comment by Darkhand81 Same issue here, problem with PlayerLoginEvent when an op logs in: http://pastebin.com/9haebUvw

Comment by zml2008 This should be fixed in the most recent dev build (#542+).

Comment by sk89q The issue is that CommandBook doesn't change join/quit names, isn't it?

Comment by sk89q Err nevermind that, didn't see the other part.

Comment by sk89q Fixed: https://github.com/sk89q/commandbook/commit/3e31f2233909fe013b10b13177e45ef0a99074bf