Written
: 7/17/2000So, starting up you're own little game development team? Well, I've been there, I've done that, I've pulled my hair out over it and done little victory dances over it. There are a *lot* of pitfalls when you get an idea and want to make a game, a mod, or any project. Maybe I can help you avoid a few, or at least give you some good ideas. Forming the proper team can obviously make or break whatever it is you're trying to accomplish. Believe me, it can break swiftly, or die a slow painful death you never saw coming. It's best to use solid building blocks to begin with.
First off, and most
importantly, you have an idea, a game design, a mod design, sketches, any
combination of things that represent what it is you want to produce. Ideas are
great, don't bash them, but an idea is just an idea, you need to get from point
A) Idea, to point B) Something that kicks ass. This idea will no doubt be what
you use to attract the interest of other team members, or maybe you have some
friends that just want to work on things like this as a team. Either way, lets
get started :)
The Team, recruiting,
shaping and keeping together a team of individuals towards a common goal can be
a difficult, trying, and sometimes impossible task, especially if you're all
working for free or in your spare time or as a hobby. But proper construction of
a team can save you a *lot* of hassles down the road if done right in the first
place. The key, and I mean the very soul of a working team is the fact that they
work as a *team*. If people can't work together, they can't work, and that
really puts a crimp in your goals.
So, let's assume you have the idea, maybe a few design notes, or even a full blown out design document with artwork, conceptual materials (maybe some 3d models, textures, 2d sprites, whatever pertains to the project) and the whole nine yards. This leaves you with trying to find other people willing to help you realize the project in its final glorious stage. The saga begins here.