I was wondering whether any of you lot follow a certain code of modding etiquette?
Well I certainly do. Here are the rules which I attempt to stick to.
1. Never plagiarise the work of other modders
It is forbidden to use the work of another modder and claim it is your own.
2. Always give credit where due.
If you do not know the origin of an asset, do not be embarrassed to ask another modder. Ignorance is not an excuse.
3. Quality before Quantity.
Instead of aiming to produce as many mods as possible, try to made products which are more complete and well thought out.
4. Stuck? Ask for help.
Whenever you feel that you have "hit the wall" or encountered a problem, do not be embarrassed to ask for help.
5. Criticism is mostly good
You will learn a lot from both bad and good criticism.
6. There is always room for improvement.
There are no perfect mods except Cloud City: Insanity. FACT
7. Releasing Assets is just a nice thing to do.
Sure you don't have to do it, but modders will be truly thankful when you do it.
8. Don't make a promise you can't keep.
You may feel compelled to tackle the requests. However be aware of how much work load you can handle.
9. Deadlines aren't always applicable.
Sometimes with a mod you can feel whether it'll be completed before a certain date. Other times the project can be in flux and you have no idea what's going on. Deadlines can force you to get your bottom in gear, or they can be an unnecessary stress. Find your balance.
10. Research
Take a look at past mods and decide what is actually achievable, or "borrow" ideas when your brain is empty.
Well I certainly do. Here are the rules which I attempt to stick to.
1. Never plagiarise the work of other modders
It is forbidden to use the work of another modder and claim it is your own.
2. Always give credit where due.
If you do not know the origin of an asset, do not be embarrassed to ask another modder. Ignorance is not an excuse.
3. Quality before Quantity.
Instead of aiming to produce as many mods as possible, try to made products which are more complete and well thought out.
4. Stuck? Ask for help.
Whenever you feel that you have "hit the wall" or encountered a problem, do not be embarrassed to ask for help.
5. Criticism is mostly good
You will learn a lot from both bad and good criticism.
6. There is always room for improvement.
There are no perfect mods except Cloud City: Insanity. FACT
7. Releasing Assets is just a nice thing to do.
Sure you don't have to do it, but modders will be truly thankful when you do it.
8. Don't make a promise you can't keep.
You may feel compelled to tackle the requests. However be aware of how much work load you can handle.
9. Deadlines aren't always applicable.
Sometimes with a mod you can feel whether it'll be completed before a certain date. Other times the project can be in flux and you have no idea what's going on. Deadlines can force you to get your bottom in gear, or they can be an unnecessary stress. Find your balance.
10. Research
Take a look at past mods and decide what is actually achievable, or "borrow" ideas when your brain is empty.