- Joined
- Jul 18, 2008
- Messages
- 4,863
Note: This tutorial is currently unfinished, I will update it as I continue to write it
How to effectively ask for help/recruit for your wc3/sc2 modding project
Problem:
Browse through the Recruitment and Requesting forums and you'll see that many, many people fail to understand how to effectively get support for their projects, leading to threads that simply end in bumps until their dead or a few people with 1 post that leave soon after volunteering to help but never actually getting to it. Often these people seem to wonder why no one is interested in their project, or why their thread is completely ignored.How to effectively ask for help/recruit for your wc3/sc2 modding project
Problem:
Answer
Face the facts - no one will be interested in your project if you don't present it well. Like any effective advertisement, it's up to you as the person creating the thread to sell your "product" to the people. The more effectively you do this, the more help and the higher quality help you will receive in the process.
Let's start by examining how NOT to present your project.
(all examples are hypothetical - but very typical)
(all examples are hypothetical - but very typical)
All too many people fall into some specific mistakes that always end up sour on their part.
Mistake #1:
Saying absolutely minimum about pretty much any details concerning your project.
Example said:
Every time I see a thread like this, I want to somehow find a way to use the power of the internet to digitize my fist just to punch this guy halfway across the world for expecting any help for this sort of thing. It should be obvious, but let's examine the main errors here:
*You say absolutely nothing about your project. Not an inkling of the proposed project is presented except for the fact that it is an RPG. No one will be interested as you've given them nothing at all to be interested in. This is a big red X that essentially says you don't want any help - people will happily oblige to this.
*You don't say what you need anyone to do. How do you expect people to help you if even you don't know what you want them to do? More importantly, you don't state what you yourself will do. Many people seem to give this impression that they need others to do the whole map for them - being a "team leader" isn't exactly going to cut it and for a project to work effectively, everyone needs to be doing at least something.
Overall the main flaw in this is that the thread overall looks half-@$$, as if you had spontaneously came up with the idea like 5 seconds ago and then started rushing to get people to code the whole map for you.
If you learn anything from this tutorial, anything at all, take this and don't be this guy - he NEVER gets any help for his project.
Mistake #2:
Complete Cliche - no real idea at all
Example said:
Okay, so this looks more acceptable - yet it still is majorly lacking and may fetch a few people to help, but won't fetch anyone with some real experience. Let's examine this thread's main errors:
*The main problem is this thread is just one huge cliche. No one will be interested, as no one wants to work on what's been done hundreds of times. Stop digging in the bargain bin of old tired ideas and come up with something truly interesting.
*Building on the above point, being cliche it also looks like a half thought out idea - it's like mixing together key RPG terms in a blender to create a flavorless smoothie.
*"Archer: uses arrows to fight enemies from afar" - Orly? The reader can infer this, especially since they've seen a million other archers before. Not everything can be original in a project, at least not in just any project - if the reader can infer something correctly, don't insult their intelligence.
Last edited:
