Alpha and Beta definitions

Does anyone know which definitions FD uses for Alpha and Beta phases respectively?

I found the following interesting statement by Chris Roberts on how he defines the two terms:
* Alpha: Functionality complete, but not content complete
* Beta: Content and functionality complete, but with bugs remaining that the dev team is working on

Chris also alludes to those definitions being "the standard ones".

Has David said anything about the definitions he's using for Alpha and Beta?
 
Last edited:

Jenner

I wish I was English like my hero Tj.
I think FD make their own rules and definitions - which is good.

So do I. :cool:

<crickets>

Just kidding, folks. Man, tough crowd!

Ok, so the Star Citizen discussion thread is that-a-way:
http://forums.frontier.co.uk/showthread.php?goto=newpost&t=20451

Discuss alpha/beta definitions here, but let's not get into a 'which-space-game-is-superior' argument, which invariably happens when Star Citizen or Chris Roberts are mentioned.

Thanks and carry on.
 

Jenner

I wish I was English like my hero Tj.
Fine, so what are the definitions used?

There has been no formal definition given by FD. They say it's an Alpha or Beta...it's an Alpha or Beta to FD. Not sure if that will satisfy, but that's the situation.
 
Does it really matter? A game is in whatever state it is in. Defining it does not make it more or less complete or buggy.

Well I think it matters very much, especially since ED has put such an emphasis on those terms through associated monetary segregation between the two. Alpha much more expensive than premium beta. Premium beta more expensive than general beta.

I for one am interested in understanding what semantic meaning the studio gives to those terms, especially considering the funding model used. Else I wouldn't have asked the question.

If you have no light to shed on the subject, please refrain from posting in this thread.

There has been no formal definition given by FD. They say it's an Alpha or Beta...it's an Alpha or Beta to FD. Not sure if that will satisfy, but that's the situation.

Jenner, thanks for that.
Do you know if anyone from FD is ever looking at these forums?
 
Last edited by a moderator:
Every shop has there own definitions. Really it boils down to this:

Alpha is the first version of the software the development team is willing to let people outside the team see.

Beta is just Alpha with more stuff and a wider audience.
 
Every shop has there own definitions

Exactly, so did the teams I were on in the past. That's why I'd like to understand the meaning FD gives those terms.

Perhaps they're just as broad as you exemplify, perhaps not. Still interested in hearing their view on it though.
 
I think FD make their own rules and definitions - which is good.

Alpha started with partly functional and ended functionally complete in the sense that you had the game arc. So the alpha stage was to make it function complete as per the definition.
In the same vein beta has started where alpha left off and has been adding in more content and bug fixing the functionality in readiness for gamma which will be functionally and content complete as per the definition. Most big bugs should have been eliminated by this point but I can see the unexpected bug or balancing tweak meaning that an extra wipe is needed and gamma 2 to be issued.

The question is, do you think that there will be a beta 3?
 
Personal definitions:

Alpha software is the stuff you get to test but fully expect to not even load up and work at the first go, or else to consist of fragments of code that don't connect to anything else.

Beta software is the stuff you get to test that should look more or less like an actual game, but still expect to be riddled with bugs and otherwise incomplete.
 
Chris's definitions are pretty much what places I worked in use although I find it hard to see how a beta can be content complete. Content can be a broad term I guess.

How "finished" something is is not that easy to define. Is it only finished when everything is implemented and there are zero bugs? I think that is where most of the variance in interpretation comes from.

Going by FD's releases it seems obvious to me that that is their definition too. The base game is functionality complete. There are bugs to fix and more content (missions, ships, etc) to finish but the core game is all there. Addons have their own dev cycle.
 
I seem to recall DB saying that alpha was getting the barebones of gameplay right, beta was successive releases of additional gameplay mechanics and content, and gamma would be feature complete and 'mostly' content complete, with some content coming at release.

All of this excludes the expansions of course.
 
Well I think it matters very much, especially since ED has put such an emphasis on those terms through associated monetary segregation between the two. Alpha much more expensive than premium beta. Premium beta more expensive than general beta.

I for one am interested in understanding what semantic meaning the studio gives to those terms, especially considering the funding model used. Else I wouldn't have asked the question.

If you have no light to shed on the subject, please refrain from posting in this thread.

Your questions can all be answered by looking at the functionality that was in:

a) Alpha, which was released in December 2013
b) Premium Beta, which was released end May 2014
c) Standard Beta, which was released end July 2014.

All three are now simply a matter of history. There is no need for you to solve a Rubik's Cube of semantics, as every aspect of those phases you mentioned are fully documented in past release descriptions.

As far as monetary segregation goes, that is also in the past. Neither "Alpha" nor "Premium Beta" costs have any relevance today.
 

Viajero

Volunteer Moderator
Jenner, thanks for that.
Do you know if anyone from FD is ever looking at these forums?

