Thread: [Discussion] Thoughts on a Community Project?
View Single Post
  #6    
Old January 17th, 2013, 04:27 PM
Nintendork15
I'm gone. Bye.
 
Join Date: Feb 2009
Location: Undertaker. Co.
Age: 20
Gender: Male
Nature: Naughty
Quote:
Originally Posted by DaSpirit View Post
I've honestly never seen a community project finish anywhere. They always fail.

I'd be better to just start an open source project.
The amount of people that could work on a community project, when one person leaves, there's always bound to either be someone ready to replace them, or someone who can do the same thing already in the project.

Quote:
Originally Posted by Sunfished View Post
It really sounds like a fun little thing we can get into. And because of the amount of people this board REALLY has and the creativity of some who never got into game developing, we can really steamroll through this kind of project!

If your planning to attempt this, I suggest you begin as soon as possible. Every time a new Pokemon game comes out, this place gets kinda deserted...

I'll support this
I agree, this place has alot of creativity and potential, enough to make a really good game, I'm hoping enough members want to do this! '

Quote:
Originally Posted by Maruno View Post
I've had this thought too. It'll be very difficult to pull off, though.

If you go for the "one leader/coordinator, everyone else contributes", then it's practically no different to any other fangame being made. The "contributions" will only be vague suggestions, meaning no actual work will get done except by the leader, who will inevitably give up once they realise they're stuck doing everything by themselves. Also, the community will never agree on anything (plot/pacing/Pokémon/mapping/etc.), so no progress will be made there anyway unless someone (the leader) takes charge and defines a direction - in which case, again, it's no different to any other fangame.

----------------------------

There is an alternative, though, and it's one I've been thinking about and which may have potential. One person works on the game at a time, and possession rotates between those who volunteer in turn. There is a strict time limit of 1 week per person, during which time they're allowed to do anything they want to the game (including undoing/redoing other people's work without remorse). At the end of their week, they send a download link to the next person on the list, and post a summary of what they've done for everyone to see. If they fail to do either of these things, their efforts are ignored and the previous week's version gets passed on instead (both the revised game and the summary are required, as it's a team effort and there shouldn't be secrets or hidden information between members; otherwise their work cannot be accepted).

The advantage of this is that people can have a go at a bit of game-making for a week, and will only contribute if they're actually interested enough to volunteer (which means they will do something). The time per person (1 week) is kept relatively short to encourage actual progress, rather than letting it get bogged down with designing new-for-the-sake-of-new systems (not to mention keeping things going relatively smoothly if someone vanishes). Meanwhile, the thread for the project will have discussion about the latest week's changes, collaboration about the story and so on, and will help direct the suggested progress of the game - the current week's developer still has absolute free reign over everything, of course. In the end all the revisions and possessions and discussions should come together to form an actual game.

Obviously someone needs to start things off first, perhaps before even making a thread for this project (so there's something to start from). Or maybe you could say that the Essentials example maps are the starting point, rather than starting with a blank slate like normal, and for starters the aim is to expand/turn them into an actual game (plans can always change later). I don't know whether it's better to let everyone download every week's revision, or whether it should be passed privately between each person as their turn comes round (the project's coordinater should also keep every revision for archiving, which is their only purpose). Everyone should definitely be kept informed of all the changes made each week, though.

Could this work?
The only problem I see with this, and a problem all together with a community project is, someone managing to sign up to this, and get to their turn, and just mess it all up.
Of course we'd have backups but it would be a real let down.

As for the passing it around, it's a well good idea, but privately would work better, but in the Project's thread the last member who worked on it, must post Screenshots of their progress and their summary sheet, and any adaptations they have made to the Design Document, including the Document itself. The private way I can see is something like Google Drive, only people you want can access the downloadables. Which means we'd all have to get Google accounts.

And yes, starting off would be a bit iffy, We'd need to make a story, and features and general plots and thing like that, that usual take a while to generate and write down.
__________________
gone.

Last edited by Nintendork15; January 17th, 2013 at 04:34 PM. Reason: Your double post has been automatically merged.
Reply With Quote