Pilot Archive
Thread: Idea for droid commands
Page 1 of 1
Ducimus
Thu Aug 04, 2005 8:17 pm
#1
This is blantatnly inspired by the EWS energy management system,
But heres the idea, and i dont think it would require that many changes.
1.) reduce in scale, the Droid Controller delay. The delay is just too long. Want to be able to use droid commands on the fly more often.
2.) Remove the overload decay, its a stupid idea that is poorely implemented, no one gets decay anyway.
3.) Overloads such as weapon and engines inverse operators in the form of Tuninng. The idea here is to make it so that Running EO3 disallows the use of WO3. Infact running one should encourge you to run the tuning program in the other to save energy. For example if i run EO4, then i should be encouraged to run WT 3 or 4 to counter the energy drain on the reactor.
The heckler in all of this is RO, CO, and CTSS as they have no inverse operation. Maybe make RO and CO inverse operators? Dunno, just a wild stab in the dark on that one.
Just an idea is all, im bored at work and my tools are frozen and not working so i cant do much except think of stupid things like this.
But heres the idea, and i dont think it would require that many changes.
1.) reduce in scale, the Droid Controller delay. The delay is just too long. Want to be able to use droid commands on the fly more often.
2.) Remove the overload decay, its a stupid idea that is poorely implemented, no one gets decay anyway.
3.) Overloads such as weapon and engines inverse operators in the form of Tuninng. The idea here is to make it so that Running EO3 disallows the use of WO3. Infact running one should encourge you to run the tuning program in the other to save energy. For example if i run EO4, then i should be encouraged to run WT 3 or 4 to counter the energy drain on the reactor.
The heckler in all of this is RO, CO, and CTSS as they have no inverse operation. Maybe make RO and CO inverse operators? Dunno, just a wild stab in the dark on that one.
Just an idea is all, im bored at work and my tools are frozen and not working so i cant do much except think of stupid things like this.
Bawarr
Thu Aug 04, 2005 8:21 pm
#2
hmm they really do need to change them so their not *that* good, maybe have them run out after a certain ammount of time but reduce the decay.
Another idea is to make it insta-decay 1 point for a lv1 overload 2 points for lv2 etc
So instead of causing 100/110 it would be 106/106 after using a lv4 overload. There would still be no downside to CtSS however.
Page 1 of 1