It's great that you want to get involved in building games
But I wouldn't want you to get discouraged when this project falls apart under it's own weight, rather than taking it slow, designing and building something achieveable, getting the satisfaction of looking at a finished project and saying "Yay, I built this! Now let's try the next level up". You're trying to run before you can walk, but if you learn it right you might get there one day
If you're serious about building games, my advice is to do a smaller test-project first. Think like the kind of games you get on your phone; puzzle blocks, arcade, maybe a 2d scrolling shooter. Two classic first-games are tic-tac-toe and pong. You can add a little story between the levels if you want.
They might sound more boring than your current plans, but it will give you a realistic idea of how games are put together, how long it will take, what team members you need and how to organize and divide the workload between them.
I think the point that the others haven't quite got across is that if this is the first game you have ever worked on, you're batting too high. Even an experienced team of home developers would struggle to take on something this big.
But don't get dissuaded, it's fun to have dreams and come up with ideas when you're a kid. We've all done it; I wanted to make a platformer (which were pretty damn good in 1993). It was awesome coming up with all the level designs, ledges to jump on and enemies to kill, that kind of thing. But I made the classic beginner mistake that you've just fallen into; designing a game exactly like the kind of games I played without knowing how they're made. When I was advised to scale it down, I thought it'd be fine if I just did 10 levels instead of 100. Doesn't work like that; I now know that if a platform game is built properly adding extra levels is piss easy. As for my project, all I managed to do was get a sprite to walk left and right on a plain black screen. The difference between us is I didn't drag anyone else in before my little project crumbled. I didn't mess anyone else about, getting them to put time into something I'd never finish.
Rather than pulling other people in too early without a clear idea of what they need to do, I think you need to go, think it through and research the process of building a game a bit more. I don't think you know how a game is put together; to use an example from your thread asking to build graphic models before the programmers have worked out what size they need to be doesn't make sense to me. The story, characters, plot, setting, narrative, no matter how long or intricate it is, that's all only a very very tiny part of the equation.
As a player all you see is the story and graphics, but there's a lot, lot more going on behind-the-scenes that you seem to have missed. Do this right and you might find game development rather fun.
If you're serious about building games, my advice is to do a smaller test-project first. Think like the kind of games you get on your phone; puzzle blocks, arcade, maybe a 2d scrolling shooter. Two classic first-games are tic-tac-toe and pong. You can add a little story between the levels if you want.
They might sound more boring than your current plans, but it will give you a realistic idea of how games are put together, how long it will take, what team members you need and how to organize and divide the workload between them.
I think the point that the others haven't quite got across is that if this is the first game you have ever worked on, you're batting too high. Even an experienced team of home developers would struggle to take on something this big.
But don't get dissuaded, it's fun to have dreams and come up with ideas when you're a kid. We've all done it; I wanted to make a platformer (which were pretty damn good in 1993). It was awesome coming up with all the level designs, ledges to jump on and enemies to kill, that kind of thing. But I made the classic beginner mistake that you've just fallen into; designing a game exactly like the kind of games I played without knowing how they're made. When I was advised to scale it down, I thought it'd be fine if I just did 10 levels instead of 100. Doesn't work like that; I now know that if a platform game is built properly adding extra levels is piss easy. As for my project, all I managed to do was get a sprite to walk left and right on a plain black screen. The difference between us is I didn't drag anyone else in before my little project crumbled. I didn't mess anyone else about, getting them to put time into something I'd never finish.
Rather than pulling other people in too early without a clear idea of what they need to do, I think you need to go, think it through and research the process of building a game a bit more. I don't think you know how a game is put together; to use an example from your thread asking to build graphic models before the programmers have worked out what size they need to be doesn't make sense to me. The story, characters, plot, setting, narrative, no matter how long or intricate it is, that's all only a very very tiny part of the equation.
As a player all you see is the story and graphics, but there's a lot, lot more going on behind-the-scenes that you seem to have missed. Do this right and you might find game development rather fun.
