As some may be aware, i'm making lots of new playable races for our server.
One of them, the beholder has a real issue. If i equip an armour which the model itself does not support, the client crashes. So far no other model has this issue (eg: umber hulk, drider). I'm guessing its something to do with nodes and armour parts.
When i create a beholder in the toolset and give it the armour it looks ok, but when in game its invisible.
So, it looks pretty clear that its the act of trying to apply armour parts (or apply an armour type to this model that it doesn't support) it causes the client to crash. Saying that, reloading the crashed creature also crashes the client.
I took a look at appearances.2da, tried to set thing like modeltype and stuff to different values, seeing if any of those would allow me to work around the problem. Nothing i changed helped.
Suggestions?
1) Anyone with modelling skills can take a look at the beholder model, see if something is missing (nodes?) and fix it?
2) Anyone know of an alternate beholder model? (on the old vault i seem to recall some rather simple red looking beholder but low quality).
3) Is an appearance.2da fix possible?
4) Any way to stop creatures equipping armour? I thought to remove any armour proficiencies, but thats still going to leave cloth armour open to equipping. Setting an on-equip function to auto remove the armour doesn't work quick enough (tried it) to stop the crash.
5) Final option... just roll with it, and warn players if they equip armour they will crash their client and have to wait for me to edit their BIC to remove it. However, i can provide some armour that at least will be compatible with the model (for example, one set of settings actually allows you to close the Beholder's main eye which is rather cool).
Retour en haut
