Team Hack Planning
This thread shall serve as a location for both hack leaders and aspiring team hack members to locate helpers and intriguing projects respectfully. The intention of this is to restrict the great number of threads requesting help, and this will allow people interested in participating in a team collaboration to more easily discover a thread that fits their desires. As a result of this thread's existence, there should be no outside threads or posts searching for helpers or team hacks; team hack threads may be opened in the Works in Progress subforum once relatively significant progress on the project has been reached.
Rules
Leaders
1.) Make especially certain to define the main story or theme for your hack. Not many people are going to join your project if you vaguely describe it in a single sentence. Thus, it would be wise to have a well-defined idea of your hack, preferably within one to three paragraphs or so.
2.) Attempt to make the goals for your hack realistic. Most team hacks fail due to their outrageous objectives; many members are simply unable to accomplish various tasks. For example, many people on SMWC would be unable to make bosses at the caliber of those in Brutal Mario, so you should not expect them to be able to create a boss or sprite to such a great magnitude. If you yourself cannot imagine a possible way to make an aspect of the hack work, then you may wish to hold back on including that detail for the hack.
3.) Please identify which roles will be required for your project. Without knowledge as to which roles require positions, other users will not know where they fit into your hack, and they are much less likely to apply.
-a.) Other than positions that remain unoccupied, you should not be managing your team hack in this thread or an existing project thread. Clearly, you may show off work in a team hack thread that you may release on a later date, but try to make contact with your other members through outside means, including PMs, the Discord, and more.
4.) Similar to other related scenarios, do not whine if you are not acknowledged at first. If your hack is truly appealing to others, people will come by eventually. As such, you should not "bump" your post for at least a week's time; it typically reflects poorly upon your person anyway.
5.) Being a team leader does NOT exclude you from working on the project itself. If you cannot create levels or fulfill various roles in the project, then you should simply not be a part of the project at all. Your "leadership" position should entitle you the rights to assemble and manage the various pieces and positions of the project, but you should also fill a role or two in the project. Overall, you should always be working as an organizer and member together in a single position.
-a.) Although you have the main authority when it comes to what is finalized in the hack and who works on the hack, you should listen to the members involved in your project. They will have great ideas for the benefit of the hack, and if your co-operation is an issue, then your project as a whole will have holes in it.
Regular Members
1.) When you are posting in this thread, make sure to identify the hack you are joining and the role(s) you are taking. By doing so, you will make it easier on the team leader to add you to the list. If you fail to identify either of those, it will require further work from others to discover what you wanted to do.
2.) Do not repost if you are not noticed immediately. If anything, the team leader has not checked the thread since you posted, and he or she will most likely check the thread eventually. If worse comes to worst, you could send a PM to the team leader and indicate your post.
-a.) If you are not accepted by a team leader to join a project, do not become disheartened. There should be many other projects that you can join, and through practice, your hacking skills will improve. Eventually, there may be an even great project underway that you will be applicable to join. So, do not become discouraged; it is simply something that happens in life regardless of experience or enthusiasm.
3.) By signing up for a project, you are assuring the leader that you will fulfill your specific part in the project and complete your tasks as necessary. If you do not pull through with your work, then you are only going to delay the project, and you may be dropped from the project accordingly.
-a.) As a member of the project, however, you are also permitted or perhaps even expected to provide insight about various subjects regarding the project. Doing so will help enhance the quality in the project, and it will strengthen the connection between all of the members of the project.
As said, follow the rules, and have fun with your team hacks! Try not to let them get too out of hand.