[LINK] & [LINK:XX]
[LINK]text & [LINK:XX]text
These tags should only be used by experienced scripters. You can drop your own script into the EZAD and use the EZAD macro system to control the script through link messages. For example
[LINK]SCRIPT_ON
This macro will broadcast the message SCRIPT_ON to all the linked prims in the EZAD. If you used [LINK:4] instead the message would only be sent to link 4.
May 22nd, 2008 at 1:46 pm
This isn’t very clear.
I have a particle emitter script (call it ‘Smoke’) in a prim attachment I am wearing and another script (call it ‘Activator’) that targets and activates ‘Smoke’ on a listen channel (say ’100′). If I put Activator into my EZAD, can I make it work using a macro? And if so, how would that macro look?
May 22nd, 2008 at 2:20 pm
If all the activator script does is say “Smoke” on channel 100. I would just write a macro that says Smoke on channel 100. It would look like this:
[100]Smoke
The [LINK] macro is to replicate llMessageLinked() commands. So if you put a more complex script inside the EZAD you could use the HUDDLE interface to control it with link messages.
May 22nd, 2008 at 2:33 pm
The Activater script uses a string and a listening channel to set the particle emitter off.
Your [LINK] macro sounds like a better idea anyway. Could you provide a more comprehensive example of how llMessageLinked() commands would be replicated in an EZAD macro?
May 22nd, 2008 at 2:45 pm
Well it only works with the string part of a link message. You can have a macro like this:
[LINK]Message for other script
And it’s the equivalent of you using a llMessageLinked() command like this:
llMessageLinked( -1, 0, “Message for the other script”, NULL_KEY );
Does that help? I’m not sure what part needs clarification.
May 23rd, 2008 at 2:57 am
Thanks for that Keiki. I’m not an “experienced” scripter at all but I’m keen to learn and little examples like that make all the difference. I was confused by ‘SCRIPT_ON’ in the description above. It’s hard to see what that means.
May 23rd, 2008 at 8:01 am
I think the best thing to do is work with LSL and figure out how link messages work. Once you get a handle on them, this macro will make more sense.
December 25th, 2008 at 11:53 am
I am trying to control a device using the huddles. I have the problem where the device will only listen to the owner… and won’t listen to what the huddles says. I’m using the [DIALOG] command and that works nicely for simple commands… but I would also like to pass the current huddles target to my other device. I tried putting [target] into my dialog button…but it does not work. So… I thought… I’ll just write a script to set up the dialog and use [LINK] to pass the target to the script… but that don’t work either. Have you got a way to use [TARGET] in a dialog?
Thanks for you help…and thanks for Huddles… my favorite device!
December 26th, 2008 at 7:45 am
Bart, excellent question. I don’t think it works now to put [TARGET] into a dialog, but I will look into putting that in the next version. I’m hoping to start work on it very soon. One problem with using [TARGET] in a dialog is that a dialog button is limited to 24 characters, so it will often get chopped off.
April 19th, 2009 at 4:06 pm
I have to agree. This isnt clear at all, even with the above comments.
I finally figured it out after much trial and error. Im simply trying to
set up a button macro to send chat commands to a pair of wings to open and close them, but have the same problem as Bart, that the wings only listen to the owner, so I have to make a few changes. Im trying to send a link message to my script in the huddle which will then send a chat command to the wings on a random negative channel where the modified wings will listen to anything.
April 22nd, 2009 at 9:33 am
Keiko, you don’t need to add an extra script. If you want to broadcast to a negative channel use this:
[-199]message
If you want to have commands come from your avatar instead of the HUD, use the [DIALOG] tag.
http://imakehuddles.com/wordpress/about/dialog/