How to contribute

There is a multitude of things you can do depending on your skills:

• answering other people's posts. Every post we don't have to answer ourselves adds to the time we can spend on coding.
• create documentation. If you think it was hard to figure out how something works but now you know, write down your knowledge.
• scripting. Many of the settings in the scripts are not there because the scripters want them to be that way, but because nobody found the time to change them.
• use InsideUO. Looking up the hex-code for a missing sound, animation, item you request is easy but rather time-consuming.
• report bugs. If you experience something that you feel is a bug, take the time to report it, even if you found another solution.
• systematic testing. As opposed to reporting just the bugs you encounter while playing, testing means trying to get bugs.

If you have at least a basic knowledge of C/C++ you can also

• make bugs reproducable
• use the debugger to find bugs
• provide bugfixes
• code small features
• do some revamping
• code big features
• help to redesign kernel subsystems
• do profiling and tuning

(order of appearance marks difficulty imho) Be careful to choose the task that is appropriate to your skill ! Example: If a newbie coder implements a feature in 5 days and an experienced dev spends a total of 5 hours to help him, the newbie will learn a lot and the dev will have fun helping him. But if the dev would have implemented the same feature himself, it might have taken only 2 hours. So this can not be considered a true contribution to Wolfpack. Rule of thumb: If you can do one of these tasks without any help from another dev, the next task in the list will probably be appropriate (needing just a few hints).