It’s a dated announcement, not a complete account of the ship’s development or a promise of when you could fly it.
To keep the timeline useful, each entry should separate what an announcement actually stated from any interpretation or plan attached to it. For example, an announced detail belongs under a confirmed-announcement label; a future intention should be marked as a plan, not treated as a completed event.
This is a focused fact-check of dated statements, rather than the full Javelin development story. As you read, check the date and wording tied to each entry, and keep later claims distinct from what was recorded at the time. That approach helps you see what was publicly stated on a particular date without turning an inference into a confirmed milestone. For the broader sequence of development events, use the Javelin milestones article to place individual announcements in context.
What RSI announced in November 2014
RSI’s November 27, 2014 announcement described the Javelin as designed by David Hobbins and implemented by Foundry 42 for the opening of Squadron 42. [1] Those are the announcement’s specific historical details; they do not, by themselves, establish that the ship was publicly released or available to play at that time.
What the announcement says
The announcement identifies David Hobbins as the Javelin’s designer. [1] It also says the ship “has since been implemented by the team at Foundry 42 for the opening of the Squadron 42 single-player” experience. [1] That wording ties the implementation to the game’s opening, but does not say the Javelin was available to players or provide a final specification sheet.
For example, write “implemented for the opening of Squadron 42,” rather than turning that phrase into a claim about public availability or a completed, playable ship.
This is a useful distinction when you compare historical announcements: a detail about who designed a ship or how it was implemented does not automatically answer when players could access it. Keep this entry focused on what RSI stated on that date, rather than adding a release date, gameplay status, or specifications that the announcement does not give.
Use the Javelin development milestones article to see how this announcement fits alongside other dated events.
Separate confirmed details from plans and claims
Use a clear label for each Javelin statement so you can tell an announcement from a plan or a later status claim. For example, mark an official statement as a “confirmed announcement,” future-facing wording as a “stated plan,” and a later outside listing as a “third-party status claim.” Those labels show what kind of statement you are reading; they do not make a prediction certain.
Separate a plan from a release confirmation
The claim that the Javelin will enter the Persistent Universe after Squadron 42 is a stated plan, not a dated release confirmation. [2] The wording gives an order of events, but it does not provide a calendar date for the ship’s arrival. If you add it to a timeline, place it under “stated plan” rather than treating it as a scheduled launch.
That distinction matters when you compare timelines or repeat a claim in a discussion. “After Squadron 42” describes a sequence, while a release date would identify when the Javelin is expected to become available. Keep the original wording attached to the plan, and avoid turning it into a promise of a particular date.
Keep later status claims in their own category
The production wording about the Javelin being built and tested for in-game implementation comes from a later third-party listing, not an RSI announcement. [3] Label it “later third-party status claim” and attribute it to the listing. Do not combine it with an official announcement as though both statements came from RSI.
A practical timeline entry can name the statement’s source type in the same line: “stated plan,” followed by the Persistent Universe wording, or “third-party status claim,” followed by the production wording. This makes it easier to scan the timeline without blurring future intent, outside reporting, and announcements. For context on how separate Javelin milestones fit into the development story, use the milestone article.
How to read later production status
Fleetyards’ listing, dated April 21, 2026, describes the Javelin as “currently being built and tested for implementation in-game.” [3] That wording gives you a later snapshot of how a third-party ship listing characterized the work; it does not turn the 2014 announcement into a delivery commitment or establish when the ship will be available.
Keep the dates and claims in separate lanes
The RSI announcement says the Javelin had been implemented by Foundry 42 for the opening of Squadron 42. [1] Fleetyards uses present-tense production language in a separate entry dated April 21, 2026. [3] Keeping each statement attached to its own date and publisher helps you avoid blending an announcement about a specific implementation with a later description of production work.
For example, you can write, “Fleetyards described the Javelin as being built and tested for in-game implementation,” and label it a later status claim. [3] Avoid rewriting that as “the Javelin will arrive in-game by [a particular date]”: the listing’s wording does not give a delivery date. [3] It also does not, by itself, prove a definitive current status beyond the dated listing.
When you update a timeline, preserve the wording, date, and publisher of each entry rather than merging them into one continuous promise. That makes it easier to distinguish what was announced at one point from what a later listing reported. For broader context on how individual announcements fit into the development story, use the Javelin milestones article.
What this timeline does not confirm
What you should not infer from the timeline
Treat the timeline as a record of dated statements, not as proof of every detail that later appears on a ship page. For example, the claim that the Javelin will enter the Persistent Universe after Squadron 42 is presented as a future plan; it does not give you a release date. [2]
That distinction matters when you are trying to work out when you can actually fly or encounter the ship in the Persistent Universe. Don’t turn “after Squadron 42” into a calendar year, a patch number, or a promise of immediate availability; the wording supplies none of those details. [2]
The same caution applies to specifications and prices shown in later ship listings. Fleetyards lists measurements, cargo figures, inventory capacity, and a pledge price alongside its implementation-status wording, but those are listing details—not specifications or prices established by RSI’s 2014 announcement. [1][3]
So, if you are comparing ship figures, keep the listing separate from the dated announcement: don’t cite its length or price as something RSI confirmed in 2014. Check the current listing before relying on those figures, and keep the announcement’s confirmed details limited to what it actually states. [1][3]
Use the Javelin development milestones article as your next step if you want broader context. It helps place individual announcements within the development story without turning a plan or a later listing into a dated confirmation.
Use the milestones to place each announcement in context
Keep a dated announcement, a later status claim, and a future plan in separate categories: they describe different things. A dated announcement records what was said at a particular point; a later status claim reports how someone describes the ship afterward; a plan points to an intended future step, not a confirmed release date.
That distinction helps when you compare entries. The dates tell you when those statements were recorded, but the later listing is not itself an RSI announcement or a delivery date. [3]
When you read the timeline, ask what kind of statement each entry makes before treating it as a milestone. A past announcement can establish what was publicly stated then; a later status description can add context without changing the earlier wording; and a plan should remain a plan unless a dated announcement confirms that it happened. This makes it easier to follow the record without turning an intention into a completed event.
For the broader development story, use the Javelin development milestones article next. It can help you place individual announcements alongside the other events in the ship’s development, rather than treating each dated statement as the whole story.