Step 1 – Get your code (free KINETICS Code Maker)
- Ask KINETICS for the free KINETICS Code Maker, wear it or rez it.
- Type in local chat the hover height of your shoes, in meters:
/73 0.130 - You get a code like
KH1:39c6fc2a171318. Every code is different, even for the same height: that is normal.
The height is the number you would type in the viewer's Set Hover Height window (between -1.000 and 1.000).
Step 2 – Put the code in your shoes (choose one)
Option A – Script (recommended)
Put the script Kinetics_creator_kit in the root prim of your shoes and paste your code:
string CODE = "KH1:39c6fc2a171318"; // from the KINETICS Code Maker
The script is open (modify): you can read everything it does. It holds no secret, it only repeats your code:
- when the shoes are worn, to the wearer's own attachments only (
llRegionSayTo); - when the wearer's HUD asks
HOVER?(e.g. at login). The listener only reacts to that exact message.
You can also paste these lines into your own shoe script:
integer HOVER_CH = -7358001;
string CODE = "KH1:39c6fc2a171318";
// in state_entry():
llListen(HOVER_CH, "", NULL_KEY, "HOVER?");
// in attach(key id):
if (id != NULL_KEY) llRegionSayTo(id, HOVER_CH, CODE);
// in listen():
if (channel == HOVER_CH && llGetAttached() && llGetOwnerKey(id) == llGetOwner())
llRegionSayTo(llGetOwner(), HOVER_CH, CODE);
Option B – No script
Add your code anywhere in the description of the root prim of your shoes, before you set them no-modify. The rest of the description can stay as it is.
Notes
- Why a code? The channel is public: a plain value could be read by any other HUD. Your code can only be read by the KINETICS Hover HUD, and it is useless to any other product.
- One version per body (different shapes per mesh body)? Make one code per version, with its own height.
- The old plain format
HOVER:0.130still works, but anyone can read it: use a code. - The wearer's own setting (SET in the HUD) always comes first; your value comes before the database.