LE, I have stumbled upon a problem with our defined constants for stats. At this point it only seems to effect ones above 600 and not all are affected, some are the same in both clients. I did not go through every single one.
The problem is different stats show up based on what client you are using, will cite some examples below.

Using client version 4412 (RoK boxed set) this is what you see when examining the item...
And with client version 5721L you get this... both are using 611 and 616
client 4412 611 = Speed at all times and 616 = Inhibit Healing
client 5721 611 = In Combat Run Speed and 616 = Blurs Vision

But in our defines:
Correct, Zco?

The concern I have is that we have never identified each client version's item_stat definitions. Is this going to be a problem?

Bah, those bastards at SOE must have renumbered the effects from one version to another. This means that it will make my life more of a pain because I'm going to need to create a lookup table in the database similar to the opcodes table for these effect types. What I'll have to do is keep this lookup table up-to-date and make parser use the lookup table to make sure that it properly puts the right effects into the items table. The data in the item_stats table will be different than what it is now. There will be a list of effects from 1+ and World will use the lookup table to determine which id to send the client for each effect. Don't worry it sounds complicated, but it will really be seamless to the user, just another pain delivered by SOE :/

Ah bummer, so it isn't something magical we can do in our data to "just make it work" hehe. Sorry for the added work. Glad we caught it now tho...

But my question is, how will you find the item_stats values for all the different versions we have Items data for? Unless you've stashed each Everquest2.exe, which would be very forward-thinking of you

I have quite a few (9) different complete versions of EQ2 sitting on my hard drive, so although it might not be every one I doubt the values changed enough to prevent me from getting the right ones for all the data ranges we use right now.