[FSD] Add Star Class to System name

Simple request, add the Star Class under the System name, above the Security Level.
Star_Class.png

Alternatively, it could go on the Jump target, but the point is to make an awareness that is not in the perishable Information window.
 
It tells you if there is a scoopable star in Primary, shown in your picture, or secondary or none which is the most important information.

The temporary does show the class briefly and you can spot stars with jets during the jump.

So I am curious about why you believe it is needed?
 
It already tells you in the Info panel (top right). I don't think it shows it for the entire countdown though, so I guess it's easy to miss.
 
It already tells you in the Info panel (top right). I don't think it shows it for the entire countdown though, so I guess it's easy to miss.
it's a passing message like any other, so it can be missed or covered by other messages. But yeah, you get that info, at the start of the countdown, I think.
 
You can see them coming, well you can if you are an experienced explorer, but is it that you want to avoid them? There's a route setting for that.
No, I am not trying to avoid them, it is more in the way of not being caught unprepared. This would give you that 4 second window where you can't do anything else to identify the star.

We are literally talking about injecting a single line of code into the middle of an existing procedure, something along the lines of:

PRINT "Star Class: " Jump_Target_Star_Class$

where the variable has already been defined because it is used in the INFO window.
 
Didn’t we used to get the star class a few versions of the HUD ago before either the security level or more likely fuel star info was added?
 
No, I am not trying to avoid them, it is more in the way of not being caught unprepared. This would give you that 4 second window where you can't do anything else to identify the star.

We are literally talking about injecting a single line of code into the middle of an existing procedure, something along the lines of:

PRINT "Star Class: " Jump_Target_Star_Class$

where the variable has already been defined because it is used in the INFO window.

You can't be caught unprepared, what do you need to prepare? You can literally see them coming even if you miss the message, the graphic at the far end of the jump sequence is unmistakable. Now let's just note that we get two different messages in the center where you want the star class, we get one message when we jump into an empty system telling us about fuel stars, and a different message when we jump into an occupied system, with no data about the fuel star at all, the data about the fuel star vanishes and is replaced by other data about the occupied system, the extra data isn't simply added. This indicates to me, because they had to remove some data to put different data in, that the amount of info that can be put into that little box in the middle of the screen is limited in scope. That is if they put in what you want then they will need to take out something. It's all very well implying something is simple, but you don't know whether or not the amount of data that can be stored in that area is hard coded.
 
Simple request, add the Star Class under the System name, above the Security Level.
View attachment 407444
Alternatively, it could go on the Jump target, but the point is to make an awareness that is not in the perishable Information window.
Its pretty easy, it tells you when you jump.
If your out in the Black you can then cancel the jump and plot a new course to a scoopable.

O7
 
The only thing I'd like an alert for is when I jump into a binary system and I'm about to pass through the smaller star to get to the main star as I leave hyperspace. That underwear had to go straight into the incinerator.
 
That's not how discussion forums work, you want to stop people discussing your idea you need to get the mods to close the thread, otherwise it's discuss on my friends!
...and now I am violating my statement to myself.

It was a declaration, not an ordination. I chose not to continue contributing and announced that fact.

I have refrained from expressing my opinion about your statements because I am uninterested in acquiring another soft ban for flaming.
 
...and now I am violating my statement to myself.

It was a declaration, not an ordination. I chose not to continue contributing and announced that fact.

I have refrained from expressing my opinion about your statements because I am uninterested in acquiring another soft ban for flaming.
If your declaration had been more explicit you might not have needed to come back.
 
Back
Top Bottom