there is a possibility if you have re-saved the quest files using qedit (cmode) which aren't really fully supported in the public version, it itself has caused the corruptions, if this is the case i apologise for allowing qedit to even save cmode files in the first place.

Lol, it's fine, like you said it isn't even technically supported. Although since what's in the rar and what was up on Eden are the same, I doubt I saved the quest files and rebundled them in the far depths of my computer just to let it sit there. I'll port over the hex from GC when I get the chance, shouldn't take me too long. Damn I'm getting a nice laundry list of things I need to redo lol

Well i'm the closest thing to an expert on challenge mode format and quest structure and use in general that there is, i'm sure i could poke some more holes in stuff that's broken if i looked more carefully at it

Well something else that's broken is that I don't know the structure/what the client wants in terms of displaying cmode rank in lobby. I know what packet type to send, just not the size/what part of the challengeModeData array it wants for the rank

BoxDrop: array [0 .. 9, 0 .. 8] of byte; // $8C8 Box Drop Data

Did you mean to say [0 .. 9, 0 .. 6] here? Because your offsets after that are wrong if you meant 0..8 for the second part, and I know you described this section as 7 different kinds of drops for the 10 areas, not 9

yeah oopsie typo'd the multi array somehow in my commented version, it's actually fine in my program, wonder how that happened, considering i included correct hex offsets lolol. anyway section size for confirmation is 0x46 bytes (70, 10 x 7).

Alright lol, that's what I was thinking since the hex offsets went with what you said, kept wondering why the size of the PT struct wasn't quite 0x1000

meh happens, you did remember to use signed bytes for the parts I used shortint for right, important for the dam negative values they like to throw out, like for example the dam cmode daggers starting weapons class lol -1 -_-

Yep, that part was correct in the Teth source before I touched it, just the usage wasn't right

where you using teth's usuage of it in your program?