Definitely trust lerxst! He's set me straight more times than I can remember
I agree that the client logs probably won't yield anything in this case, especially since there's a 28-second difference between the messages.
[If if turns out to be your server...]
Going on the assumption of an autoloot->cursor pickup->delete action, this is the only segment of code I see that will cause this exact sequence:
https://github.com/EQEmu/Server/blob...tory.cpp#L1153
And since this is a fail return scenario, the resync code kicks in for the final message.
Hopefully something in this con-check will jog your memory or, at least, point us in the right direction
EDIT: Looking at this closer, there appears to be only 2 cases where the server will 'World Kick' you..that link is one of them.
This doesn't include the perl or lua interpreters, which would bring into account script files...
Threaded Mode
