Actually, it is a defect or how it should be?
And if a defect, please make the possibility of writing descriptions for add-ons.

It's a defect / incomplete.
It's a defect / incomplete.
When to add a description of the planets?
Need descriptions =)
Yes. I'm looking at this. It's not easy, there is only limited space in the GUI.
Hmm, I think you can do this:
gui.(name of the selected planet \ moon \ star).desc = description
And most likely better to increase the information window
Or do Gui window:

This is a pretty GUI. But I will point out, the planet is not square...
Well, instead of round planets use the registered image for the planet \ moon.
If necessary, I can make a sketch GUI window.
If necessary, I can make a sketch GUI window.
Yes please, sounds great.
@radfast



If the lang file does not contain descriptions - do not display on the screen.
nice job, thank you it helps a lot.
.desc text. I might even add more in-game data.gui.[name].information.desc will be too long - I don't want to include so much text in the main .lang files. So I'm thinking a new .lang file in a folder named galacticraftcatalog. Translating galacticraftcatalog will be optional and the translation style can be different - maybe the translators can find information about the planet in their own language on Wikipedia or somewhere else, or maybe they want to write a shorter or longer text in their language.I am also thinking about merging all galacticraftmoon .lang files into galacticraftcore, and merging galacticraftmars and galacticraftasteroids .lang files into one.
.unexplored. If true, no description will be shown, only a "this planet is unexplored" message. Add-on authors can create in-game conditions which switch that to false. Do you think this unexplored data needs to be saved per player? Or do you think if one player discovers a planet, the whole world knows immediately?Did you make a configuration for enable \ disable save per player.
OK we can do it like this: CelestialBody.setExplored(EntityPlayerMP) and CelestialBody.setExploredAll().
I'm planning to add something like this in 1.8.9

Most helpful comment