Template:Alpha-1 testing

The term "alpha" is a tricky one, and it typically has 2 meanings in gaming. The development meaning for alpha is a point in the process where we are ready to test the fundamental systems in their core form, without polish and without much of the content. Then, there is the external or "marketing" term for alpha. This is typically applied to Eastern-ported MMORPGs, when in fact that is a completed game being localized for a region, and not really indicative of a true development alpha. As you may know by now, game development has many stages - from the initial tech demos to the pre-production and pre-alpha states, then on to the alphas and betas and eventually launch. – Steven Sharif

I want to make emphatically clear, our alphas and betas are true development alphas and betas, and some have said I am crazy to allow these phases to be seen without an NDA…maybe I am crazy? lol… But I am trusting the community of gamers out there to get a glimpse into the process, and understand the long road ahead for what will eventually be worth the wait. Given time and talent, amazing things can happen, so make sure you help us in communicating that we are in open development which means people get to see the bare bones before the meat. And look, I know people see our 4K footage and say, "This looks better than most released games!", but trust me when I say, you ain't seen nothin’ yet. – Steven Sharif

Phase	Release	Estimated/Actual date
Alpha-1	Alpha-1 early preview livestream.	March 27, 2020.
	Alpha-1 limited QA testing (NDA).	May 28, 2020.
	Alpha-1 preview pre-test 1 (NDA).	Dec 18 - Dec 21 2020.
	Alpha-1 preview pre-test 2 (NDA).	Feb 19 - Feb 22 2021.
	Alpha-1 preview intermittent spot testing (NDA).	Mar 19 - Jul 9 2021.
	Alpha-1 preview weekend (no NDA).	July 9 - July 11 2021.
	Alpha-1 (no NDA).	July 14 - August 15 2021.

Read more...

Over the last month, several new developments both internally and externally have led me to err on the side of caution and postpone the NDA release and Alpha One dates to July. If it had only been any one of these issues, we would have powered through it. – Steven Sharif

First, with the inclusion of siege systems and the combat backend revamp, our internal code-lock dates slipped a bit and ate into our QA and optimization timelines. While our feature timelines typically include a 30% padding to account for unknowns, I knew including this for our testing would be cutting it close. I made the call to take this risk due to its benefit for the overall testing period. The siege systems now being in place are still going through bug testing before they are ready for primetime. Oftentimes the bug fixing (QA period) can really tighten things up pretty quickly, so I gave it until the end of this weekend to evaluate. Suffice to say, these systems could benefit from another week or two of testing and bug fixing before being ready to include in Alpha One. – Steven Sharif

Second, our timeline for the move back to the studio has been accelerated, and this would have put our move-in dates in the middle of the June test window. That would have been a difficult task to juggle for the team, yet we were prepared to do so, and had plans in place for how to accomplish this. However, given the other factors of the delay equation, it made more sense to get the move out of the way first and allow our teams to be in the studio together during the testing period. – Steven Sharif

Finally, several new expansion launches for other live games were announced that would have coincided with our test starting June 1st. We estimate roughly 25% of our current testing pool are active players across these titles combined. This fact presents us with forcing our testers to choose between participating in our testing environment (which will be a long and arduous responsibility), or playing an expansion with their friends in other popular titles. As I outlined earlier, this testing period is an important one. It will require not only participation, but also the attention and feedback from both our testing audience and the broader Ashes of Creation community and general public. – Steven Sharif

Coupled with the above facts, media coverage and content creators would have been asked to cover either Alpha One for Ashes of Creation, or the other live launches on June 1st. While the primary purpose of this testing and NDA release is to collect data, gather feedback, and test systems, it is also an opportunity to grow our community, building on the already millions of people who are following our development and participating in the success of the project. – Steven Sharif

So, with the above information, I’ve made the decision to position our Alpha One presentation and testing period in the month of July, instead of June. If you are already a member of the Alpha One testing group, you will still be testing on May 14, but this testing will remain under NDA. Additionally, during the month of June there will be spot/stress testing that you will have an opportunity to participate in. Also, given the delay in our testing schedule, I will be extending our refund policy from 30 days to 90 days going forward for all pre-orders retroactive from May 5, 2021, out of respect to those who purchased anticipating the NDA release for this month. – Steven Sharif

As usual, we will continue to showcase in-game footage during our live streams this month and next. With the launch of our Content Creator Program, this will also provide some additional time for those of you who are interested in creating content around Ashes of Creation to prepare. – Steven Sharif

Again, announcing a delay is not the highlight of my week, but it is my responsibility to protect the project and position ourselves for success. While I will take this on the chin for the next few weeks, if it means a better Alpha One presentation with more time for QA, a smoother studio move, and better participation and coverage overall for the test, then I think it’s the right call. Hope you agree. – Steven Sharif