Guidelines are under review, some info can be not totally updated.
Anyway....you don't have to take my words literally....with "your map sucks" i was trying to make clear that maybe have more sharped tongues could be a good thing.
Obviously what i posted is a bit harsh, i don't think I will post something like that in a map thread to discourage someone to continue with a map project, but in the same time I'm pretty sure that I will make clear that if a map should not have a future, then the mapmaker should be well aware of this.
In past, also before your uncle's time here, CAs were able to not support a map and a map was able to reach the live stage anyway with the support of the community. On the opposite, always during the old days, the CAs were able to support a map but have to kill it because the community didn't want it.
That's the right and correct balancing of things.
Today, if CAs do nothing, then nothing will happen. There's too much expectation to those who are supposed to be here to facilitate the foundry process.
As said I have no problem to say to someone to stop with a map project, but i can't force him without the community support (apart if the map has something against the guidelines or it is a big no no for CC). These days if a mapmaker is stubborn and patient enough, he can see its map quenched anyway.
Shape wrote:1. A map should be ‘inherently unique either in gameplay, location, or theme’.
Btw the above rule can be circumvented easily. And follow it ensure only to not have double maps, not to have quality ones.
Shape wrote:But you blue guys/gals do have more responsibility around these parts than the common user, as you (and correct me if I'm wrong) volunteered for a position, so I feel like you guys do have a higher calling, and if no one is willing to say that a map is bad, it should fall to the ones in charge around here. And, too, like the D.C. map, the map should be nipped in the bud before too much is invested in it.
When and if I have to "kill" a map, i try to do into the earlier stage. This exactly to not ask to the mapmaker to put to much effeort into it for nothing. As said the problem is that in most of cases it ends that it's only like "the evil foundry foreman doesn't like my map"....when it's not in this way. If a mapmaker has potential but he is trying to develop a bad map it's my role to go there and tell that to him. I usually act like a father that has to scold one of his children. He doesn't like to do that, but it needs to do that.
Certainly in some cases I can be wrong...I'm not
God and I'm well aware of this...but must be said that it's been a while that I do this "job" and I have seen many maps. I can say I have a bit of knowledge and experience on this type of things.
But now think you are the mapmaker, I (or another CA) posted "bad words" in your map topic...
Nobody else says a word about it.....then now imagine...what could you think?"Nobodies is an idiot, he doesn't like my map, but it's just him so I continue."
I think in most of cases is human to think something like that. Now imagine the same thing, but with the support of the community on a side or on another...in any case it will be clear what the destiny of that map should be.
Now, it's true that rarely CAs take a clear and strong position for a map...but like i said in my previous post, this is because we're easily labelled as tyrant in that case...and i say this because it already happened in more than a single occasion. This is not good because the next time a CA, a person who spend his free time to help people here, will be more afraid to espress his judgment on a map.
But now I'm at work and usually I write really bad post when at work....so sorry if the above is not totally clear....I try to explain everything in a better way this evening, when back at home.