@mandude said:
I think this might be another futile endeavour for as long as we don't rectify what made it die the last time.
People can't realistically commit to specific departments or the project as a whole until some of the finer details have been worked out. Until that point you run the risk of over-saturating the project with people who only have a mild interest, which in turn dilutes the commitment coming from people who genuinely want to create something.
Just keep in mind that in this environment, asset creators are more valuable to you than designers, so if you're going for a similar design-by-committee system like the last project had, I would recommend making it entirely inclusive of the people who will actually be making the various parts of the game.
I agree. Unless there is a Lead in every category that has final say and the power to push things forward, this isn't looking very promising. Before anything gets coded or drawn, there needs to be direction. Without a solid design doc that at least solidifies what the game is and where it's going to be headed (and ideally at least one fully fleshed out level), everyone else is just spinning their wheels creating random ass assets. I'd recommend culling the "designer" position down to just two or three people tops to discuss and iron out what to do. Go ahead and have them take ideas from the community but limit the designers down to as few as possible just to get the ball rolling.
Here's what I recommend. Take down names now for people who are interested in contributing, that's cool, but first gather the designers and really focus on getting what exactly the game is going to be. I mean down to as small a detail as you can manage because otherwise, the programmers won't know what to do when they get to any part that isn't written out for them.
An easy example is say
Player can jump and double jump.
What is the peak jump amount? Is there vertical slowdown as the player reaches the peak? Can the player stop upwards movement at any time or is it full jump every time? Can the player change direction once leaving the ground? Can the player only double jump if they're still moving upwards? If not, how far can they fall before double jump is unavailable? All same options for double jump as regular jump. Can a double jump be started if the player didn't manually start the initial jump? (fall off ledge) How soon after landing can the player jump again? Will ground movement be effected by landing from a jump? etc.
Every one of these things that aren't worked out before hand will cause delays and most likely will be determined by whoever is programming. If this information isn't communicated back to the team, it'll prolly cause confusion later. Hell, working alone, I sometimes lose track of how something works which causes me to look back through hundreds of lines of code to find out why something is doing something instead of something else -_-;;
Working with a very small team of people, you may be able to wing it but I feel like the way this project will go, it needs to be written down for everyone.
Actually, fuck it. Just use the awesome images SuperNormalStep made and write out a dating sim =D
Whatever happens, I'm looking forward to what you guys put together. GB community rocks.
Log in to comment