grifftron wrote:Ye... I believe the community itself is what killed the foundry.
When people lose interest, it gets pretty dry. I don't see how you can blame admin for this. Do you want them to spend time making big, time consuming changes just to see that the community still doesn't give a...
No, I'd rather see them make small, incremental changes that don't take much time, and announce them (and other foundry news) to the general population.
I disagree with those who think the community killed the foundry. Back when there was activity here, there were fairly regular updates to the mapmaking capabilities and/or play modes. The latest ones that I'm aware of - Transformations and Scenarios were poorly conceived and implemented, and didn't seem to generate much interest. There are many more basic capabilities that should have been implemented first, but these ideas have been ignored.
One example is Conditional Bombardments*. It should have been a trivial addition to the XML. In the
suggestions thread about it, it was said to have been submitted for implementation almost 4 years ago. Where the hell is it? You can't blame the community for leaving when their requests have been ignored by the site for so long. People get tired of using the same tools over and over. Mapmakers asked for some minor upgrades, but instead got some overly complicated pet projects that didn't help anyone create any more maps.
Another issue is that many people say the site has too many maps already. I don't think it has too many maps any more than Amazon has too many products. The problem is the crappy map browser. There is no way to sort or filter the maps to find new ones that appeal to you, or an evaluation system so people can say what they do and don't like about a map. Your only choice is to page through all 253. If you had to do that to find something you wanted on Amazon, no one would go there either. This is also something that the community can do nothing about. Yes, I realize that this is a much bigger project, but where is the incentive for someone to make a new map, when it will only be thrown onto the pile with everything else, with no easy way for players to find it.
The real change has to start at the top. When the site shows that it wants more maps with something more than just lip service, maybe then the community will respond - or maybe it's already too late.
* Actually, the first thing that should be implemented is an
XML versioning system to avoid breaking old maps when new features are added.