[Scripts] Requests for new Script Commands & Options

[muD]

This is sort of possible, but I'd imagine it would be very buggy. Or just break down in the middle of a process at the very least.

What makes you think that?

[Powerlord]

What makes you think that?

I forgot to specify that I meant that it's sort of possible in the game right now.

[muD]

I forgot to specify that I meant that it's sort of possible in the game right now.

explain what you're talking about if you want. im not going to ask.

[Powerlord]

explain what you're talking about if you want. im not going to ask.

They're possible, but there's only so much you can do with it. Really it's narrowed down to where I would just call them placement holders (being there's a difference). I would create a script that basically connects with others that require it to work, that way I don't have to clutter a bunch of lines of code in 1 script. Hopefully that made sense.

[MechaWho]

That's why directories would be useful, so you can have families of scripts that relate to the same process all under one 'folder' or directory. Some people have so many scripts that the list of scripts is too long and difficult to navigate. I don't understand why you think it would be buggy.

[muD]

They're possible, but there's only so much you can do with it. Really it's narrowed down to where I would just call them placement holders (being there's a difference). I would create a script that basically connects with others that require it to work, that way I don't have to clutter a bunch of lines of code in 1 script. Hopefully that made sense.

The idea of Script Directories is to allow the management of scripts to be similar to how components are saved. i.e. When you save a component/script you choose (or create) the directory to save it in, then save it in there.
It'd offer a much cleaner scripts menu.

Imagine if all your components were saved in one directory, including all the system components.. it'd be a loong list eh.. that's what my script menu looks like :p

[Powerlord]

The idea of Script Directories is to allow the management of scripts to be similar to how components are saved. i.e. When you save a component/script you choose (or create) the directory to save it in, then save it in there.
It'd offer a much cleaner scripts menu.

Imagine if all your components were saved in one directory, including all the system components.. it'd be a loong list eh.. that's what my script menu looks like :p

I see where you're going with this. Cool idea.

[kolinko9]

So lets just strt with im best at explaining through a headset. But here goes.

some things id like to see in future updates or scripting functions.

Having a Repeat or a looping function in stead of having 1000's of lines of Script saying the same thing with he copy and paste.

Making the Script blocks able to have a power source linked from 1 Script block to another without having Look range,button,switch, or linking thro a wifi. so have 1 Script block able to transfer power to the other script block.
(which would be great with having more than 1 script able to run at a time. such as the Wait timers take a backup string. instead maybe doing the same as the wait but linking script blocks together as 1 power on and 1 power off without it having to use a switch or the other ppower button and wat not.

Also allowing The Script screen to be some way minimized when rechecking cords. without saving exiting and rechecking cords.

Maybe thoughts of also adding a HOW TO for the script commands like in the Link here in the forums

anyway many more ideas but ill leave it at this for now

[Craig]

Making the Script blocks able to have a power source linked from 1 Script block to another without having Look range,button,switch, or linking thro a wifi. so have 1 Script block able to transfer power to the other script block.
(which would be great with having more than 1 script able to run at a time. such as the Wait timers take a backup string. instead maybe doing the same as the wait but linking script blocks together as 1 power on and 1 power off without it having to use a switch or the other ppower button and wat not.

You could do this now with the SetPower command?

[kolinko9]

example.

Script block 1
Power on: Set Power x,y,z
 ClearBlock x,y,z (coord of what you want deleted)

Power off: SetPower x,y,z (on) (cords of Script block 2)

Script block 2
Power on: CleaBlock x,y,z (cords)

Power Off: SetPower x,y,z ( script block 1)


This definitely doesn't work.

Also you can test this as simple as using usng SetPower x,y,z (cords of the block of the script block OR a POWERED LIGHT)

The light will not turn on. without having a switch,button,wifi, pressure plate, look range.

so DO you HAVE to have 1 of those link to it if so the SetPower doesn't quite do much.....

[Craig]

The SetPower command should not require switches or anything. It should just power the target block on or off just like a switch would do (without the switch).

[kolinko9]

althou it doesn't lol go try to use it with a powered light and let me kno how that works

[muD]

I would say this is a bad idea because it could leave your world in an unknown state. I suspect if you think you need this command, then there is probably a better way to design your scripts so that it is not needed. Unless you can give me an example where there is no better option.

would it be possible to add a [millisecond] parameter to the Notify command to sustain a notification?
would be great alongside that cancel script command, particularly for worlds giving info & hints

[Craig]

would it be possible to add a [millisecond] parameter to the Notify command to sustain a notification?

Problematic. The notifications are a queue. If you sustain a notification for some time, all notifications after it in the queue will also be held up.

[muD]

Problematic. The notifications are a queue. If you sustain a notification for some time, all notifications after it in the queue will also be held up.

Could that not be accounted for by subtracting the sustain time from the delay of any following notifications, or by using a separate script to run any other notifications that may need to be displayed while another is being sustained?