there is only 1 file that makes em fly ppls n thats MountMotion.ini and as said earlier its all bout .c3,, eg:- the first flying mounts 810000 have a folder inside there Horse c3 folder,this is because you can set them to fly and walk, heres and example of there mountmotion ini
16999915=c3/Horse/816000/fly/915.c3
16999916=c3/Horse/816000/fly/916.c3
16999917=c3/Horse/816000/fly/917.c3
16999918=c3/Horse/816000/fly/918.c3
16999921=c3/Horse/816000/fly/921.c3
1016999100=c3/Horse/816000/fly/100.c3
1016999101=c3/Horse/816000/fly/101.c3
1016999110=c3/Horse/816000/fly/110.c3
1016999111=c3/Horse/816000/fly/111.c3
1016999120=c3/Horse/816000/fly/120.c3
1016999121=c3/Horse/816000/fly/121.c3
but with the other 5 or so flying mounts they are just normal mounts where instead of running they fly so u just add them like you would any other mount
i use the saphire+ruby dino client and database side for all my mounts just changing id's and lookfaces etc this way they have the correct hex to put em in the batch hatcher purchaser and in the goldcrown seller, if you search for my release the scorpion mounts it was done using my templates i use over and over
hope this gets u an idea of how they work
<NEO>[PM]