RSI published a Comm-Link titled “This Week in Star Citizen – September 28, 2026,” giving players a dated place to review that week’s announcements. [1] If you’re catching up, start with that post rather than trying to piece together the week from scattered chatter. It also helps to read This Week in Star Citizen: September 21, 2027.
The title identifies the weekly post, but the result available here does not show its individual announcements. [1] So, for example, don’t assume it announced a new ship, a patch, or a gameplay change based on the title alone. Check the post itself for the details before treating any specific item as confirmed.
That’s useful if you missed the update when it appeared or are returning to Star Citizen after time away. The dated entry gives you a clear starting point; once you have the post open, you can focus on the parts relevant to your next session, such as news about a feature you follow or an event you planned to join. The title alone, however, isn’t enough to tell you which of those topics the post covered. [1]
What the weekly post confirms
Treat the dated post title as confirmation of the post’s existence, not as evidence of specific game changes. The available entry identifies “This Week in Star Citizen – September 28, 2026,” but gives no itemized announcements to assess. [1]
What you can confirm
You can confirm that the entry is presented as a weekly Star Citizen post and includes the invitation to catch up on activity in the ‘verse. [1] That does not tell you which ships, missions, systems, or development work—if any—the post discusses, so don’t turn those topics into reported updates.
For example, a claim that a ship received a balance change would need an explicit statement in the announcement. The same goes for a new mission, a release window, or a feature arriving in a particular game version. Without those details in the entry, label them as unverified rather than repeating them as confirmed news.
Keep discussion separate from updates
If you see players predicting what the weekly post might cover, treat those predictions as community discussion, not as announcements. A comment such as “this probably means a new ship is coming” is not confirmation; look for clear wording in the post before presenting it as a game update.
When you review the full announcement, separate its explicit statements from your own interpretation. For instance, report a named change as confirmed only if the post actually names it, and describe a possible implication as your analysis rather than a developer commitment. In this case, the listed entry supplies no itemized details to summarize, so avoid filling the gap with guesses. [1]
How Pirate Week fits the date
Pirate Week’s reported end date gives September 28 event context, but it does not show what the weekly post covered. [2][3]
A report about Pirate Week 2026 says the event ran through September 28, while another says that was the end date for the whole event. [2][3] That makes the date relevant to players checking the week’s news, but it is not enough to conclude that the weekly post discussed Pirate Week, its rewards, or its activities.
Keep the distinction clear when you read a dated update: an event happening around the same time is not proof that it appeared in the post. For example, seeing September 28 attached to both a weekly post and an event does not confirm that the post described a treasure hunt or a competition. The available event reporting also gives a separate deadline for Most Wanted contest submissions, so do not treat that deadline as evidence of the weekly post’s contents. [4]
If you are deciding whether you still have time to participate, check official announcements for the current event schedule and any remaining activity details. Use the date as a prompt to verify, not as a substitute for checking which activities are open or what the announcement says.
Where to check the full announcement
For the complete announcement, open RSI’s Comm-Link entry titled “This Week in Star Citizen – September 28, 2026.” [1] Use the dated post itself rather than trying to reconstruct its contents from a headline or from posts published in other weeks.
Check for later updates
Before you act on a detail from the post, check RSI’s current official announcements for any later clarification or change. For example, if you are planning around a feature or event mentioned in the entry, make sure a newer official post has not revised what players should expect. Treat a later announcement as an update, not as proof that the original post said something it did not.
Keep earlier weekly posts separate
Do not fill gaps in the September 28 entry by borrowing details from an earlier weekly roundup. A feature, event, or plan discussed in another week is not automatically part of this announcement. If the full post does not spell out a detail, leave it unconfirmed rather than carrying it over from a previous post.
This approach is especially useful when you are comparing weekly news: keep the dated announcement open, check for newer official notices, and avoid mixing details across weeks. That way, you can share what the September 28 post actually contains without presenting older information as part of it.
What to take away from this week’s post
The key takeaway is to treat the dated RSI Comm-Link as the reference point for this week’s Star Citizen news, and to stick to what its post actually confirms. The available post text identifies it as “This Week in Star Citizen – September 28, 2026” and describes it as a place to see what is happening in and out of the ‘verse. [1]
For your next step, open the full dated post and check its wording before repeating any announcement in chat or planning around it. For example, if a player asks whether the post confirms a gameplay change, look for that specific change in the post rather than assuming it is covered. The text available here does not spell out individual announcements, so avoid adding details that you cannot verify in the full post.