List of Pose balls

Hello,
My question is, is it possible to make a list of all my surrounding pose balls, print them in a dialog, and then when one is selected, make the av to sit on that pose ball?
I kind a did the first part with llSensor, I also did the av to move to that pose ball but I can't make it to sit on it.

Thank you for your help.

if you're defining a target for the user to move to, could you apply that same information to llSitTarget ...?

I'm probably not much use here, I'm still very much a scripting newbie

Ive tried llSitTarget but nothing happens, BTW I dont want literately to sit on the poseball, I actually want to "Use" the pose ball, I don;'t know if I explain myself correctly, i.e. if the pose ball is a dance ball, I want the av to start dancing
Thanks again.

That's the way all poseballs work. You have to sit on them. The animations trigger once you sit, and you play the requested animation instead of the sit animation (usually after it loads, so you actually may sit on it while it does).

There's no way to force an avatar to sit, period, though. You can make it easy by making the poseball default action "Sit" in the first tab of the editor dialog, but the user still MUST click the poseball to initiate the sit action.

Now, you CAN make a pose "object" which can start an animation on an avatar without them having to actually sit on it, but you will have to llRequestPermissions still, and they will have to allow it. The upside is that they don't have to sit on an object to do it; the downside is that you cannot control their position while their av plays the animation. You can push them to a spot, but you can't keep them there. For most single dance machines, this is how they work, and it is OK. However, for couples dances and beyond, you really need a poseball set to keep the avs together; that means you are back to "sitting" again.

Also note if you want to make a dance machine which animate more than one person, you have to do multiple scripts, as you can only have one set of permissions per avatar per script.

The thing is that I don't control the script on the pose balls, I'm just trying to have a script with all the possible pose balls around me, so I can select one to sit on. I don't mind if I have to ask permission to do it, but if you are telling me there is no way I can force my av to sit on the ball on "run-time", then I can't do what I want to do

There's no scripted way to force your AV to sit, period. Sit actions are *always* initiated by the user.

That doesn't mean you can't do what you want to do; just means you have to use a different method to achieve it. Either you sit on a poseball and select a specific pose, and the poseball moves/rotates itself and you then plays the animation, or you do the "dance machine" route where you click on it and it animates your AV after you click on it or it otherwise decides to start up.

You still have to always request permissions to animate an avatar via script, but they are given automatically when you sit on (or wear, I believe) an object.

Correct, there is no way to do precisely what you're asking.

Thank you all for your replies, do you have any idea if this funtionality will be added on the next versions?

Thank you again, you all been very helpful.

Very unlikely. They would have to add a couple new capabilities to LSL:

- requesting permission to 'seat your avatar' on another object
- activating a 'sit' on another object, specified by ID (presumably)

In general, I believe that allowing scripts to control other scripts (written by others) is frowned upon. It's quite possible that it opens security holes or avenues of attack for griefers. Sure, it would be nice to be able to write control gadgets for collections of objects you bought, like a chair that allows you to change poses from a menu, while all the sit poses were purchased independently. Someone else wanted to write a script that knew all the chat commands for various objects -- sort of a home central control system, I suspect. Again, the only way involved multiple steps for the user. If we go down this avenue, it doesn't stop with sitting, it would also include touching (yet, currently only avs can touch, and this avoids serious security issues), and chatting (no such security there, other than knowing the owner's ID), and who knows what else. Again, we'd need a pair of abilities for each of these things: one to ask permission of the av to act as proxy, and the other to perform the proxy action.

Feel free to suggest it as a feature request. Maybe enough other scripters are more interested in this idea.

Maybe you are right, but i wouldn't go as far as having to control other people’s code. I would be happy if i had the option to make my av sit on the thing and then let the natural flow of the engine control the av's actions.
Also another function that I think should be added to the scripts is the possibility of wearing/taking off clothing at runtime. It would be nice to be able to make a HUD to control the inventory of clothing.
I don't know, this is my first script and I'm already encountering lots of restrictions, hopefully with time I'll find "cheats" to do the things I want to, and I'm sure this language will keep growing with time.

Thank you again.