Quote Originally Posted by cn187 View Post
As far as I can tell, zone IDs only go up to 1000 (unless they decided to do something really weird). I think it's more likely to be a struct change.

A quick look through the code only shows a few paths that will generate that debug message. I don't think it's zonechange or player profile related, as I suspect things would be broken, rather than just showing a debug message.

I suspect either OP_GuildMemberList, or maybe zonePointStruct.

To test for OP_GuildMemberList, check and see if the zone info in the Guild window is correct, and/or check and see if you get the same debug messages with a character that isn't in a guild. (alternately you could probably replace the opcode for OP_GuiildMemberList with ffff and see if the message goes away).

I could easily see it being this one, because I don't think much attention has been paid to the guild-related code for quite a while.

If it's zonePointStruct, I'd expect that hovering over a zone-exit clickable (like a PoK book) should cause the debug message to print, and a bad zone name in the popup text.

I could also see it being this, as some other issues have been reported that may be related.
I believe I narrowed it to a problem with the GuildMemberUpdate struct.
Code:
structGuildMemberUpdate
{
/*000*/  uint32_t  guildId;                   // guild id
/*004*/  uint8_t  unknown004[4];              // 4 bytes added 11/16/16
/*008*/  char  name[64];                     // member name
/*072*/  uint16_t  zoneId;                   // zone id 
/*074*/  uint16_t  zoneInstance;             // zone instance
/*076*/  uint32_t  lastOn;                   // time the player was last on.
/*080*/  uint8_t  unknown080[8];             // 4 bytes added 11/28/12, +4 added 11/16/16
/*088*/ 
};
zoneId no longer seems to be in the packet as best I can tell. Haven't checked on zoneInstance but will give that a go next time I am in a zone that shows the instance number to compare.