Some good info in there, most known but a few things helps. The biggest problem isn't where things are.. we know for the most part but between versions bytes will slip into strange places and throw offsets off a bit which is what causes fields to be off... and it's annoying as heck btw.
Also I'm going to commit some more item stuff even tho I promised myself I'd take a break. Item movement and bags should work after this.
Some items also cause the client to 'crash', it's an odd crash the client just fails to load and eventually just exits to the desktop with no error. Nothing even in log. Something about the item packet is malformed and causes this.
Code:
[Sat Feb 14 23:43:06 2009]00318:MSG_TIME_STAMP received. (Items inc).
[Sat Feb 14 23:43:06 2009]00319:Received an item via EQI_STARTING_ITEM at loc 2
[Sat Feb 14 23:43:06 2009]00320:Received an item via EQI_STARTING_ITEM at loc 7
[Sat Feb 14 23:43:06 2009]00321:Received an item via EQI_STARTING_ITEM at loc 8
[Sat Feb 14 23:43:06 2009]00322:Received an item via EQI_STARTING_ITEM at loc 9
[Sat Feb 14 23:43:06 2009]00323:Received an item via EQI_STARTING_ITEM at loc 10
[Sat Feb 14 23:43:06 2009]00324:Received an item via EQI_STARTING_ITEM at loc 13
[Sat Feb 14 23:43:06 2009]00325:Received an item via EQI_STARTING_ITEM at loc 14
[Sat Feb 14 23:43:06 2009]00326:Received an item via EQI_STARTING_ITEM at loc 17
[Sat Feb 14 23:43:06 2009]00327:Received an item via EQI_STARTING_ITEM at loc 18
[Sat Feb 14 23:43:06 2009]00328:Received an item via EQI_STARTING_ITEM at loc 19
[Sat Feb 14 23:43:06 2009]00329:Received an item via EQI_STARTING_ITEM at loc 23
[Sat Feb 14 23:43:06 2009]00330:Received an item via EQI_STARTING_ITEM at loc 24
[Sat Feb 14 23:43:06 2009]00331:Received an item via EQI_STARTING_ITEM at loc 25
[Sat Feb 14 23:43:06 2009]00332:Received an item via EQI_STARTING_ITEM at loc 281
That's it, end of the log. There's a couple more items after 281 but I've confirmed it's what's at 281 that's causing the crash in this case it's: 5022. I noticed having some fields set wrong (usually the unknowns) causes this to happen when making the packet. So im guessing there's an unknown like this somewhere in the shuffled fields.
Threaded Mode
