passing a name to a newly rezzed object

If a script rezzes a transport that is intended to only take a given recipient, is there an easy way to pass their name or key to? Right now my solution is to use chat to broadcast the information on a shared channel, but the timing of this feels quite clumsy, ie:

1. rez object
2. get rez event
3. delay arbitrarily or wait for a msg from object (safer, incase of sim lag)
4. llSay intended start parameter to object, who should now be listening and hear

If its an integer I can pass it in the rez, but this solution for a string seems quite cumbersome.

Does anybody know a faster and more reliable way of doing this?

You could also have the rezzed object request the information, that way you are sure it is rezzed and listening.

That's the most reliable way to do it. Otherwise, you have to hash their name and/or key to an integer to pass in the single integer param, and the transport object would have to hash it the same way and compare before it would function. Might take a little more script time, and there is always an astronomically small chance that your hash function would return the same value for two or more different people, but it is unlikely.

So, basically, you're doing it pretty much the way most everyone does it.

Yep, listening for a message from the rezzed object is best. (I'm assuming you're saying the object_rez event is unreliable, because naturally I'd recommend using that first.) You really don't want to rely on fixed timers because sims will cut back on script processing when things get hairy, increasing the time between events.

EDIT: It's unfortunate you can only pass an integer on rez. If you could pass a string, the rezzed object could convert that to a key or an integer or whatever.

Well I'm glad I'm not the only one!

Ah well, it works so I guess I'll leave it as is for now.

Thanks for the input thusfar.

I'm not saying object_rez is unreliable, just to me its too undeterministic. Does that mean the object has been created and scripts are beginning or have yet to begin running, does it mean its run through the state entry functions and has become idle.. ie does it mean it is actually going to be ready and listening, or is there a chance of a missed message.

Thats why listening for a callback seems the safest.. its just also the most painful (and sometimes slow) way to tell an object 'your name is frank' when it is a relatively trivial part of the overall functionality of the system, in my opinion.

Vote for https://jira.secondlife.com/browse/VWR-1488

I recently started using llRezObject on a project and I used a different approach that worked well for me: in the object_rez event I send the rezzed object a notecard with some info. Ofcourse, since you can't create notecards on the fly, it may not be usefull for everything. But in a lot of cases where you want to texture the rezzed object, drop a texture into it's content and use the changed event to detect and use it.

Lyn

I've been working on a hud for some things, and one of the features I've included is a teleporter to take you to specific areas (the compatable ship you have preselected on it). To avoid people sitting on it prematurely before it's received it's response to the request for a destination, I just have it 100% alpha, and then when it's ready it goes back to normal visibility and announces it's ready to energize.

Looks pretty seamless as regionsay is pretty fast most of the time, and even with the object id authentication to avoid crosstalk between your other compatable ships, it usually only takes it about 2 seconds max to appear. Most people think it's short enough that it just rez'd when it appears rather than having sat there and had a little conversation prior.