Oolite Bulletins

Pleb wrote:

Was there not, maybe years ago, a way of dumping the galactic data/co-ordinates to the log, or something to that effect?

var galaxyNumber = S.info.galaxyID;
for (var i = 0; i<256; i++)
{
	var si = System.infoForSystem(galaxyNumber, i);
	log("sysinfos", "System: " + si.systemID + " Name: " + si.name + " Government: " + si.government + " Coordinates: " + si.coordinates + " Inhabitants: " + si.inhabitants + " TL: " + si.techlevel + " Description: " + si.description);
}

Pleb wrote:

The first thing I noticed with the seed I had originally chosen for Galaxy 9 was creating a galaxy with systems that only had 4 types of government instead of 8, so 64 of each type instead of 32, so I changed the seed to one that still had all the government types in.

Pleb wrote:

The next problem I detected was that, as Wildeblood originally stated when he created this thread, the system properties could not be edited by legacy script or Javascript. At first I thought this was going to be the end of this little experiment, but then I remembered I had seen something in the file Universe.m... And seeing as it was similar to the code I changed before I realised this is the code that ensures the galaxy seed matches the first 8 galaxy seeds or otherwise locks out all planetinfo.plist, script.plist or any Javascript changes to the system info data... Therefore I changed the above code... I also changed the code at line 5846, which looks the same to the same code... This now makes both legacy script and Javascript accept galaxy numbers 8 to 15 when scripting. It also answers Wildeblood's original question of why the system info data is made read-only when changing the galaxy seed, and how to overcome this issue in the source code.

Wildeblood wrote:

I won't bother to check ancient change logs

Wildeblood wrote:

You have, however, completely ruined my cunning plan to make a heroic re-entrance to the discussion when you got stuck.

Wildeblood wrote:

In fact, with a completely unmodified version of Oolite you can set the system properties of higher-numbered galaxies from javascript, and the changes will be duly recorded in local_planetinfo_overides; they just won't be applied to anything, but won't produce any kind of error or warning either.

• All 8 galaxies should hopefully have all 8 government types, as some can be generated without.
• Some galaxies should have unreachable (but not necessarily vast) areas of space.
• All 8 galaxies should have systems that reach Tech Level 14.
• They should not contain any system names that others might deem offensive (although the Arse system would be funny!).

Ahruman wrote:

But it’s fun! (svn blame <file> does most of the work.)

JD wrote:

It might just be me, but I like the idea of a galaxy where not all government types are present. A galaxy that was all anarchies and multi-governments could be quite interesting. Or at least one where the safer systems are under-represented.

JD wrote:

It might just be me, but I like the idea of a galaxy where not all government types are present. A galaxy that was all anarchies and multi-governments could be quite interesting. Or at least one where the safer systems are under-represented.

Fatleaf wrote:

I think this is a good idea that could be expanded. The devil is obviously in the detail. But one thought I had was maybe having a galaxy that was under attack by the Thargoids and so you met them on regular occasions.

Wildeblood wrote:

This empty template version of Galactic Hyperdrive XG OXP might be of use to someone. For use only with 16 galaxy versions of Oolite, it has the eight usual destinations arrays and eight empty arrays waiting for you to record your favourite destinations in uncharted space.

Smivs wrote:

Galaxy four has no Dictatorships

El Viejo wrote:

Nothing wrong with a few 'unreachable' system clusters - they can sometimes be reached via mis-jumps, as is the case with the Riftworlds in G7.