It would be better if the engine outputs the file position in the wmb if the wmb has an incorrect format and not the character itself. Mentioning the type of struct it is trying to parse would be even better.
long num_textures; // number of textures
long offset[num_textures]; // list of texture offsets from the start of the list, in bytes
A texture begins at the offset given by the array of texture offsets.
I'm a bit confused right now.
So is it the offset from the beginning of the file or from the long num_textures?
