- This script installs 1 hotkey.
- Pressing the hotkey pauses all turrets on your ship for 5 minutes or until you change sectors.
Whatever comes first. - Pressing the hotkey again unlocks your turrets.
- Starting a new turret script on one turret unlocks that particular turret.
- If you have one of your ships targeted and this ship does have turrets, the pause/continue is applied to that ship instead of yours.
- Some of you may now say that this already exists here.
The difference is that this script here works with all current and future turret scripts without any changes.
It also doesn't disable the turrets indefinitely. I sometimes forgot turning them back on and didn't even notice since I had switched to another ship.
[SCR] Turret On/Off Hotkey
Moderators: Scripting / Modding Moderators, Moderators for English X Forum
[SCR] Turret On/Off Hotkey
(Das entsprechende deutsche Topic ist hier.)
![[ external image ]](http://www.egosoft.com/img/button_download.gif){kind=link}
My complete script download page. . . . . . I AM THE LAW!
There is no sense crying over every mistake. You just keep on trying till you run out of cake.
There is no sense crying over every mistake. You just keep on trying till you run out of cake.
-
Lancefighter
- Posts: 3144
- Joined: Sun, 19. Dec 04, 02:41
Strange...
You have this line:
$Target -> interrupt task $Nr.of.turrets with script "plugin.gz.turret.onoff.turret" and prio 5 : arg1= null arg2= null arg3= null arg4= null
does the 'get number of turrets' command also get them in such a way that you can command them like you are?
And my general overview of the script is that it will put a task in front of the current turret script, and wait until the timer is up, then get rid of said task. Is this correct?
I also note you get the number of turrets multiple times... is that needed?
You have this line:
$Target -> interrupt task $Nr.of.turrets with script "plugin.gz.turret.onoff.turret" and prio 5 : arg1= null arg2= null arg3= null arg4= null
does the 'get number of turrets' command also get them in such a way that you can command them like you are?
And my general overview of the script is that it will put a task in front of the current turret script, and wait until the timer is up, then get rid of said task. Is this correct?
I also note you get the number of turrets multiple times... is that needed?