Todd Mitchell wrote: > excellent - I was not doing it wrong then. > > I am doing animations for the player race faces but only the frontal (151 - > 152) for now (unless I get inspired). While I am doing this I would like to > know once and for all what the proper convention is - the general form for > these appears to be is 111 is back side(moving north) 131 is right > side(moving east) 151 is front (standing, moving south) and 171 is left side > (moving west). This is what the documentation says too. > > 8 1 2 > \ | / > 7-0-3 > / | \ > 6 5 4 > > The default face is up for grabs (111, 171...) There seems to be a bit of > variation on these and I would like to fix that since it has burned me in > the past. > If there is a common agreement on this convention now would be a good time > for me to fix these to use it. the table you have above is correct in how it deals with direction (eg, direction 1 is up, direction 5 is down). It is also correct in that the code deals with directions the same way. EG, if an animation has 8 facings, they would be ordered in that same method. If an object has 4 facings, it would be 1, 3, 5, 7. If it had 2, it would most likely be 3 and 7 (vs 1 and 5). However, the numbering convention is to make things easy. I could do something like: anim facings 8 face1.111.png face2.111.png ... face8.111.png mina In other word, the code itself doesn't actually care what the face is called. You could have 8 random file names there, and it would work. It'd just be really confusing (and messy) to store in the directory. What this means, is if someone has the 3 and 7 facings reversed in the images, but they also reverse them in anim/mina, everything would look as expected. It'd just be confusing for people that come to work on the archs later on. > > Also - what about retiring old images? > I recently updated the 'classic' Ent and was wondering is there a process > where images are retired. Am I supposed to be doing this? Also what is the > deal with the alternate image set? Not a simple answer. if you replace an image with a newer one, that old image is basically retired in the sense it doesn't exist anymore. IT really shouldn't be renamed. The problem comes in in the opininion of people of 'is that new image better than the old one'. In some cases, the answer is a pretty basic yes (eg, for images that were scaled up from the 24x24 to 32x32, if you clean it up, it'd be a yes). However, when completely new images are made, people have differing opinions. The alternate set is now the 'classic' set (vs base). At one point, support for it wasn't very good, so there was basically a seperate tree for images in the classic set, and the collect script was modified to use it (looked in the altnernate directory, if it didn't find it there, then used the base version). A server would only support one set, which basically depended on what the server admin set up. So you should completely ignore the alternate_images directory/tree. _______________________________________________ crossfire-devel mailing list crossfire-devel at lists.real-time.com https://mailman.real-time.com/mailman/listinfo/crossfire-devel