IsStatue = unknown0006, Offset 6 (Some models have a "Statue" animation that makes the NPC larger and striking a pose.)
DrakkinHeritage = unknown0011[3], Offset 14 (Body coloring, available colors at character creation dependent on player class)
DrakkinWhite = unknown0011[4], Offset 15 (Nonzero yields a white haired, white tattooed, white face-spotted Drakkin)
DrakkinWhite2 = unknown0011[5], Offset 16 (Acts like DrakkinWhite for all values 0-15 except 0, 2, 8, and 10)
NOTE: It's possible DrakkinWhite and DrakkinWhite2 somehow interact with DrakkinHeritage, and it's possible there's some 16-bit workings going on in the field causing the weirdness. Dunno. I can only test push 8-bit values at the moment.
DrakkinTattoo = unknown0079[0], Offset 369
Targetable11 = unknown0156[3], Offset 625 (If this field is set to 11, the NPC is untargetable. Weird, I know. Totally found it by accident!)
I'm still looking for beard color and Drakkin facial dots.
Also, I found the bug with my bald player character. This block of code in mob.cpp at line # 724 was messing things up. It assumes a zero value for the appearance fields is invalid, and sets such zero fields to 0xFF instead.
Code:
ns->spawn.haircolor = haircolor ? haircolor : 0xFF;
ns->spawn.beardcolor = beardcolor ? beardcolor : 0xFF;
ns->spawn.eyecolor1 = eyecolor1 ? eyecolor1 : 0xFF;
ns->spawn.eyecolor2 = eyecolor2 ? eyecolor2 : 0xFF;
ns->spawn.hairstyle = hairstyle ? hairstyle : 0xFF;
ns->spawn.face = luclinface;
ns->spawn.beard = beard ? beard : 0xFF;
The problem is, zero is perfectly valid. It's generally the first available appearance option for each field! Zero is the matted-hair for high elves, the dark brown hair color for races that can use it, the moustache face for humans, etc. Setting them to 255 actually SET them to an invalid value, making anyone with a zero value for the fields bald or incorrectly colored.
I simply commented out the 0xFF stuff, and things started working normally again.
Code:
ns->spawn.haircolor = haircolor; // ? haircolor : 0xFF;
ns->spawn.beardcolor = beardcolor; // ? beardcolor : 0xFF;
ns->spawn.eyecolor1 = eyecolor1; // ? eyecolor1 : 0xFF;
ns->spawn.eyecolor2 = eyecolor2; // ? eyecolor2 : 0xFF;
ns->spawn.hairstyle = hairstyle; // ? hairstyle : 0xFF;
ns->spawn.face = luclinface;
ns->spawn.beard = beard; // ? beard : 0xFF;
Maybe they were put in place to correct a render problem in a pre-SoF client. I tried messing around with it for a couple of minutes with the Titanium client, but I couldn't even get beards to load with Titanium to test with. Hair color and hair style seemed to work properly with the 0 values, so the 0xFF stuff might have been implemented for a pre-Titanium client, though that would mean this bug would have been around for a long time.
Hybrid Mode
