Cartographer’s Log, Stardate 2018.1224
Here is a new template for resource deposit mapping, applied to the first sector of Federation space (from independent space to P’Jem).
The first sectors of Romulan and Klingon space are comparable in structure, but have significant differences in terms of resource availability. Detailed maps to follow.
Findings show that Level 27 faction system clusters follow the same mold as those at 25: a center system, with three pairs of spokes at ascending levels (24-26).
All three factions have virtually identical structures for their level 27 clusters, with the primary differences being hostile type and resources in each system.
Key findings:
Raw data in table format…
| Name (Level) | Star Color | Hostiles | Resources | Planets |
| Vendus A (27) | Orange | Explorer/Survey 26-28 | 18x 3* Ore (6000), 1x 2* Gas, 5x Dilithium | 4x station hubs, 4x mission objects |
| Nipaj (24) | Blue | Battleship/Survey 23-25 | 25x Parsteel (7000) | 10x station hubs, 1x mission object |
| Wauoxic (24) | Red | Explorer 23-25 | 25x Parsteel (7000) | 10x station hubs, 1x mission object |
| Jeuaiei (25) | Blue | Interceptor/Survey 24-26 | 25x Parsteel (7000) | 10x station hubs, 1x mission object |
| Mewudoh (25) | Blue | Battleship/Survey 24-26 | 25x Parsteel (7000) | 10x station hubs, 1x mission object |
| Rooth (26) | Orange | Interceptor/Survey 25-27 | 12x Parsteel (5000) | 14x station hubs, 2x mission object |
| Strezhi (26) | Orange | Explorer/Survey 25-27 | 12x Parsteel (5000) | 14x station hubs, 2x mission object |
| Enthra (27) | Orange | Battleship/Survey 26-28 | 13x Dilithium, 12x 2* Raw Crystal | 4x station hubs, 3x mission objects |
| Vosak (24) | Orange | Battleship/Survey 23-25 | 25x Parsteel (7000) | 10x station hubs, 1x mission object |
| Loait (24) | Blue | Interceptor/Survey 23-25 | 25x Parsteel (7000) | 10x station hubs, 1x mission object |
| Loaiy (25) | Blue | Explorer/Survey 24-26 | 25x Parsteel (7000) | 10x station hubs, 1x mission object |
| Laija (25) | Blue | Interceptor/Survey 24-26 | 25x Parsteel (7000) | 10x station hubs, 1x mission object |
| Ias (26) | Orange | Battleship/Survey 25-27 | 12x Parsteel (5000) | 14x station hubs, 2x mission object |
| Izth (26) | White | Explorer/Survey 25-27 | 12x Parsteel (5000) | 14x station hubs, 2x mission object |
| Doska (27) | Red | Interceptor/Survey 26-28 | 9x 2* Raw Ore, 9x Dilithium, 7x 3* Raw Gas | 4x station hubs, 3x mission objects |
| Metea (24) | Red | Interceptor/Survey 23-25 | 25x Parsteel (7000) | 10x station hubs, 1x mission object |
| Bazamex (24) | Blue | Explorer/Survey 23-25 | 25x Parsteel (7000) | 10x station hubs, 1x mission object |
| Mapic (25) | Blue | Explorer/Survey 24-26 | 25x Parsteel (7000) | 10x station hubs, 1x mission object |
| Eagutim (25) | Blue | Battleship/Survey 24-26 | 25x Parsteel (7000) | 10x station hubs, 1x mission object |
| Querlz (26) | Orange | Battleship/Survey 25-27 | 12x Parsteel (5000) | 14x station hubs, 2x mission object |
| Durchman (26) | Orange | Explorer/Survey 25-27 | 12x Parsteel (5000) | 14x station hubs, 2x mission object |
Cartographer’s Log, Stardate 2018.1217
My completed study of the Gemet Cluster has yielded interesting results.
As suspected, those results extend to the Romulan and Klingon cluster equivalents, Sufiday (25) and Yadow (25), with one very minor difference (Yadow has one less mission planet).
Consolidated overview of each cluster:
(25) 4x Tritanium, 24-26 Explorer/Survey, 4x hubs, 2x mission
Key findings:
Raw data follows for review…
Cluster Center
Alignment:
Star Color:
Hostiles:
Planets:
Resources:
Cluster:
Alignment:
Star Color:
Hostiles:
Planets:
Resources:
Cluster:
Alignment:
Star Color:
Hostiles:
Planets:
Resources:
Cluster:
Alignment:
Star Color:
Hostiles:
Planets:
Resources:
Cluster:
Alignment:
Star Color:
Hostiles:
Planets:
Resources:
Cluster:
Alignment:
Star Color:
Hostiles:
Planets:
Resources:
Cluster:
Alignment:
Star Color:
Hostiles:
Planets:
Resources:
Cartographer’s Log, Stardate 2018.1212
Setting aside interface bugs and the introduction of new features, the most common complaint regarding the Fleet Command experience seems to center around the protection and use of mining vessels.
The amount of mining required for certain missions means invariably, Survey class ships will be left to mine unattended on a regular basis. This leaves them susceptible to piracy, and often locks out the resource for other mining vessels, even after the resource has been completely depleted.
What if there were simple changes that could be made that could help safeguard mining vessels (without completely removing opportunities for piracy), while also ensuring depleted deposits were unblocked and allowed to regenerate?
With that in mind…
A mining vessel is being piloted by a crew, and that crew should be able to be given instructions to follow. All ships should have the following toggles on the ship management screen:
Note that these changes still allow pirates or alliances on strike missions to destroy the vessels that are actively mining; it just ensures better resource turnover, and decreases the threat to unattended mining vessels.
Please find me via Fleet Command interface at SimonWelles [MAP] to share your thoughts!
Cartographer’s Log, Stardate 2018.1211
For the purposes of this case study, I have temporarily relocated to Mapoc, a small planet orbiting the star Gemet in the Federation Sector.
Gemet is a level 25 system sitting at the center of a star cluster, with five planets, one starbase and four tritanium deposits in orbit.
The starbase and one of the planets are mission locations (yellow names in the diagram below), while the other four planets are station hubs (blue names).
Hostiles in orbit here are Federation Traders (Survey class) and Federation Patrols (Explorer class), levels 24 – 26, both Federation-aligned.
As of today, there are only three stations in the entire system, each orbiting a different planet.
In this post, we explore a flow chart outlining “Sector Two” of the galactic map, spanning all systems between Rigel (13), and the edges of space controlled by the three factions (Federation, Romulan, and Klingon)…
In the chart above, we highlight areas containing different elements, including:
Important items of note:
The galactic map in Star Trek: Fleet Command seems vast, and can be difficult to navigate.
However, the design of the galaxy is patterned to create a uniform experience, regardless of where your starting system is.
As a result, the map can be compressed into the following flow chart, showing all of the key stars and high yield resource zones in what we’ll call the “first sector”. This sector begins with the level 1 systems we all begin in, and ends at Rigel, a level 13 system that acts as a gateway into the next “sector”.
We’ll explore subsequent sectors in future posts. For now, here’s Sector One:
As you can see, the flow is identical, with the only anomaly being Murasaki 312, a level 10 system connected to Tellun (which coincidentally also holds the wreckage of Leviathan).
In the diagram above, we’ve introduced the notion of a “resource field”. Most systems contain a small number of resource deposits for mining. However, in “resource field” systems, deposits of a noted resource are plentiful, making those systems key destinations for mining vessels.
NOTE: There is a small dilithium supply at Clytomenes (12), but not enough to qualify as a field. It is labeled with light blue.
Understanding the patterns involved makes navigating the system easy. Note that all systems at the same position in the flow chart have identical resource provisions (or lack thereof, depending).
Next time, we’ll examine the flow from Rigel into faction space!
Simon Welles
Admiral, Inner Light [LITE]
Stellar Cartography Department 