Rules for making a successful request

From Nexus Mods Wiki
Jump to: navigation, search

For those of you with modding ambitions

1) Define your project: nothing is more important than this. Tell exactly what you're trying to make. Show that you've put some effort and thought into your project already. If you don't have this definition, you're going to have a hard time convincing anyone you're serious about it, and you probably won't ever get beyond the initial "hey, I could make a mod" thought.

2) Make your requests specific: don't just say "I need interior/exterior builders, scripters, modelers." Ask for specific things like "I need a sword model, and a script that does x." You've got a lot better chance of getting the help you want, and you're not wasting people's time by making them guess what you need.

3) Make sure YOU are doing something, and not just providing an idea: Whose project is going to get more interest, someone who posts a progress list, screenshots, and shows clear evidence of work on it, or someone who just writes a single line idea and expects everyone else to do all the real work. This is especially important if you're asking for major work.

4) Use correct English: It's not everyone's main language, and everyone makes mistakes, but there's just no excuse besides laziness for stuff like "u" and 1337ish. If you don't take your project seriously enough to do this, why should anyone else?

5) Nobody owes you anything: People don't have endless free time just praying someone gives them an idea to work on. So don't complain if your request doesn't get enough interest. Maybe you've got a problem with 1-4 above, maybe your idea isn't that interesting to people, or maybe the help you need doesn't have enough time to work on your project.

6) Don't get too ambitious. It's very easy to start listing all the cool features you want to have and congratulating yourselves on what an amazing mod you're about to make. But be realistic, these things are a lot more complicated than you think. Most of these ambitious mods fail before they really get anywhere, and for good reason. Think very carefully about what you realistically can do, and cut down your ambitions. It's better to produce a smaller mod than to fail at making a bigger one.

7) Use the talents you have. This ties into not getting too ambitious... take a look at the people you have and their talents, and give yourself a sanity check. Can you actually do all these things you're dreaming of? It's very easy to say "I'll have X new models". But do you have someone with the right software and skills to make them? And make them well? Don't count on the miracle of someone showing up to join your team.

8) Modding is HARD. It's very easy to start a self-congratulatory list of what a cool mod you're going to make. But odds are, you have no idea how difficult a project you just started. Take whatever amount of work you think it'll take, multiply that by a hundred or so, then double it, and maybe you'll come close to the real number.

Small-scale mods are bad enough, but doing a total conversion or other large mod is an entirely different nightmare. Not only will you need those expert modelers/texturers/writers/scripters/etc, but you'll need several of each (at least if you want to be done before TES VII is out). And even worse, you'll need administrators. Leading a team is much harder than it looks... anyone can throw out some vague ideas, but actually managing a large-scale project is far more difficult. Even if the leader doesn't produce one model/script/paragraph of writing themselves, they'll probably be investing more time and energy than anyone else on the team.

9) Bad things happen. If you start on one of these large-scale projects, bad things will inevitably happen. Your leader will find himself with a sudden increase in real-life commitments. Your storyline author will have to leave for personal reasons. Your concept artist will forget to pay his internet bills and be offline for a month and screw up all your deadlines. The only copy of your quest-writers work will be lost in a hard drive crash. You'll find after a month of work that two critical scripts (written by different people) have conflicts with each other and need to be redone. Etc... the list goes on and on. Real life will intrude on your happy dreams of modding. Are you really prepared to deal with these problems and keep working, or will the project just fall apart?