Pilot Archive
Thread: Has anyone experienced this Droid interface problem?
As it states in the droid program breakdown, the speed is based on the level of the program and the speed of your DI. However, most droid programs are bugged and have the timer of a Level 4 program. A good comparison is the difference between Cap Overcharge 3 and engine Overload 3. My understanding is that all the "3" programs should be loading just as fast as CO3.
This is all old bug stuff, nothing has really changed since the last batch of droid programs got added. (timer for CO3 is correct because it was one of those later additions).
RE the level of your FC or droid- no neither have an effect on speed. DEs have been begging for the ability to experiment and improve astromechs and FCs since beta, so we can sell based on quality and provide a valuable service, but alas, nothing.
Alyxian wrote:
Overloads should take no time to load at all, it is a silly timewaster, I load into space, run my macro and go get coffee...there is no point I can see to having a timer on them.
It was assumed that we would be running different programs in different situations, hence the normalize programs. And some do need the timers. Cap to shield for example, could you imagine how tough it would be to take down a ship with a 50+ regen cap, cap OL4 and instant cap to shield?
Sylia wrote:
Alyxian wrote:
Overloads should take no time to load at all, it is a silly timewaster, I load into space, run my macro and go get coffee...there is no point I can see to having a timer on them.
It was assumed that we would be running different programs in different situations, hence the normalize programs. And some do need the timers. Cap to shield for example, could you imagine how tough it would be to take down a ship with a 50+ regen cap, cap OL4 and instant cap to shield?
That is why I specifically said overloads. CtSS, etc, definatly need timers...not the overloads though. CtSS is not an overload.