how do i force an avatar to sit on a prim with rlv?

ok... ive got the hang of most of the scripting for rlv but i need to know how to force a sit from the script using rlv as all attempts i have made have failed. any scripters out there who know rlv and the answer?

ty anyways though hun.

Use the TOKON Hud system, and also get a relay.

There are other systems out there as well from remote controlling.

apparently not very well......

The UUID being, of course, that of the object on which you want the av to sit, not that of the av (a point I know confuses some people -- it did me, anyway, the first time I tried to make something using @sit: ).

I think, though I can't swear to it, that the object needs a sit target.

No.

No UUID is needed.

With a RLV controller and wearing a relay, any person can sit you on anything or do all kind of other things like remove all your clothes and attachments, teleport you without a TP request, etc.

A Tokon HUD can do it with an extra Relay so i assume it has one built in.

If you are not using the Tokon Master/slave HUD, you need to have a RLV Relay.

Yes, the UUID is absolutely required, the viewer won't know what to sit on without it. The UUID is being sent to the relay object in that case, which in turn passes it on to the viewer with that @sit command.

offtopic:
hey bianna, did you recently have an ad for automatic hamster in your sig? trying to figure out where I saw it.

Especially to innulla

This is the code that worked.

default
{
state_entry ( )
{
llSitTarget ( < 0.0, 0.0, 0.1 >, ZERO_ROTATION );
}

touch_start ( integer total_number )
{
llOwnerSay ( "@sit:" + ( string ) llGetKey ( ) + "=force" );
}
}

And too Void Singer...

I read it very well ty. Nowhere in that ai does it state sittarget is needed. and the ai is confusing on the matter of which uuid to use. Do not assume that someone didnt read something very well if it is not written very well.

Maybe from the scripting side.

But what i was talking about was OBVIOUSLY not about the scripting aspect since i mentioned items that can sit you without you giving the object any sort of UUID yourself.

If i had noticed this was in the scripting section I would have never replied.

This is very OBVIOUSLY the scripting forum, and even if we were to pretend that this wasn't the scripting forum and instead the how to use completed objects somebody else already made forum, those objects still need to use the UUID, even if you don't see it.

Brianna - it "appears" as if you don't need the UUID of the object - but you do. The way tokon and OpenCollar and Amethyst collars have you sit on anything (that is scripted, of course) is it "scans" a certain radius (usually 20 meters) and grabs the names and UUID's of the objects it finds.

:HRUG:: PEBKAC or more loosely CF:TB (Communications Failure: Text Based)

Lol! Everyone heere is so uptight. I apreciate any help i can get even if the answers dont apply. We all learn from what we experience and even if the answers are not what we need at the moment the info supplied couold be used at a later time. So in effect, no worries everyone and thanks for everything. ~

The way the hud works, I take it, is it fires llSensor(), returns a list of object names it's detected, then when you chose one, finds the appropriate UUID (which it's also detected as part of the sensor) and says something like

 llSay(relaychannel, cmdname + "," + (string)av_id + "," + "@sit:" + (string)object_id + "=force");

with cmdname being an arbitrary name you're using in the handshake between the hud and the victim's relay, av_id being the victim's uuid and object_id being the uuid of whatever you're chosen to sit your victim on.

The victim's relay then does the rest.

Void: no.