We know for a fact that they are. Welcome to the forums, I guess.

Well I think it matters very much, especially since ED has put such an emphasis on those terms through associated monetary segregation between the two. Alpha much more expensive than premium beta. Premium beta more expensive than general beta.

I for one am interested in understanding what semantic meaning the studio gives to those terms, especially considering the funding model used. Else I wouldn't have asked the question.

If you have no light to shed on the subject, please refrain from posting in this thread.

Are you a backer or are you in in the current Beta testing phase? I am asking this because the meaning FDEV assigns to each phase would be fully transparent to you from the point of view of the game content you see or have seen for each of the alpha or beta phases. You do not really need a definition given that you get to experience the real thing. What you saw in Alpha is what Alpha meant for FDEV. And what you see now in Beta is what Beta means for FDEV. If you nevertheless want to have a definition though I suggest you refer to each individual package description that was published in the game store and in the forums in each alpha or beta phase.

What was actually delivered is to all effects FDEV's definition as each release was named Alpha or Beta as the case may have been. Other games like SC have not even released an Alpha (CIG is calling the current version of AC a pre alpha) so CR needs to use semantics due to the lack of any official meaningful release in this regard.

If you need to obtain a comparison between ED Alpha and Beta release states so far and the final game you can either await a bit longer for actual release or simply look at the DDA forum which should give you a detailed picture of what will most likely be in the gold version.

Now, having said all that I suspect that what you are really trying to do is to establish the gap between any eventual theoretical definition of Alpha and Beta and what FDEV has actually delivered in order for you to be able to claim that FDEV may have not fulfilled their "contract" if you decide there is a gap.

If that is the case then you ll be probably sorely disappointed:

Firstly, I d hope FDEV is smart enough to avoid putting themselves into a completely arbitrary semantics discussion that adds no value whatsoever to them. Much less if said discussion is proposed so to be able to open up a certain degree of liability towards FDEV in any way or form.

Second, the only thing you are paying for when you pledged for alpha and beta is for the opportunity to test. If you look at the terms and conditions or EULA of any of the alpha or beta packages you ll probably realize there is no guarantee wether implicit or explicit of the content and features for each phase. Are you in Beta? Did you read the Terms & Conditions / EULA?
 
Last edited by a moderator:
For me this is clearly an Alpha.
Its only called Beta since they opened it up to a wider range of people.
They needed to point it out in a name. Alpha 1 2 3, Premium Alpha, Public Alpha...
sounds confusing and most people don't know what an alpha is,
but had heard from betas, as almost every google service etc. is an beta.

But since there is a lot of content missing that is planed for release,
and there are placeholders and a lot work in progress here,
this is an Alpha. A Beta is a feature complete program to be tested for
finding bugs and do some fixing, tweaking and balancing in it.

But its really doesn't matter what the naming is, as long as there is progress. ;)
 
Since beta software is a pre-release version of the final application, it may be unstable or lack features that will be be included in the final release. Therefore, beta software often comes with a disclaimer that testers should use the software at their own risk. If you choose to beta test a program, be aware that it may not function as expected.

they needed to make this disclaimer with 20 confirmation click screens, so all would understand that this is BETA now :)
 
since there is a lot of content missing that is planed for release, and there are placeholders and a lot work in progress here, this is an Alpha.

The latter part of the the cited text was really what spurred me to open this thread. I've read in countless other threads a lot of harsh and unfriendly put-downs by people saying more or less the same thing; Paraphrased "Yeah, <thing> is [entirely] missing, but this is BETA, so wad'ya expect?".

To me those statements made absolutely no sense, since I'm coming from a world where Beta means that all significant functionality and mechanisms are in place and the time left before release is just bug hunting and polish.

When reading this forum I got the sense that the message from a lot of members pretty much was:
Don't ask, highlight or question the absence of anything, nor question any aspect of the implementation, because by magic and divine intuition, FD will take care of all those things [in the few hours remaining in the Beta]

Now, if we're really in a phase some [you, me and others] are normally calling an Alpha, then there's still a lot of hope. If otoh. FD was to go by the "standard" definition, then it'd be a good time for backers to start panicking ;)

Since beta software is a pre-release version of the final application, it may be unstable or lack features that will be be included in the final release. Therefore, beta software often comes with a disclaimer that testers should use the software at their own risk. If you choose to beta test a program, be aware that it may not function as expected.

Thanks for that quote. That really clears things up for me and indeed that characterization of Beta is what all places I've worked at attribute to an Alpha.

I've heard the term Gamma also thrown around as well, so currently I'm interpreting that [next] phase to be what an ordinary Beta normally is. If you have a source that contradicts that interpretation, feel free to correct me, so I can enter the next round of testing with the proper expectations.
 
Back
Top Bottom