people get too complacent with games and media in general. its not whining if your disappointed. devs should strive to be the best and if no one is speaking up then why the ♥♥♥♥ should they care if they deliver a sub-par experience. i am really dissapoint

~2 years. Not enough time for Data to make an addition to a game.

~2 years. For any other dev, time to make 2-3 games of decent quality.

Today I'm going to write a devlog entry about why the metagame wasn't shipped as playable in this build, but the short story is that the skirmish/scenario mode and menus ended up being so broken from all the fundamental changes in the engine (4 teams instead of 2, etc) that I had to go redo it completely from scratch, or there wouldn't have been a way to start ANY game in the build by now, and then you'd actually have a reason to be pissed

Stay tuned to the devlog.. the DRL site should be more responsive today since we diverted the humble traffic away from our poor feeble server..
- D

Also, sorry to hear some people are disappointed. However, while I do strive to make the best game I can, I'm sure it's abundantly clear that I do not strive to make it as fast as I can. Game development isn't 100% of my life, and so from time to time it gets put on the back burner when other things interest me more. This is why I am an independent developer: to have the freedom to work on what I want, when I want, how I want to, and however intensely I want to.

I am sorry to have not been able to deliver a metagame when and in the build number I had hoped, but like I will describe in the coming devlog post today, there was good reason not to ship a half-baked version, along with a completely broken skirmish mode.. it would have been a true disappointment and waste of your time to download and try to play.

- D

It's okay, though some stuff like isscrap and Lua on attachables would be extremely appreciated. *HINT*

IsScrap, Lua on attachables, and velocity inheritance for emissions will buy you a good six months of community love, if not more.
I think I speak for a fairly large portion of DRL when I say that.

Custom wounds would be great too.

This would releate strongly to the attachable Lua. We already have AttachEmitter() or so in Lua, but it causes crashy havok instead of, say, attaching an AEmitter.

Invalid MO crashes should be avoided by engine code. Executing Lua code in Removed() or gibbing a dreadnought wrong can result in a memory violation.

Quit hating, all of you. C'mon, give the guy some slack. This started out as a little project, and this isn't his entire life. I believe that the content fully makes a new build, who cares if it's not what he might have said he wanted. Plans change. You think Data wants to make a game that sucks? No, it takes time. I couldn't care if it takes 5 years. I'm more worried about the end product than how long it gets here. I'd rather a great game that took a while than one quickly pumped out that sucks.

I think the major consensus is that while he is an Indie developer, he needs to at least give us some clue as to what he's doing every once in a while, which he's just done. If he did that every, I dunno, month or so, then there wouldn't be as much of a problem.

Also, for the record, Cortex has been in development for more than 7 years now, on and off.

Implying Dan does enough month to month with Cortex Command to generate enough content for a dev log.
Hey Dan this just in your excuses are stupid. You have been working for a year and nine months. A year and nine months. Even if you spent like two hours every weekend you should have at least a working campaign, or some not buggy and slow as ♥♥♥♥ lazy code. Quit acting like you're justified in what you've done and just come out and say "I've been a lazy ♥♥♥♥, my bad." and fix it. We're the reason you can afford to make your own schedule. You've chosen to completely ignore us and work on almost anything but CC for the past year and nine months.

How can he possibly have not had enough time to implement these changes before the deadline?
It's been EIGHTEEN MONTHS or more.

No sh*t.

And it wouldn't even be that much of a problem, if you'd update your devlog once in a while. Once a week would be perfectly doable.
At least people would have known what progress to expect (if any).
But shoving a mediocre B24 in our faces like this, after eighteen months of silence... Mind boggling.

Nobody expects you to be like Notch, but you're like the complete opposite of him. Not good.
<- me

Once every three weeks is sufficient enough.

Or once every month..

Considering his pace, going once a week won't give him anything to talk about.

I have to say, this is the first time in a while since he's directly responded quickly to community concerns. Hope? I'd think so, but after the last one, I dunno.

I'm dissapointed, but now that he's come out and said the engine got a major overhaul, I'm okay with what few changes there are. It's just so hard to tell how much work he's done when there's so little front-end stuff done.

Also, I find it interesting how we talk about data as an absent third party, not directly, because we're under no false impressions that he's actively listening.

I'll still be playing cortex command for a while. It's a damn fun game. That won't change because of B24.