Display Moreyeah, we cleared the adds first
Just formulated an hypothesis yesterday but it is more related to computer science.
For short, server-side, we each have a log buffer of fixed size. Game wait to fill it before sending it for processing and renew it, or after 30 minutes of inactivity (sound familiar?)
When you join a cross server instance a log buffer is allocated for each. As you do "thing", fill the log buffer, the data is sent to your original server for processing, and the buffer is renewed.
When you leave the cross server instance, since there's no purpose of keeping the log buffer, it is simply destroyed without processing.
When you kill the last rabbit, the "event" may be stored in that buffer, waiting for processing. But leaving right after the last rabbit may destroy "rabbit killed" log entries.
And since 1 log buffer is linked to a char, all log buffer of a party are not really synchronized (about mobs killed entries) since each party member has its own activity as well.
This may explain why:
-despite of all care on client side, server count may not be the same.
-despite of presence of all party member, members may not have the same count.
Zinth you said you did the 15 rabbits at last, after cleaning mobs, then left. My hypothesis may explain it.
In fact, not a real GF bug, but on NC side (lack of data processing and cleansing at cross server instance leaving).
No, we did clear the entire instance so it had some time to update.