The kite's Start Position is where the Kite "string" is anchored and the kite will face this spot and it's position will always be relative to this point,
If a Kite Post is used, the position of the post is the Start Position, and a particle "string" will be connected to it.
If you don't use a Kite Post, your position, (when the script is reset), be used as the Start Position.
When the kite script resets (which happens anytime you change it's contents), it will look for a rezzed Kite post. If one is found (within 96 meters), a particle string will connect the two automatically and the post position will be used as the Start Position.
If you have more than one kite, and want them connected to different posts, an additional step is required.
You can also use this method if you want to connect the kite to something other than the kite post provided. (But there will not be a particle string generated).
The default behavior of the kite is to move about as the Second Life wind changes direction. It is not uncommon for the wind to slowly rotate and make a full circle. But you can force kite to stay in one area by configuring a default wind direction.
You can define a distance limit for the kite to move from its Start Position. Regardless of this distance, the kite will stay within it's current region; and if you want, it will stay within a specific smaller area.
While the Start Position lets the kit know what direction it should face, the Kite Post needs to identify the kites it is to connect with a string. When the post is rezzed it will search for kites and automatically connect to them.
But if you want a kite post for each of several kites, you will need to add notecards to each kite post with the names of the kite.
Three kite posts are included in the package.
Configuration information is provided in the name of a few notecards in the Kite's Contents.
The Kite Script will reset when any of these notecards are changed.
TIP: If you want more than one kite connected to the same post, use different heights for each kite. Sometimes the SL Wind will change with altitude and setting different heights will prevent them from bunching up.
For higher values the kite will stay in one place longer after repositioning. Shorter times will make the kite more responsive to changes in the SL Wind. But the SL Wind is highly variable. It may change direction quickly, or stay at the same direction for a long time; or it can even rotate 360 degrees over 10 minutes or so.
This lets you fly the kite always over one side or a corner of your parcel. Or to use the kite as an advertisement that stays over your store.
For example: "WIND 90 10" will fly the kite to the east of the Starting Position and will shift between 80 and 100 degrees.
NOTE: Tail streamers are flexible objects that respond to the actual SL wind and so may not stream in the same direction as a kite using the WIND notecard. If you fly the kite fairly high, this may not be noticeable. You can also edit the kite object and remove the streamers.
Normally you will let the kite automatically find and use the Kite Post for this. But if you are using an artificial WIND notecard, you may want the kite facing somewhere other than a post.
If this position is in the same region as your kite, just go to that spot and use your region coordinates with the LOOKAT notecard.
But if the LOOKAT spot is not in the same region as the kite, there is an additional step:
Kites start as a thin single prim oriented with the Z axis pointed toward the ground, X axis to the right, and Y axis up.
The name of the Tail Texture must start with "TAIL "
"TAIL RGB blended".
Streamers or tails can be any shape. I've chosen elongated cylinders so the texture appears on all wides.
Configured them for Flexible Path. You can experiment with the settings to get the desired amount of flexibility and responsiveness to the wind.
To add more, just link them to the kit object. Remember to touch the kite prim last when adding child prims.
You can make more complicated kites by linking additional parts as child prims to the main kite object. You will probably want some degree of flexible path configured for them, so they appear loosely connected -- but not as much flexibility as for tails.
Mesh objects usually will not usually meet the requirement that the Z axis points toward the post location on the ground.
If this is the case, you can't just add the kite script to it, you will need to create a small cube that you can use as the root prim of the kite and link to mesh object to it. Add the kite script and notecard to the cube and then shrink the cube so that you can hide it inside the mesh object.
Here is an example of mesh eagle (that I've made partially transparent), where I've hidden the root kite object inside with the Z axis pointed down.