FAQ



Is this Pro or Anti SC?

No. The idea is to present facts to let everyone make up their own minds and draw their own conclusions, it doesn't matter to use if you end up liking or hating StarCitizen we just want people to do so in an informed manner.

Who maintains this?

The community, we aim to keep every change or submission open and transparent. To do that we adopt open source methodologies, chages are submitted per issues discussed in the open and then included via merge requests.


Definitions

Expectation:

Anything said or written that could reasonably be seen as a confirmed.

Examples

"We've already announced that we're gonna be supporting TrackIR, so that's definitely on our list."

Expected Slam dunk, officially saying a feature will be included.

"I think we'd let people design their own costumes for their characters."

Expected Did not explicitly say it would be included, yet the expectation was set that they would let players do [x].

"The idea is you'll start in the hangar and then you'll equip your ship, and you can even chat with friends and organizations in the hangar, say 'Hey all, let's get into a battle.'"

Expected Sets the expectation by telling the customer to imagine it working this way in the final product. Slam dunk in our opinion but doesn't adhere to a strict interpretation of a promise.

"Our plan is that we're gonna have regular content updates, maybe not weekly, but hopefully at least bi-monthly, as we go, but then we'll also have some much bigger content updates which would be, say another single player campaign like Squadron 42, or the ability to play one of the alien races."

Expected In a way can be seen as confirmed but should needs to be treated carefully when it comes to the details.

"So we haven't really thought it out. [...] I'm not quite sure about that, but probably the likelihood is support for iOS and Android."

For DiscussionSome context is required for this, so it will be discussed in the related issue before a decision is made.

"We're also, I think it would be interesting to explore it on a multiple monitor situation. Although when I've talked about this, to be sure, this won't be functional in the dogfighting, and it's a longer term goal for the game."

Not Promised This talks about exploring a feature, not implementing it. The result of this could be that it's not going to be included.

"We've considered it, we're not 100% sure about doing it, though the system supports it as each thruster is physically modelled correctly and supplies thrust individually. So, I would say that would be something that we'd consider, as it's not too hard, but no promises."

Not Promised Littered with disclaimers. We don't think anyone would read this and expect it to be included.

Completed:

Fairly self explanatory. Was the promise delivered for the most part? Best is if it is still working or accessible. To be completed the bar to meet is 'completed in spirit' not 'completed by the letter'.

For something to be considered completed it will require strong evidence. Being accessible in the current version of the game is one of those, for non game items actual fulfilment (i.e. if a video was promised and is delivred) is another.

Given that Star Citizen is still in alpha this category will remain fairly empty, the 'in alpha' category is going to be more prominent as it will covere partially finished tasks that are available today

Compromised:

Delivered in some form varries significnatly from the original goal. Items can't fairly be considered fully complete but neither broken.

In alpha:

Best is if customers can currently access it. Features that are starting to work in the alpha version. Things that appear on AtV or promo videos do not necessarily qualify and are left to editor discretion. In addition, StarCitizen Tracker takes a skeptical stance towards internal builds because without interacting with the feature for ourself, we do not know for sure if something is pre-rendered or otherwise staged in a non-game tool.

We are seeing some promises disputed because there is a 3D model for some aspect of a feature. We will not be labeling all NPC promises In alpha just because there is an asset for them. In that respect, a feature should be at least 25% complete and testable in the alpha for it to be considered.

Not implemented:

This is the default. Submit sources if there are grounds to suggest otherwise. Features that appear in trailers, promotion material, and the RSI website that are otherwise not yet implemented in the downloadable game.

Stagnant:

We attach a date to every item, if more than a 3 years have passed without testable progress, the expectation will automatically be labeled ‘Stagnant’

Broken:

Items that are clearly not happening despite being promised.

As with Completed this will require hard evidence to support, a official claim "it is not going to happen" would be one of them.

Again as Star Citizen is still in development this category will be fairly empty as most items that can't be confiremd to be actively worked on will be in Stagnant.