{"data":{"id":18532,"title":"The Public Roadmap Companion","rsi_url":"https:\/\/robertsspaceindustries.com\/comm-link\/SCW\/18532-API","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-links\/18532","api_public_url":"https:\/\/api.star-citizen.wiki\/comm-links\/18532","channel":"Undefined","category":"Undefined","series":"None","images":[{"id":26651,"name":"STARCITIZEN_WHITE.png","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/y1f0boj8fak5rr\/source\/STARCITIZEN_WHITE.png","alt":"","size":73278,"mime_type":"image\/png","last_modified":"2021-02-03T06:54:29+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/26651","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/26651\/similar"}],"images_count":14,"translations":{"en_EN":"Public Roadmap Companion\nThe Star Citizen and Squadron 42 Public Roadmap is designed to give you an unprecedented look into the game development process by following every feature being worked on by our 50+ development teams, from their initial implementation to their release.\n\nStar Citizen and Squadron 42 are massive projects with lots to track, and this companion guide will help you read and navigate the Roadmap for both projects, as well as provide additional insight into the processes behind it.\n\nUpstream and Downstream\nThe Difference Between\nThroughout our development communications, you have likely seen us reference a team as being designated \"Upstream\" or \"Downstream\", which carries an important meaning. Upstream teams begin work on any given feature at the beginning of its process. They typically handle things like art, vehicles, locations, and gameplay features. These teams set the major tentpole deliverables for the rest of Star Citizen and Squadron 42, and as such, they're able to plan up to four quarters in advance, which is displayed in the Progress Tracker.\n\nDownstream teams are reactive and support the upstream teams, so they depend on the upstream teams scheduling and progress to determine their own work and priorities. Because of this, they're only able to plan for the upcoming quarter, rather than a full year.\n\nExample: The Vehicle Teams (Upstream) begin work planning a newly concepted ship, the Aurora. The Vehicle Content Teams then schedule out production of the Aurora, from a design, art, and animation standpoint. Once the ship is nearly built and the design is close to final, the downstream teams jump in and begin adding details like VFX, Audio, and UI. The important takeaway is that the downstream team relies on information from the upstream team in order to produce a schedule\/plan.\n\nThe Final Review Process\nFeature Cards are added to the Release View near the start of the quarter, once they've been completed for release and the QA process begins. These new cards will always show up on the Roadmap marked as Tentative, meaning the goal is to release in the next quarterly patch, but the feature has yet to pass its Final Review.\n\nEvery quarter, development Directors come together to review features approaching completion in an effort to evaluate if said feature is ready to be released to the live game. If a feature passes its Final Review, then it is integrated into the live release candidate and marked as Committed on the Roadmap. At this point, it is nearly certain that the feature will arrive with its corresponding update. Once the feature has been released to the Live servers, its status is then updated to Released.\n\nUpstream Teams\nActor Feature Team\n\nEU Landing Zone 1\n\nEU Landing Zone 2\n\nEU PU Gameplay Feature Team\n\nEU Sandbox 1\n\nEU Sandbox 2\n\nGame Services Team\n\nLive Tools Team\n\nMission Feature Team\n\nMTL Sandbox 1\n\nSystemic Services and Tools Team\n\nUS PU Gameplay Feature Team\n\nVehicle Feature Team\n\nVehicle Content Team - EU\n\nVehicle Content Team - US\n\nVehicle Content Team - MTL\n\nWeapon Feature Team\n\nDownstream Teams\nAI Content Team\n\nAI Tech and Feature Team\n\nArena Commander Feature Team\n\nAudio\n\nCharacter Tech Art\n\nCinematics Team\n\nEditor Team\n\nEngine Team\n\nFacial Animation\n\nGameplay Story\n\nGraphics Team\n\nInteractables Team\n\nLocation Concept Art\n\nLighting Team\n\nMotion Capture Team\n\nNarrative\n\nNetwork Team\n\nPersistent Tech Team\n\nPhysics Team\n\nPlanet Tech Team\n\nStar Citizen Character Art\n\nSquadron 42 Character Art\n\nSquadron 42 Art\n\nSquadron 42 Feature Team\n\nSquadron 42 Level Design 1 - FPS\n\nSquadron 42 Level Design 2 - Flight\n\nSquadron 42 Level Design 3 - Social\n\nSquadron 42 UI Feature Team\n\nTech Animation Team\n\nTools Team\n\nUI Tech Team\n\nVehicle Concept Art\n\nVFX Team\n\nWeapon Content Team\n\nYou'll also find additional teams displayed on Progress Tracker with scheduling data ending in the past completely. These are deprecated teams that have either been renamed, restructured, or combined with other teams.\nLast Updated: June 14, 2023\nProgress TrackerThe cornerstone of the Roadmap is the Progress Tracker view, which is the default view when you visit the Roadmap. The Progress Tracker pulls back the curtains for all teams, showing you what each team is working on this quarter and what their priorities are after completing the deliverable at hand.\n\nThis view presents a comprehensive look at features, art, and technology scheduled for production within the next four quarters. Keep in mind that this isn\u2019t necessarily when these items will be completed, simply when the work on them is scheduled to finish out by that team specifically.\n\nBelow is a breakdown of the information displayed in the Progress Tracker view and how to navigate it.\n\nWhat is a Deliverable?A deliverable in the Progress Tracker view is a 1:1 representation of a group of tasks scheduled for work in a particular time period. This can be just about anything, a ship or location, an AI behavior, or even a piece of core technology. Shown to the right is a list of deliverables for the Actor Feature Team.\n\nA deliverable will house all work scheduled to be worked on for that specific deliverable, including varied disciplines. For example, if you clicked on the \"Drake Vulture\", it would display work being done by numerous teams such as concept art, audio, etc.\n\nAll in the DetailsYou can sort between two major views when browsing the Progress tracker. First, you can sort by teams, which allows you to browse any work being completed by a specific development team. Alternatively, you can sort by Deliverable, which allows you to browse any\/all teams working on a specific deliverable. This multi-path approach is meant to give you the tools you need to follow along with development in great detail.\n\nExpanding a Deliverable, as shown in the image to the left, gives you further insight into what teams are working on a feature, and for how long. Here you can also see if a Deliverable is being worked on simultaneously with another on the same team, signified by a striped progress bar. Finally, you can also click on the team's abbreviation to navigate to the Teams view mentioned above.\n\nAdditional NavigationThe Progress Tracker reveals 500+ deliverables across 50+ teams. It's no secret that such a large dataset can be overwhelming, which is why it was a priority for us to provide you with tools to easily navigate the presented information. Most importantly, while in the Deliverables view, the search bar can help you find a specific deliverable based on a key word or two. Both the deliverable names and descriptions are indexed, so you're able to search for something even if you don't know exactly what it's called.\n\nAdditionally, the filters on the right side of the Roadmap allow you to sort deliverables by project (Star Citizen, Squadron 42, or both), as well as their Release View categories.\n\nRelease ViewThe second section of the Roadmap is the Release View. The Persistent Universe of Star Citizen receives updates on a quarterly basis, and the Release View's intent is to show the planned features for the next quarter's Persistent Universe update. These cards represent a high level of confidence in their release timing, however these features may still move depending on unforeseen circumstances or a change in priority.\n\nRelease WindowsThe columns displayed on Release View represent release windows for their respective quarters, labeled with a patch number. The column displays the overall status of the release at the top, along with the intended timing of the start of the patch cycle.\n\nEach column represents the entire cycle, both the initial release as well as any incremental follow up patches. For example, Alpha 3.15.0 released on November 10, 2021, but a follow up 3.15.1 update was released a few weeks later that added new ships and content. All of this is represented together under the 3.15 column on Release View.\n\nFeature CardsAll features scheduled for release are represented by \"cards\" on Release View, sorted into these categories: Locations, AI, Characters, Gameplay, Ships and Vehicles, Weapons and Items, and Core Tech.\n\nEach of these cards displays a description of the feature, an image, and links to the corresponding Progress Tracker deliverable. Above the feature you can see its current status of Tentative, Committed, or Released, which is determined by the status of its final reviews.","de_DE":"\u00d6ffentlicher Fahrplanbegleiter\nDie Star Citizen und Squadron 42\nDie \u00f6ffentliche Roadmap von Star Citizen und Squadron 42 soll dir einen noch nie dagewesenen Einblick in den Entwicklungsprozess des Spiels geben, indem du jedes Feature, an dem unsere \u00fcber 50 Entwicklerteams arbeiten, von der ersten Implementierung bis zur Ver\u00f6ffentlichung verfolgen kannst.\n\nStar Citizen und Squadron 42 sind riesige Projekte, bei denen es viel zu beachten gibt. Dieser Leitfaden hilft dir, die Roadmap f\u00fcr beide Projekte zu lesen und zu navigieren, und gibt dir zus\u00e4tzliche Einblicke in die Prozesse dahinter.\n\nUpstream und Downstream\nDer Unterschied zwischen\nIn unserer Entwicklungskommunikation hast du wahrscheinlich schon gesehen, dass wir ein Team als \"Upstream\" oder \"Downstream\" bezeichnen, was eine wichtige Bedeutung hat. Upstream-Teams beginnen mit der Arbeit an einem bestimmten Feature am Anfang des Prozesses. Sie k\u00fcmmern sich in der Regel um Dinge wie Grafik, Fahrzeuge, Schaupl\u00e4tze und Gameplay-Features. Diese Teams legen die wichtigsten Meilensteine f\u00fcr den Rest von Star Citizen und Squadron 42 fest und k\u00f6nnen daher bis zu vier Quartale im Voraus planen, was im Progress Tracker angezeigt wird.\n\nNachgelagerte Teams sind reaktiv und unterst\u00fctzen die vorgelagerten Teams, d.h. sie sind bei der Festlegung ihrer eigenen Arbeit und ihrer Priorit\u00e4ten von den Planungen und Fortschritten der vorgelagerten Teams abh\u00e4ngig. Aus diesem Grund k\u00f6nnen sie nur f\u00fcr das kommende Quartal planen und nicht f\u00fcr ein ganzes Jahr.\n\nBeispiel: Die Fahrzeugteams (Upstream) beginnen mit der Planung eines neu konzipierten Schiffs, der Aurora. Die Fahrzeug-Inhaltsteams planen dann die Produktion der Aurora aus Sicht des Designs, der Kunst und der Animation. Sobald das Schiff fast fertig ist und das Design fast fertig ist, beginnen die nachgelagerten Teams damit, Details wie VFX, Audio und UI hinzuzuf\u00fcgen. Wichtig ist, dass das nachgelagerte Team auf die Informationen des vorgelagerten Teams angewiesen ist, um einen Zeitplan zu erstellen.I.\n\nDer finale \u00dcberpr\u00fcfungsprozess\nFeature Cards werden zu Beginn des Quartals in die Freigabeansicht aufgenommen, sobald sie f\u00fcr die Freigabe fertiggestellt sind und der QA-Prozess beginnt. Diese neuen Karten werden in der Roadmap immer mit dem Vermerk \"Tentativ\" angezeigt. Das bedeutet, dass das Feature mit dem n\u00e4chsten Quartals-Patch ver\u00f6ffentlicht werden soll, aber noch nicht die Endpr\u00fcfung bestanden hat.\n\nJedes Quartal kommen die Entwicklungsleiter\/innen zusammen, um Features, die kurz vor der Fertigstellung stehen, zu \u00fcberpr\u00fcfen und zu entscheiden, ob das Feature bereit ist, f\u00fcr das Live-Spiel freigegeben zu werden. Wenn ein Feature den Final Review besteht, wird es in den Live-Release-Kandidaten integriert und auf der Roadmap als Committed markiert. Zu diesem Zeitpunkt ist es fast sicher, dass die Funktion mit dem entsprechenden Update ver\u00f6ffentlicht wird. Sobald die Funktion auf den Live-Servern freigegeben wurde, wird ihr Status auf \"Freigegeben\" aktualisiert.\n\nFortschrittstracker\nDer Eckpfeiler der Roadmap ist die Fortschrittsanzeige, die als Standardansicht angezeigt wird, wenn du die Roadmap besuchst. Sie zeigt dir, woran die einzelnen Teams in diesem Quartal arbeiten und welche Priorit\u00e4ten sie nach der Fertigstellung des jeweiligen Projekts haben.\n\nDiese Ansicht bietet einen umfassenden \u00dcberblick \u00fcber Funktionen, Kunst und Technologie, die in den n\u00e4chsten vier Quartalen in Produktion gehen sollen. Im Folgenden erf\u00e4hrst du, welche Informationen in der Progress Tracker-Ansicht angezeigt werden und wie du dich dort zurechtfindest.\n\n\nWas ist ein Deliverable?\n\nAlles in den Details\n\nZus\u00e4tzliche Navigation\n\nWas ist ein Deliverable?\nEin Deliverable in der Progress Tracker-Ansicht ist eine 1:1-Darstellung einer Gruppe von Aufgaben, die f\u00fcr die Arbeit in einem bestimmten Zeitraum geplant sind. Das kann alles M\u00f6gliche sein, ein Schiff oder ein Ort, ein KI-Verhalten oder sogar ein Teil der Kerntechnologie. Auf der rechten Seite siehst du eine Liste der Aufgaben des Actor Feature Teams.\n\nEine Aufgabe enth\u00e4lt alle Arbeiten, die f\u00fcr diese spezielle Aufgabe geplant sind, einschlie\u00dflich verschiedener Disziplinen. Wenn du z. B. auf \"Drake Vulture\" klickst, werden die Arbeiten verschiedener Teams angezeigt, z. B. Konzeptkunst, Audio usw.\n\n\nAlles im Detail\nDu kannst zwischen zwei Hauptansichten sortieren, wenn du den Progress Tracker durchsuchst. Zum einen kannst du nach Teams sortieren, so dass du alle Arbeiten eines bestimmten Entwicklungsteams sehen kannst. Alternativ kannst du auch nach der Leistung sortieren, so dass du alle Teams sehen kannst, die an einer bestimmten Leistung arbeiten. Dieser mehrstufige Ansatz soll dir die Werkzeuge an die Hand geben, die du brauchst, um die Entwicklung im Detail zu verfolgen.\n\nWenn du ein Deliverable erweiterst, wie in der Abbildung links gezeigt, erh\u00e4ltst du weitere Informationen dar\u00fcber, welche Teams wie lange an einem Feature arbeiten. Hier kannst du auch sehen, ob an einem Deliverable gleichzeitig mit einem anderen im selben Team gearbeitet wird, was durch einen gestreiften Fortschrittsbalken angezeigt wird. Schlie\u00dflich kannst du auch auf die Abk\u00fcrzung des Teams klicken, um zur oben erw\u00e4hnten Ansicht Teams zu gelangen.\n\n\nZus\u00e4tzliche Navigation\nDer Progress Tracker zeigt mehr als 500 Aufgaben in mehr als 50 Teams an. Es ist kein Geheimnis, dass ein so gro\u00dfer Datensatz \u00fcberw\u00e4ltigend sein kann. Deshalb war es f\u00fcr uns wichtig, dir Werkzeuge an die Hand zu geben, mit denen du dich in den dargestellten Informationen leicht zurechtfindest. Das Wichtigste ist, dass du in der Ansicht \"Leistungen\" mit der Suchleiste eine bestimmte Leistung anhand eines oder zweier Schl\u00fcsselw\u00f6rter finden kannst. Sowohl die Namen als auch die Beschreibungen der Leistungen sind indiziert, sodass du auch dann nach etwas suchen kannst, wenn du nicht genau wei\u00dft, wie es hei\u00dft.\n\nAu\u00dferdem kannst du mit den Filtern auf der rechten Seite der Roadmap die Deliverables nach Projekt (Star Citizen, Squadron 42 oder beides) und nach den Kategorien der Release-Ansicht sortieren.\n\nRelease-Ansicht\nDer zweite Abschnitt der Roadmap ist die Release-Ansicht. Das persistente Universum von Star Citizen wird viertelj\u00e4hrlich aktualisiert und die Release-Ansicht zeigt die geplanten Features f\u00fcr das n\u00e4chste Update des persistenten Universums. Diese Karten repr\u00e4sentieren ein hohes Ma\u00df an Vertrauen in den Ver\u00f6ffentlichungszeitpunkt, allerdings k\u00f6nnen sich diese Features noch verschieben, wenn unvorhergesehene Umst\u00e4nde eintreten oder sich die Priorit\u00e4ten \u00e4ndern.\n\n\nRelease-Fenster\n\nFeature-Karten\n\nRelease-Fenster\nDie in der Versionsansicht angezeigten Spalten stellen die Versionsfenster f\u00fcr die jeweiligen Quartale dar und sind mit einer Patch-Nummer beschriftet. Oben in der Spalte wird der Gesamtstatus des Releases angezeigt, zusammen mit dem geplanten Zeitpunkt f\u00fcr den Beginn des Patch-Zyklus.\n\nJede Spalte steht f\u00fcr den gesamten Zyklus, d.h. sowohl f\u00fcr die Erstver\u00f6ffentlichung als auch f\u00fcr alle Folgepatches. Zum Beispiel wurde die Alpha 3.15.0 am 10. November 2021 ver\u00f6ffentlicht, aber ein paar Wochen sp\u00e4ter kam das Update 3.15.1 heraus, das neue Schiffe und Inhalte enth\u00e4lt. All dies wird in der Spalte 3.15 in der Versionsansicht angezeigt.\n\n\nFeature-Karten\nAlle f\u00fcr die Ver\u00f6ffentlichung geplanten Features werden in der Versionsansicht durch \"Karten\" dargestellt, die in folgende Kategorien unterteilt sind: Orte, KI, Charaktere, Gameplay, Schiffe und Fahrzeuge, Waffen und Gegenst\u00e4nde und Core Tech.\n\nJede dieser Karten zeigt eine Beschreibung des Features, ein Bild und Links zu den entsprechenden Progress Tracker-Beitr\u00e4gen. \u00dcber dem Feature siehst du den aktuellen Status: \"Tentative\", \"Committed\" oder \"Released\", der durch den Status der abschlie\u00dfenden Pr\u00fcfungen bestimmt wird.","zh_CN":"Public Roadmap Companion\nThe Star Citizen and Squadron 42 Public Roadmap is designed to give you an unprecedented look into the game development process by following every feature being worked on by our 50+ development teams, from their initial implementation to their release.\n\nStar Citizen and Squadron 42 are massive projects with lots to track, and this companion guide will help you read and navigate the Roadmap for both projects, as well as provide additional insight into the processes behind it.\n\nUpstream and Downstream\nThe Difference Between\nThroughout our development communications, you have likely seen us reference a team as being designated \"Upstream\" or \"Downstream\", which carries an important meaning. Upstream teams begin work on any given feature at the beginning of its process. They typically handle things like art, vehicles, locations, and gameplay features. These teams set the major tentpole deliverables for the rest of Star Citizen and Squadron 42, and as such, they're able to plan up to four quarters in advance, which is displayed in the Progress Tracker.\n\nDownstream teams are reactive and support the upstream teams, so they depend on the upstream teams scheduling and progress to determine their own work and priorities. Because of this, they're only able to plan for the upcoming quarter, rather than a full year.\n\nExample: The Vehicle Teams (Upstream) begin work planning a newly concepted ship, the Aurora. The Vehicle Content Teams then schedule out production of the Aurora, from a design, art, and animation standpoint. Once the ship is nearly built and the design is close to final, the downstream teams jump in and begin adding details like VFX, Audio, and UI. The important takeaway is that the downstream team relies on information from the upstream team in order to produce a schedule\/plan.\n\nThe Final Review Process\nFeature Cards are added to the Release View near the start of the quarter, once they've been completed for release and the QA process begins. These new cards will always show up on the Roadmap marked as Tentative, meaning the goal is to release in the next quarterly patch, but the feature has yet to pass its Final Review.\n\nEvery quarter, development Directors come together to review features approaching completion in an effort to evaluate if said feature is ready to be released to the live game. If a feature passes its Final Review, then it is integrated into the live release candidate and marked as Committed on the Roadmap. At this point, it is nearly certain that the feature will arrive with its corresponding update. Once the feature has been released to the Live servers, its status is then updated to Released.\n\nUpstream Teams\nActor Feature Team\n\nEU Landing Zone 1\n\nEU Landing Zone 2\n\nEU PU Gameplay Feature Team\n\nEU Sandbox 1\n\nEU Sandbox 2\n\nGame Services Team\n\nLive Tools Team\n\nMission Feature Team\n\nMTL Sandbox 1\n\nSystemic Services and Tools Team\n\nUS PU Gameplay Feature Team\n\nVehicle Feature Team\n\nVehicle Content Team - EU\n\nVehicle Content Team - US\n\nVehicle Content Team - MTL\n\nWeapon Feature Team\n\nDownstream Teams\nAI Content Team\n\nAI Tech and Feature Team\n\nArena Commander Feature Team\n\nAudio\n\nCharacter Tech Art\n\nCinematics Team\n\nEditor Team\n\nEngine Team\n\nFacial Animation\n\nGameplay Story\n\nGraphics Team\n\nInteractables Team\n\nLocation Concept Art\n\nLighting Team\n\nMotion Capture Team\n\nNarrative\n\nNetwork Team\n\nPersistent Tech Team\n\nPhysics Team\n\nPlanet Tech Team\n\nStar Citizen Character Art\n\nSquadron 42 Character Art\n\nSquadron 42 Art\n\nSquadron 42 Feature Team\n\nSquadron 42 Level Design 1 - FPS\n\nSquadron 42 Level Design 2 - Flight\n\nSquadron 42 Level Design 3 - Social\n\nSquadron 42 UI Feature Team\n\nTech Animation Team\n\nTools Team\n\nUI Tech Team\n\nVehicle Concept Art\n\nVFX Team\n\nWeapon Content Team\n\nYou'll also find additional teams displayed on Progress Tracker with scheduling data ending in the past completely. These are deprecated teams that have either been renamed, restructured, or combined with other teams.\nLast Updated: June 14, 2023\nProgress TrackerThe cornerstone of the Roadmap is the Progress Tracker view, which is the default view when you visit the Roadmap. The Progress Tracker pulls back the curtains for all teams, showing you what each team is working on this quarter and what their priorities are after completing the deliverable at hand.\n\nThis view presents a comprehensive look at features, art, and technology scheduled for production within the next four quarters. Keep in mind that this isn\u2019t necessarily when these items will be completed, simply when the work on them is scheduled to finish out by that team specifically.\n\nBelow is a breakdown of the information displayed in the Progress Tracker view and how to navigate it.\n\nWhat is a Deliverable?A deliverable in the Progress Tracker view is a 1:1 representation of a group of tasks scheduled for work in a particular time period. This can be just about anything, a ship or location, an AI behavior, or even a piece of core technology. Shown to the right is a list of deliverables for the Actor Feature Team.\n\nA deliverable will house all work scheduled to be worked on for that specific deliverable, including varied disciplines. For example, if you clicked on the \"Drake Vulture\", it would display work being done by numerous teams such as concept art, audio, etc.\n\nAll in the DetailsYou can sort between two major views when browsing the Progress tracker. First, you can sort by teams, which allows you to browse any work being completed by a specific development team. Alternatively, you can sort by Deliverable, which allows you to browse any\/all teams working on a specific deliverable. This multi-path approach is meant to give you the tools you need to follow along with development in great detail.\n\nExpanding a Deliverable, as shown in the image to the left, gives you further insight into what teams are working on a feature, and for how long. Here you can also see if a Deliverable is being worked on simultaneously with another on the same team, signified by a striped progress bar. Finally, you can also click on the team's abbreviation to navigate to the Teams view mentioned above.\n\nAdditional NavigationThe Progress Tracker reveals 500+ deliverables across 50+ teams. It's no secret that such a large dataset can be overwhelming, which is why it was a priority for us to provide you with tools to easily navigate the presented information. Most importantly, while in the Deliverables view, the search bar can help you find a specific deliverable based on a key word or two. Both the deliverable names and descriptions are indexed, so you're able to search for something even if you don't know exactly what it's called.\n\nAdditionally, the filters on the right side of the Roadmap allow you to sort deliverables by project (Star Citizen, Squadron 42, or both), as well as their Release View categories.\n\nRelease ViewThe second section of the Roadmap is the Release View. The Persistent Universe of Star Citizen receives updates on a quarterly basis, and the Release View's intent is to show the planned features for the next quarter's Persistent Universe update. These cards represent a high level of confidence in their release timing, however these features may still move depending on unforeseen circumstances or a change in priority.\n\nRelease WindowsThe columns displayed on Release View represent release windows for their respective quarters, labeled with a patch number. The column displays the overall status of the release at the top, along with the intended timing of the start of the patch cycle.\n\nEach column represents the entire cycle, both the initial release as well as any incremental follow up patches. For example, Alpha 3.15.0 released on November 10, 2021, but a follow up 3.15.1 update was released a few weeks later that added new ships and content. All of this is represented together under the 3.15 column on Release View.\n\nFeature CardsAll features scheduled for release are represented by \"cards\" on Release View, sorted into these categories: Locations, AI, Characters, Gameplay, Ships and Vehicles, Weapons and Items, and Core Tech.\n\nEach of these cards displays a description of the feature, an image, and links to the corresponding Progress Tracker deliverable. Above the feature you can see its current status of Tentative, Committed, or Released, which is determined by the status of its final reviews."},"links_count":0,"comment_count":0,"created_at":"2022-02-16T22:00:00+00:00","created_at_human":"4 years ago"},"meta":{"processed_at":"2026-05-13 20:55:13","valid_relations":["images","links"],"prev_id":18531,"next_id":18533}}