[LH][BUG?] New unit designs MUST have heads?

In adding skeletons as a designable unit, I've run into a weird issue. No matter what I've tried, if I design a skeleton unit as a NEW unit (through that menu option), it seems to render different races heads over the skeleton head. The result is a horrifying and buggy looking monstrosity. I've tried equipping different heads, equipping no heads, I've mirrored the setup of the monster skeletons... I've even removed all types from it so it can't equip anything, but a head still shows up.

This only shows up in the NEW unit design menu. If I assign the same xml, but enable the CanBeDesigned flag, it shows up on the list of trainable units without the extra face.

Seems related to the missing head issue that was cropping up for slave units awhile back. Any ideas?

Locked Post

Advanced Search

Watch this post

Do not email me updates for this post Email me updates for this post

Successfully updated karma reason!

parrottmath

Join Date 03/2008

+206

When you design a new unit the program is utilizing the generic mold they have for that race. In other, words, you skeleton body will end up with equipment type heads and such. The only way around this is to create a seperate body model type. Currently I think it is using a wraith modeltype body. You need to create a new one and add the appropriate art definitions for that particular model type. Then you would have to force this unit to arise as a generic model type other (like the henchmen, slaves, juggernauts, and golems). Then you will be able to design "NEW" skeleton units, otherwise you are stuck with redesigning skeletal units.

Successfully updated karma reason!

It looks like it goes with whatever randomized set of art assets that I assign through the UnitModelType. If I leave that declaration out, it just goes with the standard Sion stuff instead of a 'blank sheet'.

I suspected that what you said would be the case, but I was hoping it wasn't... It was fairly easy to add to the current tabs the same way they added slave units. It would be cool, but it's way more trouble than it's worth to weed through the requisite web of xml to assign everything that you want to be usable...

It'll be easier, and just as functional to just have it in the unit list and make it dependent on an ability.

Successfully updated karma reason!