I'd like to take one quick moment to address this one myself, as I've heard this on more than one occasion and would like to clear up some of the misconceptions about the individual roles on the team.
As a content designer for AO, I worked with vastly different tools and in a vastly different framework than the coders. The truth be told, I don't know the first *thing* about coding. I once made a little password program in GW-BASIC back in the day, but outside of that? I couldn't code my way out of a paper bag. I take a look at the stuff that Macrosun does on a regular basis and it genuinely hurts my head - Same with the stuff that Enno and the other render coders are tackling. This isn't even because of the old "AO code ewww" running gag that's been passed around - It's just that code genuinely goes over my head.
Content designers are hired on vastly different terms and with vastly different requirements from coders. We... don't have to know how to code to do this job. Some knowledge of scripting helps, and it never *hurts* to know coding, but they're not requirements at all. Same with, say, the art team on the project - They're hired because they know how to model and how to use Photoshop - Not because they know C++, nor because they understand game balance.
That said, it isn't that we wouldn't *like* to help out sometimes - I myself have been goofing around in my spare time with particle effect generators, just to see if I can learn how to work with this stuff and potentially offer the engine guys some aid on my spare time (which is unfortunately dwindling these days, but I do what I can). Even though I'm no longer working on AO I still feel a deep, devoted passion to it - One that makes me *want* to help the game along, even if it means taking up my spare time to do it. You mentioned in your earlier post that AO was a game that meant a lot to you, and had influenced your life in fantastic, amazing ways. You're not alone in that, and there are plenty of us here at this office who actually feel the same way - Myself most definitely included.
So it's not that we don't want to help. It's that we're genuinely not qualified. As much amazing talent that exists in the current team, a designer is a designer, an artist is an artist, and a coder is a coder - While some small amount of overlap may exist, usually the people hired are specialized in their specific role, and quite simply just doesn't have the in-depth knowledge to help out that much in other areas. It's like if your mathematics-studying best friend asks you to help them solve a complicated equation for their term grade but you studied woodworking - You could offer to make them a really pretty frame to hang their solution in, but actually solving the equation is beyond your means. That's what it's like, mostly.
Meantime, we still have jobs, and AO still needs content and such to keep people rolling, so instead of us just kinda sitting around and waiting (or worse yet, someone *forcing* us to work on code, in which case literally nothing would get done because we would have zero clue of what we're doing), content gets made. It lets us keep our jobs, it lets you guys get new stuff to play around with in-game, and it keeps us out of the render coders collective hair. Because I can guarantee you that if we aren't kept busy, they start getting tired of us popping over every five minutes to look at the shinies.