- Joined
- Feb 23, 2008
- Messages
- 587
About
Hive Community built game. With the goal of a simple to moderate size game, built by lots of different people at the hive. The design of the game would need to be built in such a way that people would be able to do one small part of it, that would hook in by a middle person.
How It could work
Game Concept
Have a Contest for a simple to moderate game idea. And allow people to come up with ideas, and let the people at the hive vote on it.
Game Details
Then Have a thread with who ever game up the idea, gather feed back for 2 weeks on furthering the detail of the game.
Game Outline (Master Plan)
Then either a admin or someone with a high level of mapping experience will take the lead in mapping all the components that need to be done. Most Components. should take the avg mapper 15 min to 60 min to complete.
He will then lay out a map of all the task to be done, broken down into many sub functions, (that perhaps he could do in hes sleep) but that are very clear on what they need to do.
He will write in a text file, or on a forum. What the functions take, and what they will do or return.
Building Components
Then in a testing area, someone else or the high level mapper, will test each thing that people have submitted. These will can be submitted via a map file, that does the task, and the code used.
People on the hive will only be allowed to do 1 or 2 task a week. (This way i think more people will get involved, and people of some skill don't all jump on the easy task)
Any resources that are going to be required for the game would be put in this area as well.
Putin Components Together
The High level mapper will start to put the components in place as they are completed. but he him self would not do the code, only the outline of shell of the game.
Finalizing game and testing
- After the map is finished, there can be a 2 week testing period, before releasing.
The Major Goal of the project
To make a com-minty built game, with varying amounts of skills, with everyone puting in a small amount of time. (expect maybe the lead maper)
Its not to have super effeicent perfect functions, or super great game. Its too allow and help get people involved and to learn, with what they can do, i feel the project could be ruined if people are to strict on how well things perform and if they shun people who are in a learning phase, or even brand new.
I think if this were done 2 or three times a year, people like my self who don't want to put in a huge amount of time to make a map, can still feel involved in the commitny here, and still stay a little be fresh.
I also think it would be really cool if someone made a video about the project and every few weeks, showing how its coming along, and to help inspire people to work on projects of there own or to join the comminty project.
Hive Community built game. With the goal of a simple to moderate size game, built by lots of different people at the hive. The design of the game would need to be built in such a way that people would be able to do one small part of it, that would hook in by a middle person.
How It could work
Game Concept
Have a Contest for a simple to moderate game idea. And allow people to come up with ideas, and let the people at the hive vote on it.
Game Details
Then Have a thread with who ever game up the idea, gather feed back for 2 weeks on furthering the detail of the game.
Game Outline (Master Plan)
Then either a admin or someone with a high level of mapping experience will take the lead in mapping all the components that need to be done. Most Components. should take the avg mapper 15 min to 60 min to complete.
He will then lay out a map of all the task to be done, broken down into many sub functions, (that perhaps he could do in hes sleep) but that are very clear on what they need to do.
He will write in a text file, or on a forum. What the functions take, and what they will do or return.
Building Components
Then in a testing area, someone else or the high level mapper, will test each thing that people have submitted. These will can be submitted via a map file, that does the task, and the code used.
People on the hive will only be allowed to do 1 or 2 task a week. (This way i think more people will get involved, and people of some skill don't all jump on the easy task)
Any resources that are going to be required for the game would be put in this area as well.
Putin Components Together
The High level mapper will start to put the components in place as they are completed. but he him self would not do the code, only the outline of shell of the game.
Finalizing game and testing
- After the map is finished, there can be a 2 week testing period, before releasing.
The Major Goal of the project
To make a com-minty built game, with varying amounts of skills, with everyone puting in a small amount of time. (expect maybe the lead maper)
Its not to have super effeicent perfect functions, or super great game. Its too allow and help get people involved and to learn, with what they can do, i feel the project could be ruined if people are to strict on how well things perform and if they shun people who are in a learning phase, or even brand new.
I think if this were done 2 or three times a year, people like my self who don't want to put in a huge amount of time to make a map, can still feel involved in the commitny here, and still stay a little be fresh.
I also think it would be really cool if someone made a video about the project and every few weeks, showing how its coming along, and to help inspire people to work on projects of there own or to join the comminty project.