Aurora 4x

VB6 Aurora => Aurora Chat => Topic started by: Shininglight on November 30, 2013, 10:20:28 PM

Title: Researching Components.
Post by: Shininglight on November 30, 2013, 10:20:28 PM
So i was wondering about how everyone here goes about it, i tend to jsut instant the component info unless i feel like going for a more story style feel but it seems to me a bit like cheating. Actually researching the component is a bit of a hassle to rearrange my ques and I feel it ads needless confusion. Anyways I was wondering how others go about getting the parts that go into actually making their ships.
Title: Re: Researching Components.
Post by: joeclark77 on November 30, 2013, 10:49:28 PM
Sometimes I'll instant the components in order to test them out, then delete them and research them the proper way.  I especially do this for missile engines, because I want to get them just right.  Otherwise I research my components normally.  It adds another level of challenge: at any given moment you have to decide whether to "commit" to a technology or to wait for "one more level...". If you commit too early, your designs will be inferior to your enemies', but if you keep researching for too long, you won't get anything into production in time.
Title: Re: Researching Components.
Post by: MarcAFK on December 01, 2013, 12:40:49 AM
I do that too, I just shove "PROTOTYPE" into the component name before I instant it, so i know to delete it later.
Title: Re: Researching Components.
Post by: alex_brunius on December 01, 2013, 04:49:01 AM
For very cheap components (5-10 days or less to research) I sometimes use instant "cheat". Especially if the base tech is much more expensive.

But for bigger projects things like main engines or carrier jump engines I would never consider it.
Title: Re: Researching Components.
Post by: Hawkeye on December 01, 2013, 12:33:55 PM
The only time I use instant research is, when I designed and researched a component and made a stupid mistake, like forgetting to raise the power modifier for a missile engine or something similar. Aside from that, everything gets researched (I sometimes even use the component with the stupid mistake, rationalizing it as contractor/contract/specification misprint/error/fraud).