Forums » Suggestions
/disableturret command
Add commands like /disableturret1. /disableturret2, ..., /enableturret1, /enableturret2, ..., or /turret1toggle, ...
These would cause the disabled turrets to not fire when /+activateturrets is used, and make it so gunners riding in your ship would not be able to fire (or maybe even enter) that specific turret.
These would cause the disabled turrets to not fire when /+activateturrets is used, and make it so gunners riding in your ship would not be able to fire (or maybe even enter) that specific turret.
+1 very good suggestion
+1
suggested multiple times.. but still a good idea. it would allow us to disable turrets with ammo while firing energy too.
+1
+1
How about a parameter for the /+activateturrets and /-activateturrets command, follow it with a turret number. Also some 'type' parameter giving the ability to turn missiles on and off separately without having to give the turret numbers individually.
-1 very bad suggestion
-1 very bad suggestion
Can you please engage in the conversation with some kind of reasoning, since you're the first person who doesn't like the suggestion?
Can you please engage in the conversation with some kind of reasoning, since you're the first person who doesn't like the suggestion?
+1, could be very useful for instances when you have missile turrets that you don't want spamming, or if you are running cap cannon and rail, but you only want one of the two firing.
I meant to say *optional* parameter
Added tonight, 1.8.633.
That's great news, thanks.
As I understand it will be about toggling on and off speciffic turret. Can I ask if instead of /+activateturrets and /-activateturrets will be just one /toggleturrets for all of them? (Or it already exists and i'm not aware of it, please let me know).
As I understand it will be about toggling on and off speciffic turret. Can I ask if instead of /+activateturrets and /-activateturrets will be just one /toggleturrets for all of them? (Or it already exists and i'm not aware of it, please let me know).
The MOTD in the patch log explains how it works:
- Added /enableturret <turret> and /disableturret <turret> commands. The <turret> value can be the turret ID, turret name in double quotes such as "Lower Aft", "all", or "missiles". The commands can also accept a list of turrets separated by spaces. Disabling a turret prevents players and /+ActivateTurrets from using it.
So, I'd suggest just using "/disableturret all" and "/enableturret all" to achieve your goal?
- Added /enableturret <turret> and /disableturret <turret> commands. The <turret> value can be the turret ID, turret name in double quotes such as "Lower Aft", "all", or "missiles". The commands can also accept a list of turrets separated by spaces. Disabling a turret prevents players and /+ActivateTurrets from using it.
So, I'd suggest just using "/disableturret all" and "/enableturret all" to achieve your goal?
I should have explain my reasoning in my previous comment: I play on pad and recently I found out about commands that can be binded to keys in game setup. Commands /+activateturrets and /-activateturrets are occupying two functions of one of my buttons (in multickick hold to activate nad press to deactivate). I was thinking if we could have a function like "turbo" - one button press to toggle it on and off. From my perspective every command that utilize two functions in the same time is more useful.