I'm not AGAINST programming, I'm against C++, that said, it's not a very easy thing to work with, especially if it's with other people.
And you even hand me my own point, if this is a community project, it needs to be simple, not a company effort. I really think that we should just stick to the basic for a FIRST game, and not get out of hand with already crafting a RPG of sorts.
ALL teams first make a prototype game, especially community teams like these who just want to make games, we first have to see who's comfortable with what, and we can leave the ambitious projects for later.
You guys are focusing on a picture that is far too large, we need to start off slowly, not just leap into the pool and bonk our heads on the cement.
P.S. - This is up to TheChosen because he is the lead designer, we all give him credit for starting this in the first place, and the only way we can actually pull of a good project is by relying on TheChosen to choose a straight course of action so that everyone is certain that we're doing a certain thing.
P.P.S. - You seem to think that I'm assuming that there'll be assignments "handed-out" but that's not the case. But we DO ABSOLUTLY need to give someone instructions on what we need help on, if everyone who wants to help just runs around and donates random stuff to a single few who are actually creating the game, it'd be senseless. Everyone needs something to do, and if we all don't decide on a "style" or certain ambigous flavor, there'll be so much unrelated and ugly meshes that this would all be pointless, and everyone's efforts to actual be "satisfied" would lead to dissapointment.
|