Questions about proposed changes

[Sigfried Hunin]

There's very little point in me spitting out another list, I feel. The coders can only do so much, and doing that just further invites people to think "OH MAN YOU GAVE HIM WHAT *HE* WANTED IN THE SYSTEM BUT NOT WHAT *I* WANTED?" when some of it falls through, because you can't please everyone.

I'm not going to hand the coders what amounts to an ultimatum of "HERE'S WHAT IT'LL TAKE FOR ME TO STICK AROUND."

Right, but the idea here is that you give a very super rough idea of what you would like without demanding a specific system. Super rough cut guidelines can give coders an idea what we want without telling them what to do.

And, I mean, once again, it's not an ultimatum, it's what we'd like to see if they were gonna come up with a new/amended system. I think that just very vague, "it would be cool if the mechanics that happened had X CHARACTERISTICS," not "I want you to implement X MECHANICS," statements can narrow down what we want to see without trying to tell them what to make.