I posted an initial version of this in the IISS forum. I've attempted to simplify the original.
With the possibility of 8 stars (!) in a system, I've been using the following to distinguish primary, close, near, and far stars. When you work away from the * on the keyboard, you get (, {, and [ in that order.
It kinda looks like this --
Primary comp (Close comp) {Near comp} [Far comp]
where comp represents the companion to another star.
Finally, I use an * to tell me which star the MW orbits.
Some examples, using >> as the start of my remarks, and using dashes (for now) in my stellar data:
I contemplate simplifying the notation above, using a 8-character string at the end of the stellar data to show star locations. Each character in the string represents one star. This allows me to use EXISTING stellar info, and add my own interpretation of where each star is located. This also means I DON'T HAVE TO CHANGE existing stellar data, but can do it my way by simply adding MY interpretation of the stellar data.
The string defaults to P to indicate a Primary with NO other stars. For each additional star I add the e-hex value of the orbit, or a "c" for a companion, and go from left to right, one position per star, in the order above. I use a "." to represent a non-existent star.
IMTU I also have a custom 4-character field AFTER the stellar data, which I call the POsH, used to "locate" the mainworld. This gives me the detail level I want IMTU. I'll add the POsH to my new indicator, with a dash as a separator.
P = planet type where 0 is planet, 1 is close satellite, 2 is far satellite, and 3 is asteroid belt
O is for the SOLAR orbit A-Z
s is the satellite orbit if MW orbits a GG, or a . (decimal) if a true planet
H is the habitable zone indicator, - for HZ-1, = for HZ, + for HZ+1, or . for asteroid belt
To use the first example above, you could get this result, using P for primary, capitalized e-hex for orbits for the Near, Close, and Far stars, and c for the companions:
Primary is K6 III, MW orbits this star, no primary companion; Close M1 V in orbit 3, no Close companion; Near K0 V in orbit 10, Near companion inside orbit 0 (the letter c); no Far or Far companion. POsH indicates a planet, solar orbit 12, not a GG satellite, in the HZ. Note that this POsH is an example only, and may not be accurate for this stellar type.
To continue with the remaining stellar systems, again as examples only, POsH just a sample, and losing the dashes in stellar data:
Makes it a lot simpler to track things IMTU, and the only update is to add that "new" field to the existing stellar data. Haven't looked at updating any OTU sectors, but I'm testing this with my Varan sector, just for kicks.
Think there is any possibility of doing something like this for the T5SS?
Feedback wanted, and thank you!
With the possibility of 8 stars (!) in a system, I've been using the following to distinguish primary, close, near, and far stars. When you work away from the * on the keyboard, you get (, {, and [ in that order.
It kinda looks like this --
Primary comp (Close comp) {Near comp} [Far comp]
where comp represents the companion to another star.
Finally, I use an * to tell me which star the MW orbits.
Some examples, using >> as the start of my remarks, and using dashes (for now) in my stellar data:
Code:
*K6-III (M1-V) {K0-V K6-V} >> Primary, Close, Near with companion
F7-V {M1-VI} [*F5-VI] >> Primary, Close, Far, no companions
M0-V *M7-V >> Primary and primary companion
*G5-V [M1-V] >> Primary and Far
*G5-V >> Primary onlyI contemplate simplifying the notation above, using a 8-character string at the end of the stellar data to show star locations. Each character in the string represents one star. This allows me to use EXISTING stellar info, and add my own interpretation of where each star is located. This also means I DON'T HAVE TO CHANGE existing stellar data, but can do it my way by simply adding MY interpretation of the stellar data.
The string defaults to P to indicate a Primary with NO other stars. For each additional star I add the e-hex value of the orbit, or a "c" for a companion, and go from left to right, one position per star, in the order above. I use a "." to represent a non-existent star.
IMTU I also have a custom 4-character field AFTER the stellar data, which I call the POsH, used to "locate" the mainworld. This gives me the detail level I want IMTU. I'll add the POsH to my new indicator, with a dash as a separator.
P = planet type where 0 is planet, 1 is close satellite, 2 is far satellite, and 3 is asteroid belt
O is for the SOLAR orbit A-Z
s is the satellite orbit if MW orbits a GG, or a . (decimal) if a true planet
H is the habitable zone indicator, - for HZ-1, = for HZ, + for HZ+1, or . for asteroid belt
To use the first example above, you could get this result, using P for primary, capitalized e-hex for orbits for the Near, Close, and Far stars, and c for the companions:
Code:
*K6-III (M1-V) {K0-V K6-V} >> *K6-III M1-V K0-V K6-V P.3.Ac..-0C.=Primary is K6 III, MW orbits this star, no primary companion; Close M1 V in orbit 3, no Close companion; Near K0 V in orbit 10, Near companion inside orbit 0 (the letter c); no Far or Far companion. POsH indicates a planet, solar orbit 12, not a GG satellite, in the HZ. Note that this POsH is an example only, and may not be accurate for this stellar type.
To continue with the remaining stellar systems, again as examples only, POsH just a sample, and losing the dashes in stellar data:
Code:
F7-V {M1-VI} [*F5-VI] >> F7 V M1 VI *F5 VI P...8.F.-3M..
M0-V *M7-V >> M0 V *M7 V Pc......-00.=
*G5-V [M1-V] >> *G5 V M1 V P.....C.-27p-
*G5-V >> *G5 V P.......-04.=Think there is any possibility of doing something like this for the T5SS?
Feedback wanted, and thank you!
