The Orbital update has introduced the notion of starship construction. For those who haven't explored this aspect of the game yet (or are still waiting for the Xbox update), the new space stations have a construction terminal where you can build a fighter, explorer, or hauler (no solars, exotics, shuttles, or interceptors at this time).
The way it works is, each ship is constructed from base components that you obtain by salvaging a starship, and a reactor core that you purchase from the starship tech merchant at the station (the class of the reactor core determines the class of the ship).
For a hauler you need: cockpit, wings, and engine. For a fighter, it's: fuselage, thruster, and wings. For an explorer, you have hull, left wing and right wing. Note that each component can (and for wings, typically is) a set of multiple of components, which is how you get all the variations.
To obtain a component, you have to scrap a ship that has the configuration you want. The ship scapper has a new option to let you salvage one component. So if you want to make a ship, you have to scrap three ships total to get each component: cockpi+wing+engine for hauler, fuselage+wing+thruster for fighter, and left+right+hull for explorer.
Testing has shown that supercharged slot arrangement is procedural. The same components (including the reactor core, so S-class vs A-class etc. matters) at the same space station will result in the same SC slot configuration. Color is irrelevant.
So what does this mean for the Glyph Exchange?
It means we can publish glyphs to space stations that result in favorable SC slot arrangements for a given starship configuration. The question is, how best to do that?
Since the subject lines here are intended to serve as an index, I'd like to suggest using this form:
Fabricated Starship/Galaxy
Then we have to name the parts and provide a photo of the SC slot configuration that you get from that space station with that configuration.
As for part naming, though it's tempting to use the game's "language" for the parts, there are a lot of component names because they are describing combinations of parts rather than the parts themselves, and those names have a lot of potentially confusing redundancies. I think it's better for us to stick with the standard part names we always use, as people are already familiar with those and it's pretty easy to figure out which ships you need to scrap to get what you want.
Can you please update your title to put "Planet/Hicanpaav" at the beginning? That way this comm can function as a searchable index.
Thank you!
You stay there until you explicitly leave for another galaxy.
Not for a staff. It is purely terminal + staff head.
Welcome to Wuburyd VIII, a paradise planet in the Strakovdo XV yellow-star system in Calypso.
This planet is a symphony of blues. From space, the ground looks like it's purple, but the planet has a filter applied to it that causes the purple to turn to a vivid, royal blue when you enter the atmosphere. And nearly everything else here is blue as well: in addition to the blue bioluminescent grass, you have blue water, blue skies, a bluish tint to the sand, and even some of the trees are blue (and those that aren't are a violet that is blue-adjacent). And of course, the bubbles look blue.
This planet is crazy-blue, everywhere, all the time.
Glyphs in Calypso
The only two relevant variables are the staff's head and the terminal. Those two determine class, color, and supercharged slot layout.
Made that decision easy, I guess. :)
I should add that this is a very shitty planet, even by Calypso's standards. Do not go AFK while on foot unless you are inside a building (with doors--this planet has extreme wind events, and they will blow you out of a trading post).
I spend most of my time in Calypso. Those are the only days I've got.
Class for freighters is random.
I am working on my rainy day fund.
Thanks! It's not a cockpit style that I see very often. And stumbling across an S-class was a stroke of luck.
Can you please update your title to put “Planet/Ploehrliou” at the beginning? That way this comm can function as a searchable index.
Thank you!