Well all this talk of Universe made me go and have a look. And since it was only £11.99 from Gnome Trader I decided to pick myself up a copy. Hopefully should arrive in the next few days.
It depends on what the error is:
There is a rule in CT Book 6 that said if you roll a K5-M9 subgiant (IV) or a B0-F4 subdwarf (VI) you should change the size to Main Sequence (V). Unfortuneately a lot of the data sets available seem to ignore this rule and so you get illegal stars. This becomes a problem in system generation as there are no luminosity figures to go on. During the import process if Universe encounters this error it will convert the star to a Main Sequence star. It will also auto correct some of the more obveous typos. (Such corrections are reported at the end of each sector import.)
Universe will reject completely any non-sensical UWP codes. So, for example, you couldn't have a system with a size code of "J".
However, UWPs where there is a non-valid combination of codes will be accepted ... but if you go to the UWP Maint screen these errors are flagged for your attention. And this combination checking takes into account the various alien module variants. For example, Andor/Five Sisters is a Droyne world. Therefore it should only have a government code or "6", "7", or "X" ... but it actually has a government code of "3" (probably because the code was assigned in Supplement 3, which was published before the Droyne Alien Module was written).
Regards PLST
Why? (curious)
You've figured which hexes are in the J6 map. I've got an algorithm that works to figure all hexes within N hexes of the target (and I can do anything from 1 to >> but generally limit it to six). Now, I just figure out the hex numbers, and would let the software then figure out how to pull the contents out of the DB, myself. But I'd like to second a request for J1..6 maps.
</font>[/QUOTE]The basic reason why is that no one's asked for this until now. They have asked for non-standard maps for use with pocket empires and the like. I suppose I'll have to add this to the list as well!
Regards PLST
M
Malenfant
Guest
That right there limits the usefulness of Universe to me then. I use UWPs, but I've added a few - B & C terrestrial size codes, and G & H atmospheres. One could also maybe add D & E+ size codes for gas giants too.
As it stands, other packages don't restrict this. If I'd have to jump through hoops and tinker with databases so that Universe doesn't reject any odd UWPs like that, then I fear I'm better off sticking with something like Galactic. I don't want a program that automatically 'corrects' my UWPs whether I want it to or not.
Also, I don't think I'd be comfortable - at this stage - in buying something that - while usable - is still not entirely developed (in the sense that you mention that H&E stuff still is yet to be added).
I think I'm going to have to pass on Universe, I'm afraid. But thanks for all the info anyway.
That right there limits the usefulness of Universe to me then. I use UWPs, but I've added a few - B & C terrestrial size codes, and G & H atmospheres. One could also maybe add D & E+ size codes for gas giants too.
</font>[/QUOTE]Thus the question about modifying the static data: to allow someone to use non-canon codes. At the moment I'm thinking of adding in some maintenance functions to allow this without having to use IBconsole (even though IBconsole is actually pretty easy to use once you understand it).
That's a valid choice ... for my self I'd rather know when non-canon codes are used and be able to decide if they are errors or not. And I hate it when programs crash or behave strangely because of simple data errors.
You could wait a long time. Release 2 is planned as the system generation release. Release 3 is planned to add dynamic NPCs (both ships and people). Release 4 is planned ... you get the idea. Each major release should be 1 to 2 years apart depending on RL intrusions.
Regards PLST
