Questions regarding // Commands

[shyrana]

Today I played with the commands listed using //help which left the following questions:

1. //thread <long running command>

thread: Runs a command in a thread Usage: //thread <long running command>

What is a long running command in this context? I dont understand which of the // commands might make sense to run in its own thread.

Or is command something else in this context, like a loop entirely written in C#? But how is this invoked then?

Can you explain this a little or provide an example for better understanding?

2. //pause [seconds]

pauses command script execution Usage: //pause [seconds]

What means command script in this context?

Is it something written in C# that executes // commands? Or is it something else? Can you provide or refere to a simple example?

I hope I will not come up with more silly questions

[shyrana]

After playing around I found several reason for the two commands.

1st example:
// thread //go person joyrana

This makes sense if shyrana stays far away from the bot shyrana because otherwise any further entry in the chat by shyrana will stop her from walking.

2nd example:
//go 5 n
// pause 15
//go 5 s
[17:11] Going North to 23,202,2255
[17:11] pausing for 15
[17:11] Finished walking 0 meters from destination
[17:11] shyrana: how are you
[17:11] joyrana: fine
[17:11] paused for 15
[17:11] Going South to 24,192,2255
[17:11] Finished walking 0 meters from destination

In the example I ordered the bot (shyrana) to walk 5 m to the north, wait 15 seconds and then walk back. The commands got somehow queued. during the pause shyrana talked to joyrana before she went back using the queued //go 5 s command.

In some situations a combination of the two commands (thread and pause) might be useful and even necessary.

Maybe there are better examples. Please provide them if you have some. I did this here due to the lack of documentation.

[Andrea]

I notice the new lsl commands that work, I can get the bot to send me time dilation to an im by clicking the box, but I see this thread and tried to script it to work with the bot and no go, really needing examples how to send sim data through an im at certain intervals and yes I'm lsl dumb mostly. why I need example lol

[jasonclandestino]

Feb 28, 2012 8:35:01 GMT -8 shyrana said:

After playing around I found several reason for the two commands.

1st example:
// thread //go person joyrana

This makes sense if shyrana stays far away from the bot shyrana because otherwise any further entry in the chat by shyrana will stop her from walking.

2nd example:
//go 5 n
// pause 15
//go 5 s
[17:11] Going North to 23,202,2255
[17:11] pausing for 15
[17:11] Finished walking 0 meters from destination
[17:11] shyrana: how are you
[17:11] joyrana: fine
[17:11] paused for 15
[17:11] Going South to 24,192,2255
[17:11] Finished walking 0 meters from destination

In the example I ordered the bot (shyrana) to walk 5 m to the north, wait 15 seconds and then walk back. The commands got somehow queued. during the pause shyrana talked to joyrana before she went back using the queued //go 5 s command.

In some situations a combination of the two commands (thread and pause) might be useful and even necessary.

Maybe there are better examples. Please provide them if you have some. I did this here due to the lack of documentation.

More documentation actually would be helpful.

I had considered implimenting osslD2Functions() within my grid so to assist with automated droid feature programming. Utilization of timer() events & other things would be simplified & character customization actually would be improved & made simple for the users.
("b0" << "d2" //har har It's appropriate to actually prepare Technological Intelligence against a population that might variably suggest things like they "bot their soul" & so forth.
Ethics for happy droids 101)

I as well think that a channel listen is terribly necessary. I found a column (!error!!erros!! //har har) about LSL Helper features & other about RLV, & that might be contextually transiently helpful, while still there's necessity for more programmed/programmable movement functionality.

More documentation actually would be helpful. I have started a column about new edition development, since Radegast development is not active.
Thanks to shyrana & developers of Radegast.

Thanks again.

[VenusAldrich]

Feb 14, 2017 20:04:44 GMT -8 jasonclandestino said:

More documentation actually would be helpful.

I had considered implimenting osslD2Functions() within my grid so to assist with automated droid feature programming. Utilization of timer() events & other things would be simplified & character customization actually would be improved & made simple for the users.
("b0" << "d2" //har har It's appropriate to actually prepare Technological Intelligence against a population that might variably suggest things like they "bot their soul" & so forth.
Ethics for happy droids 101)

I as well think that a channel listen is terribly necessary. I found a column (!error!!erros!! //har har) about LSL Helper features & other about RLV, & that might be contextually transiently helpful, while still there's necessity for more programmed/programmable movement functionality.

More documentation actually would be helpful. I have started a column about new edition development, since Radegast development is not active.
Thanks to shyrana & developers of Radegast.

Thanks again.
I am not new into LSL, but still can not figure out how I can make the bot in Radegast to actually use those commands. All I could find were the send_im, group_invite and give_inventory commands. I so want to make my bot make use of his own commands as well...but how? As I can not actually make him say the commands...