Posted 29 July 2010 - 02:49 AM
The problem of repacks are things that devs and support people for the original emu care about, but, the users usually don't, so, of course, most of you wouldn't understand what the big deal is.
First reason is that the users of repacks almost always think that the dev team on the real emu are there to support them when their repack fails, because they are the ones that maintain the code the repack was based on, so, it follows, in their mind, that they will know how to fix their problem, the problem with this, is repackers will usually include some patches, or, even modify the code themselves, and, we don't always have a way to tell what they changed, and whether or not the problem is due to their changes, or, our original coding.
Second reason (this isn't usually the case anymore, so, this reason is a bit deprecated) repackers used to include the files that are supposed to be extracted by the user from their own client (dbc, map, vmap, etc.) making these repacks illegal, and putting emu coders in the position of having to have a zero tolerance policy on repacks to keep our legal distance from them.
Third reason is that repackers have been known to make it sound in their changefiles, etc. like they are the ones improving the server, when actually, they are just updating to a newer version of the base emu and not giving proper credits to the people actually submitting the fixes.
There are some other reasons, but, I think these are three major reasons.
A personal reason, which is likely shared by many other devs, etc. is that most of the people who use repacks are lazy and end up not knowing how to properly care for their server once the automated installer is done, and then expect us to help them with the things most people who are doing it the old fashioned way already know how to take care of.