I don't care which month, I wanna know which build dev's got... I have a bet to win!I was able to say it definitely wouldn't happen in September.I was able to say it definitely wouldn't happen in October.
I can't say it definitely won't happen in November...
Fanatics incoming in 3.. 2.. 1..@staff a cry of desperation.Guys, out of sheer curiosity: what's the problem with making a feature-freeze, fix bugs and just release what is there already? Half a year ago we were promised a feature-freeze, bug fix, and release, yet you keep adding, and adding, and adding, and adding, and changing stuff, over and over and over... This seems endless. It's like you don't even care about releasing alpha17 for people anymore - just about adding features to hone your feeling of self-importance.
Why you don't do smaller milestones, smaller chunks with short iterations instead? Just look at your own diary!
"Added gyrocopter". Well then release it! You can fix bugs later if you find any, it's an ALPHA, not even beta, for gods sake!
"New water". What's the problem with releasing that feature exclusively, before starting on AI and Pathfinding?
How "New oak tree" is dependent on "new Unity lighting"?
Who in the world cares about beer dispenser textures when we can't even take a look at that gdamn oak tree??
Guys, do you even care about your community? Bugs now, new stuff later. Is that so hard to grasp? But most important, you have to work on your process. If you are unable to deliver nightly or at least weekly unstable builds, then there's something very wrong with your development process.
It seems that my return always coincides with stuff like this...Why you don't do smaller milestones, smaller chunks with short iterations instead? Just look at your own diary!"Added gyrocopter". Well then release it! You can fix bugs later if you find any, it's an ALPHA, not even beta, for gods sake!
Guys, do you even care about your community? Bugs now, new stuff later. Is that so hard to grasp?
@staff a cry of desperation.Guys, out of sheer curiosity: what's the problem with making a feature-freeze, fix bugs and just release what is there already? Half a year ago we were promised a feature-freeze, bug fix, and release, yet you keep adding, and adding, and adding, and adding, and changing stuff, over and over and over... This seems endless. It's like you don't even care about releasing alpha17 for people anymore - just about adding features to hone your feeling of self-importance.
Why you don't do smaller milestones, smaller chunks with short iterations instead? Just look at your own diary!
"Added gyrocopter". Well then release it! You can fix bugs later if you find any, it's an ALPHA, not even beta, for gods sake!
"New water". What's the problem with releasing that feature exclusively, before starting on AI and Pathfinding?
How "New oak tree" is dependent on "new Unity lighting"?
Who in the world cares about beer dispenser textures when we can't even take a look at that gdamn oak tree??
Guys, do you even care about your community? Bugs now, new stuff later. Is that so hard to grasp? But most important, you have to work on your process. If you are unable to deliver nightly or at least weekly unstable builds, then there's something very wrong with your development process.
175 to date. So... Every 2 days or so?Keep in mind, just because they don't make their daily/weekly builds public, doesn't mean that they don't do them.
I'm not agreeing or disagreeing with your comments - just saying there may be more than meets the consumers eye...
-A
Or, more likely, people that understand what phrases like "feature freeze" and "early access" actually mean.Fanatics incoming in 3.. 2.. 1..