We are all waiting for the Alpha 8 release which refers to the Alpha testing. If you want an Alpha invite, ask around and eventually someone will probably toss one at you.
EE won't be online for another 2 weeks'ish.
I just paid for Early enrollment and I am confused about what is releasing when. Am I going to be able to play on the 25th? or sooner? Is the "Alpha 8" Release referring to just Alpha Testers?
Thanks for your time.
I got you if you wanna play, just PM me your e-mail.
Goblin Squad Member
|
Well I'm new here and nobody knows me but if begging will work:
"PLEASSSSEEEEEE!! invite me to Alpha!! Please!" ::making big sad puppy eyes::
or I could suck it up and wait, but really, is that the right thing to do?
:)
Thanks
Right now I suspect there are more invitations than people asking for them. Beg away!
|
Goblin Squad Member
|
Trying to figure out how to PM you now, will send it as soon as I figure it out. Thanks so muchI got you if you wanna play, just PM me your e-mail.I just paid for Early enrollment and I am confused about what is releasing when. Am I going to be able to play on the 25th? or sooner? Is the "Alpha 8" Release referring to just Alpha Testers?
Thanks for your time.
LOL, I sent you a PM too.
There are probably a huge number of folks that will do it just for the experience. Won't even bother getting trained or weapons or anything. :-)
lol you got my number, man! Then the FFA Pit Fight everyone has been hoping for will start :) They didn't put a spawn point down there, did they?!
|
CEO, Goblinworks
|
| 1 person marked this as a favorite. |
Just got an update from the team. They have made the decision to make some updates and changes which will push the availability of the client into tomorrow. It is unclear exactly when the client will go live but it will likely be sometime early Saturday morning. I expect to get an update first thing tomorrow and I will update the thread with concrete info then.
|
Goblin Squad Member
|
Just got an update from the team. They have made the decision to make some updates and changes which will push the availability of the client into tomorrow. It is unclear exactly when the client will go live but it will likely be sometime early Saturday morning. I expect to get an update first thing tomorrow and I will update the thread with concrete info then.
NO code should be released before its time. Most of us are behind your choices and decisions.
Best is enemy of good enough, but good enough is a slippery slope.
And who does know what the client wants?
|
Goblin Squad Member
|
One delay after another doesn't instill confidence in the team developing the product. Make your releases smaller and more frequent. Sounds like maybe too much was planned/crammed into this release. A full uninstall/re-install should not be required either, which kind of forces your hand on large releases (don't want to make the users re-install often). I hope your processes are improved to make things easier on both the developers and the users.
|
Goblin Squad Member
|
| 1 person marked this as a favorite. |
One delay after another doesn't instill confidence in the team developing the product. Make your releases smaller and more frequent. Sounds like maybe too much was planned/crammed into this release. A full uninstall/re-install should not be required either, which kind of forces your hand on large releases (don't want to make the users re-install often). I hope your processes are improved to make things easier on both the developers and the users.
Proving they can't please everyone. For every voice upset about delay, there's at least one voice saying "Take your time and get it right."
It's software. The best laid flow-chart buckles to programmers working on extraordinarily complex software in separate cubicles and trying to integrate each others' code.
|
Goblin Squad Member
|
| 1 person marked this as a favorite. |
One delay after another doesn't instill confidence in the team developing the product. Make your releases smaller and more frequent. Sounds like maybe too much was planned/crammed into this release. A full uninstall/re-install should not be required either, which kind of forces your hand on large releases (don't want to make the users re-install often). I hope your processes are improved to make things easier on both the developers and the users.Proving they can't please everyone. For every voice upset about delay, there's at least one voice saying "Take your time and get it right."
It's software. The best laid flow-chart buckles to programmers working on extraordinarily complex software in separate cubicles and trying to integrate each others' code.
Actually the moral with software releases is promise about half what you think and promise it a day later than you think it will be ready.
Then if you do get everything in on time you announce "hey look at all these extra goodies we put in for you and we even got the server up early"
|
Goblin Squad Member
|
One delay after another doesn't instill confidence in the team developing the product. Make your releases smaller and more frequent. Sounds like maybe too much was planned/crammed into this release. A full uninstall/re-install should not be required either, which kind of forces your hand on large releases (don't want to make the users re-install often). I hope your processes are improved to make things easier on both the developers and the users.
More likely is that they listened to the players asking them to wait until more stuff is finished before releasing alpha 8 / Early Enrollment.
As to your second point, the self-updating patcher is part of alpha 8, so the uninstall and re-download cycle should be ending.
Goblinworks Executive Founder
|
| 3 people marked this as a favorite. |
Software releases are a messy business. Packages are as unique as snowflakes and there will always be twists and turns that throw the unexpected into the mix. ESPECIALLY when you have this fantastic environment of non-stop open design discussion, back and forth between devs and user community.
So what would you rather have? An open and active dialog with the developers about what may be possible and what we'd like to see, including prioritization, coupled with some messy releases...OR...a non-communicative group of "my way or the highway" developers completely walled off from us?
GW...ya'll are doing great.
Software releases are a messy business. Packages are as unique as snowflakes and there will always be twists and turns that throw the unexpected into the mix. ESPECIALLY when you have this fantastic environment of non-stop open design discussion, back and forth between devs and user community.
So what would you rather have? An open and active dialog with the developers about what may be possible and what we'd like to see, including prioritization, coupled with some messy releases...OR...a non-communicative group of "my way or the highway" developers completely walled off from us?
GW...ya'll are doing great.
I am very happy that we are getting races and more map. I think it's cool that they listen and I am willing to wait. However, I do agree that delays are generally not positive.
It may be normal that there are issues from time to time, but then it's about how you handle the issues. I felt last night that a client wasn't coming out, so I let it go. If people waited here for it, stayed up late and all, that kind of sucks.
I do think they are doing the best they can, but it is generally better to say, very early, "It's not gonna happen right now, we need more time." Than to postpone it and then finally say oops sorry.
|
Goblinworks Executive Founder
|
Software releases are a messy business. Packages are as unique as snowflakes and there will always be twists and turns that throw the unexpected into the mix. ESPECIALLY when you have this fantastic environment of non-stop open design discussion, back and forth between devs and user community.
So what would you rather have? An open and active dialog with the developers about what may be possible and what we'd like to see, including prioritization, coupled with some messy releases...OR...a non-communicative group of "my way or the highway" developers completely walled off from us?
GW...ya'll are doing great.
I am very happy that we are getting races and more map. I think it's cool that they listen and I am willing to wait. However, I do agree that delays are generally not positive.
It may be normal that there are issues from time to time, but then it's about how you handle the issues. I felt last night that a client wasn't coming out, so I let it go. If people waited here for it, stayed up late and all, that kind of sucks.
I do think they are doing the best they can, but it is generally better to say, very early, "It's not gonna happen right now, we need more time." Than to postpone it and then finally say oops sorry.
I understand what you're saying and I agree. I am very eager for the release too, and would be much happier right now actually playing rather than waiting.
But I have no problems with how this has played out. I believe GW deserves more than a little leeway in rolling things out. Weigh the benefits their design/development approach brings to us, their user community, against the added uncertainties, headaches and churn such an approach puts onto their shoulders. We're getting the better end of the bargain.
I know this from personal experience. I'm an application architect for IBM and have been using iterative software design/development (as opposed to waterfall delivery) on my projects for years. It never ceases to amaze me how much pressure it places on the development team and how often this is under-appreciated by the user community.