World Map and T5 System Generator - new release

[OjnoTheRed]

I have been fooling around with the app, and I may have found a problem.
If you tell the app to place the home world in the habitable zone and make it a satellite. Then there will only be the one satellite, the home world. Even if it is a large gas giant that the home world is orbiting. Is that a bug or a feature?

You have sharp eyes! That is a bug - I will check it out. Your description makes it easy. You are quite correct, even where the main world is placed in the orbit of a GG as a satellite, we still need to roll for the number of satellites and there can be others.

Many thanks!

 

[Frewfrux]

I've noticed that if you generate a system where the main world ends up in the habitable zone, then adjust the MW to another orbit, even one on the far reaches of the system, the "hospitable" tag moves with it...even though average temps are well below -200C and water cannot exist naturally in liquid form.

 

[OjnoTheRed]

I've noticed that if you generate a system where the main world ends up in the habitable zone, then adjust the MW to another orbit, even one on the far reaches of the system, the "hospitable" tag moves with it...even though average temps are well below -200C and water cannot exist naturally in liquid form.

To clarify, the "Hospitable" tag is the type of UWP roll that was used. In T5, the standard UWP generation is "hospitable", but there are others such as Big World, Worldlet, Ice World and so on. Once the UWP is generated the tag has less meaning; Big Worlds are obviously big because of their size digit, etc.. I have invented a system layout that includes the 'content type' as the type of world in that orbit zone; this lets us, for example distinguish between a Size 0 Worldlet and a Planetoid Belt. And some tags carry a bit more meaning, e.g. Rad World or Storm World which tells you something about them.

I want to exploit the tags more in generating world details - for example, Rad Worlds automatically get population zero - and need a note about the atmosphere that any taint or rating of Corrosive or Insidious should be caused by radiation.

The main problem I see with the T5 system rules is that regardless of zone, some worlds attract a standard atmosphere role, leading to the curious situation of a standard nitrogen/oxygen atmosphere appearing in worlds with temperatures below the freezing points of oxygen and nitrogen.

 

[PVernon]

I think a lot of us are thinking that a world designated "Habitable" is in the habitable zone of the star. That does not necessarily mean that it is habitable. Earth is in the middle of the habitable zone of it's star and is. Venus is also in the habitable zone of the star but near the inner limit of the zone, and Mars is on the outer edge of the zone. Neither of them rolled up as "Habitable" but they could have.

 

[OjnoTheRed]

New release is out!

The biggest change is that once you have generated a star system, you can save it (and any changes you make) to a library of saved systems. You can also load, update, delete and import and export saved systems. The exported data is a JSON file you can share with friends! This also opens up the possibility of a library of canon data on certain systems (e.g. Earth, Regina).

There are other minor bug fixes, interpretations and updates - see the Change Log if interested.

I now feel more free to move onto interpreting Grand Census and the T5 Cultural Extension because we have a way of saving and keeping data about systems to help Referees keep work over time. I know just naming every object in a system takes a lot of work.

 

[ShawnDriscoll]

JSON. Cool!

 

[SanDragon]

Link in my signature. Four new things in this release.

1) Noble estates will no longer be placed in open ocean.

And, what if it's a water world?

 

[PVernon]

It looks like the main world as a moon problem is still there. I do note that the name of the worlds orbit tends to be somewhere in the middle of the alphabet, does that imply that the program generates stuff in other orbits but does not put them in the output?

 

[OjnoTheRed]

And, what if it's a water world?

Good question!

But relax. There are always islands generated for a water world, and hexes with islands count as 'land' for this purpose.

 

[OjnoTheRed]

It looks like the main world as a moon problem is still there. I do note that the name of the worlds orbit tends to be somewhere in the middle of the alphabet, does that imply that the program generates stuff in other orbits but does not put them in the output?

Aaaargh! Totally forgot to address "the main world as moon" problem. So sorry - I will address it. And I was even looking directly at that exact code to solve certain problems with saving the system and exporting it as a JSON file.

The generated satellite orbit is random but is based on a flux roll - which is roughly equivalent to a 2D roll - so, yes, it would be biased towards the middle. But change the seed and re-run the generator on the same system to see what happens.

 

[OjnoTheRed]

JSON. Cool!

Thanks Shawn! Also if you have a look at the exported JSON files using a text editor, you will see how the code 'thinks' about the star system as a whole.

 

[OjnoTheRed]

It looks like the main world as a moon problem is still there.

Spurred on by your feedback, I have fixed the problem! Let me know of any scenarios where it happens to not work. In the end the change involved adding just one line of code.

 

[Timerover51]

I take it that this only works with worlds on the Traveller Map, with no provision for worlds not on the Traveller Map.

 

[OjnoTheRed]

I take it that this only works with worlds on the Traveller Map, with no provision for worlds not on the Traveller Map.

Not at all; you are free to enter your own details or press the "Generate Missing World Details" (which can be all of them). It works with whatever you have entered and validates the data before proceeding.

 

[Timerover51]

Not at all; you are free to enter your own details or press the "Generate Missing World Details" (which can be all of them). It works with whatever you have entered and validates the data before proceeding.

That appears to work, but what do all of the little dots in the hexes represent? They appear in both water and land hexes.

 

[OjnoTheRed]

That appears to work, but what do all of the little dots in the hexes represent? They appear in both water and land hexes.

Could I ask you to post a screen snapshot?

 

[dalthor]

Temperature range questions

Noticed today that Varan (a garden world, A8676C7-G Ga Ni Ag Ri) generated an AVERAGE temperature of -70c; Upper temp limit 438c, and lower limit -100c. Random number SEED 4183420570

Terra (A867A69-F Ga Hi) generated an average of -6c, upper limit 662c, lower limit -46c. Random number SEED was 1713661345

Been a while since I last generated details, so I don't know how recently this [possible bug, more likely a gremlin ] occurred.

 

[OjnoTheRed]

When real-world physics enters into Traveller, very severe constraints are put upon temperature ranges. To get the desired picture of a garden world or an Earth, the user needs to tweak orbital distances, albedo and greenhouse themselves. All of these are fully editable. The random generator is just that - random. It completely ignores the picture presented by the trade codes and rolls dice to determine placement of everything.

The biggest issue is the distribution of star types. Reflecting reality, M0 V to M9 V stars are the most common; however, the habitable zone is either Orbit 1 or Orbit 0 (Mercury or closer), tidally locking the world. Our "Ga Ag Ri" world just became a twilight zone world, baked to temperatures often more than 200 degrees Celsius, and freezing temperatures less than -100 degrees on the permanent night side. This would logically lead to wild storms in the twilight zone as gasses and water freeze and vapourise.