Jump To Lightspeed Archive
Thread: What is the deal with making players wait 15 minutes with a disabled DI?
Page 1 of 2
quadpers0n
Tue Feb 15, 2005 8:34 am
#1
Is this a bug? I can't see the rationale in a 15 minute timesink because of a blown droid interface resulting from screwing up with your droid programs.
Example, you overload your reactor, then overload 4 your engine. Everythign is peachy until you die, then when you repair all on your components BOOM, your reactor overload had been reset on death, but your engine overload had not, resulting in a blown droid interfact that you can either wait for up to 20 minutes to fix itself, or land, remove all your components and deed your ship.
I'm not complaining about a blown DI, but it does seem a bit rediculous to force a timesink like that. Would it be a big deal to force the player to simply land to reset it?
Or am I missing some kind of workaround that I was unaware of?
Caliet
Tue Feb 15, 2005 8:44 am
#2
I can honestly say I have never seen that or heard of it happening before reading this thread. Very odd.
quadpers0n
Tue Feb 15, 2005 8:50 am
#3
you've never blown out your DI? it's easy to do. grab a medicore 13k generation (or lower) reactor, and overload 4 your engine.
Tuscanspeed
Tue Feb 15, 2005 10:47 am
#4
never had that problem either.
i AM usuing a 13k reactor and eo4.
very odd.
quadpers0n
Tue Feb 15, 2005 12:33 pm
#5
interesting. well try stacking a weapon overcharge 4 on top of that. maybe there's something wrong with my droid interface? what level engine are you using?
if i were to launch and use engine overload four right now in my light ship (13k generation reactor, level 4 DI, level 6 RE engine) it would blow out my droid interface immediately.
when it blows out all my components are "damaged" according to the readout, and i'm unable to use guns, booster, or any droid commands, ordinarily i'll fly at 50-80% speed as well.
attempting to use a droid command results in "your droid interface is disabled".
i'm finding it hard to believe nobody else has every had this problem, i know plenty of people onmy serverwho have.
Message Edited by quadpers0n on 02-15-2005 11:34 AM
VemaGara
Tue Feb 15, 2005 12:34 pm
#6
I never use EO4 because of this very issue. When launching a new ship, I test everything within range of a space station, just in case.
I had no idea that the DI would reset itself in 15 minutes.
I had no idea that the DI would reset itself in 15 minutes.
quadpers0n
Tue Feb 15, 2005 12:41 pm
#7
15 or so, i don't know what the exact time is.
My beef isn't with blowing out the DI, it's a neat dynamic... kind of. But why the timesink with the obtuse workaround?
MonsofoLexius
Tue Feb 15, 2005 2:35 pm
#8
I think what was happening for you is the DI takes damage and therefore is reset, the engine did not take any damage and was not reset. So I guess adding a "reset all overloads on death" might be a good one for you to add to the Pilot issues thread
quadpers0n wrote:
Is this a bug? I can't see the rationale in a 15 minute timesink because of a blown droid interface resulting from screwing up with your droid programs.
Example, you overload your reactor, then overload 4 your engine. Everythign is peachy until you die, then when you repair all on your components BOOM, your reactor overload had been reset on death, but your engine overload had not, resulting in a blown droid interfact that you can either wait for up to 20 minutes to fix itself, or land, remove all your components and deed your ship.
I'm not complaining about a blown DI, but it does seem a bit rediculous to force a timesink like that. Would it be a big deal to force the player to simply land to reset it?
Or am I missing some kind of workaround that I was unaware of?
quadpers0n
Tue Feb 15, 2005 2:38 pm
#9
yeah uh. i think you missed the point.
i know i'm running out of reactor, my question is why, when you do, does it disable your reactor for such an absurdly long amount of time or force you to redeed your ship?i mean honestly, 20 minutes. let me phrase that differently....
TWENTY MINUTES?!?
one third of an hour because you hit the wrong key? or due to a random reset of programs after exiting deep space/or being exploded?
it just seems absurd to me. if landing/relaunching reset it, ok fine I can see that. if you needed to repair to fix it, that's fine too. maybe a 1 minute downtime.
imo it's a bug.
edit: (this was posted asa reply to the 2nd to last post)
I think I bugged it in the pilot issues thread already though, however the extent of downtime wasn't something I mentioned because i don't know if it's working as intended or not.
Message Edited by quadpers0n on 02-15-2005 01:40 PM
Eaca
Tue Feb 15, 2005 4:09 pm
#10
Some pilot commands force a reset of the entire ship. If I bork a droid command I just run /eweap and when the special is over, all droid programs are reset, and I can go about my business. Not sure what the rebel or privateer equivalents are.
psikobunny
Tue Feb 15, 2005 4:38 pm
#11
I never use overload4's because of permanent damage to my parts. Eaca's solution is a good one though.
MonsofoLexius
Tue Feb 15, 2005 7:00 pm
#12
drop me post there (or edit your first with more info) we wil see if more are having the same problem or if I can reproduce (or get a guildy to do so)
quadpers0n wrote:
yeah uh. i think you missed the point.
I think I bugged it in the pilot issues thread already though, however the extent of downtime wasn't something I mentioned because i don't know if it's working as intended or not.
Message Edited by quadpers0n on 02-15-2005 01:40 PM
S-1-l2-H-C
Wed Feb 16, 2005 12:14 am
#13
i get this every now and then when i leave deep space. sometimes it resets my reacotr overload program but leave engine overload 4 active, and everything gets disabled. i dont wait 15min though, i run eshields or pump reactor, and when the special ends it resets the engine back to normal and everyhting is at full power agian.
Page 1 of 2