Posted by: Deoxy
« on: April 06, 2011, 10:45:23 AM »Quote from: Erik Luken link=topic=3437. msg33246#msg33246 date=1302041650
Easily fixed. You can upload CSV files.
Yay - thanks!
Here it is - hope it's useful.
Easily fixed. You can upload CSV files.
I've pulled a list, and there are a LOT more than I realized - just over 1000. Putting it in the wiki is a great idea. . . but not one I've got time to help with just right now (sorry).
The most useful thing I really wanted out of it was the prerequisites, but I've got development cost and a few other things, too. I've dumped it to a comma delimited file and tried to get it sorted in a useful-ish fashion (the order by ID number was. . . odd), so if anybody wants to make use of it, enjoy.
Aaannnddd nevermind. . . the forum only allows graphic attachments.
I rarely utilise hyper engines myself.
As for the tech trees, the best and appropriate place would be in the wiki. There are skeletons of most of the techs already there.
*edit* link to the wiki article
hxxp: aurorawiki. pentarch. org/index. php?title=Aurora_Player_Designed_Systems
I use hyperdrives heavily atm. It depends on the landscape I suppose. For instance my Sol system has four jump points, three of which lie just outside the hyperlimit, with one being a few hours inside. My main spaceport and shipment centre is on Pluto, which is outside the limit too, where I stockpile all the minerals coming from the colonies and installations intended to go to the colonies. I have a dedicated fleet of fast non-hyperdrive freighters that only operate the Earth-Pluto route, and hyperfleets who serve other important systems, most of which have jump points way beyond the hyperlimit too. Those freighters don't visit Earth but circle around the hyperlimit, and travel times are much reduced due to this, even though it is more effort when giving them orders to make them touch all those waypoints.
Meh. Even with those advanced techs, there would have to be some SERIOUS resources out there to bother doing anything with it. I suppose the error I'm getting is due to travel time, not distance, then.
As to techs, I suppose I can build the list and post it, then. The underlying data structure is wonderfully simple (in a very good way, I mean), so it shouldn't take long.