YeOlde--- Yeah I tried Notepad++ but for some reason I could get it to do it the way I wanted, but I did not spend a lot of time with it ( was in a frustration mood at the time and was like ok this one does not work, let try this one etc.. hehe) So I sure it works. Either just glad I have something to transfer all the data.
I want to add that this works very well. I am adding some columns to
appearance.2da that are much needed. I'm thinking that some scripts can
be completely rewritten. There are a number of scripts that use test the
creature's appearance index in a switch statement. Would be much better
to store the information in an ACTUAL table rather than a virtual one.
AND then you only need to store the information in one place.
Things
like FLYING, AQUATIC, INCORPOREAL, SOFTBODIED and for creatures that
have alternate appearances such as birds that can fly or walk... you can
provide a "pointer" to the other appearance type making it very easy to
switch appearances between the two states.
Anyway... adding table data to a 2DA is gold. For some reason I did not realize this was possible.
I have done this for awhile, if you look at my HR DM tool I use a apptail 2da to match up creatures and tails to run through a custom scale function. Make it a lot easier. I also did one connecting humanoid monster to riding humanoids that do not have full animation in my riding hak (not sure if I have updated that to the vault yet.) I will be also use this system for my custom flying system coming HR base) well if your 2da are custom and you use unque names for you colums you should ok and it easy to point them back to the standard apperance.2da for you row check. Other systems could be custom tail/back models, helmet etc..
