I've been getting this question very often lately, so I'll try to explain it to you. I'm now part of the development of the Trinity kernel, and I'm running a database for that kernel. My goal and task is to correct now what I think is important and necessary for the game. Trinity was actually created to separate from the mango, to keep its repairs, but also to do its own - important. The developers of mangos fix instead of significant errors in the new add-on, for example, renaming some commands for GM. This seems completely unnecessary to me at the moment - the mangos will spend a good few weeks on it. We prefer to fix falls, spells and general functionality. From this point of view, it seems to me better to devote my time to repairs and functionality than organizing events that are not ideal for such a large number of players and usually fail. That's why there are official events - planned from the creators of the games themselves, which we always try to get back to perfection and should be enough.
Another question that you often ask is why we list here the corrected errors. The reason is completely prosaic. We list every change and correction we make so that you and we have an overview of what we have corrected and so that we can test whether the correction was successful or not. This is how it should work and has been for some time. You have an overview of what is happening with the server and we know when, how and where we did, so that we can come back to it later if the error is repeated or interrupted by another, etc. One of the reasons for switching to the latest version of the game together with the official servers is the functionality and mainly bug fixes. So we do not want to stay on older versions, like other servers for the price of maybe more stability but malfunction and without new things, but that we want to keep up with official servers and to correct the latest errors we still need data from official servers and they can only be obtained with the latest versions. It’s a long road and we know it, but we believe that with your help we can do it.
What should I do if I want to help the server?
The first way is through voluntary contributions to the server (I have to update the donor at last), which you can send using the instructions given on this Site.
The second way is through error reporting. If I find that there is an error in the game - I register on the forum (data noare the same as the login to the game) and report the error to the sub-forum Bug report - all bug reports here. I will read the topic carefully How to correctly start a topic with a mistake!. I prefer to copy the topic so that it is in everyone’s eyes:
Basic principles of creating an error report:
1) Before I create a report, I always convince myself using the function SearchWhether this error has been reported before. If I have any new information about an already reported error, I can update the topik or remind it of its importance in the case of a long uncorrected and yet important error.
2) We always create only one bug report into one topic - explained below
3) We always check first whether the error is manifested in others and not only in the individual - in this case there is a topic for the individual Help me - Help me
4) We will try to correct the error ourselves by the following procedures:
--- a) Clear temporary Cache, Interface and WTF folders
--- b) Reinstall Drahy Program
--- c) Turn off and turn on the game
5) Only now I can write a bug report - GM will then check the bug or players will confirm the bug and solve the problem sooner or later with the inscription [Solved] (Subtitle of the topic)
Example of starting a topic with an error:
Name of the error and what it refers to: (Chyba quests) Stranghlethorn Fever
Description: When killing the monster, there was no loot, which has a 100% success rate to get
Link to the site: http://www.wowhead.com/?quest=348
Date and time when it happened: 4.9.2008 - 17:00 (we do repairs several times a day)
Character (players): Melkor (Trump, Truffle, Jerk, ouma, ...)
If the error concerns a faulty dmg or heal, it is necessary to add a screenshot with a combat logo to each report, where this fact will be clearly visible.
We base only one error on the topics, so that we can always discuss the given error, solve it, supply information, what can be caused and later during the repair to test it and finally solve the error - so we do not solve 20 errors at once, but error after error and we expect separate topics on errors. If there were more errors in the topic or if God did not give a summary of all errors from one area - to search for information on a given error in a huge 50-page topical would be almost impossible and unnecessarily delaying. If a similar topic were to inform what is going on and what is not in the area, it would have to be updated regularly, which is not the case in 90% of cases. There is logic and reason. We are not interested in delaying you with one mistake per topic, the point is that we also have to correct the errors one by one and in order to handle it, we need as much information as possible about each mistake and no reports like "The spell does not work or does not work". The more information we have - in which situation we do not go, more people do not go, just some part, send screenshots, went like this always or only now, etc., the better and thus increase the chance of faster repair. I hope you understand. So we’re not looking for GMs who won’t do anything with bugs anyway, we’re looking for you who want functional spells and a server and are happy to contribute to that. Thank you for your attention and I believe that together we will be able to create a quality, stable, blizzlike and functional server full of fun and relaxation.
Server Repairs
1) Fixed crashes caused by bad thongs in battlegrounds
2) All bosses in the Sunwell Plateau (missing the final) - after successful tests we can open
3) Fixed cases where Counterspell canceled shapeshift forms
4) Fixed Winged Steed of the Ebon Blade
5) Fixed spell Blessing of Sanctuary
6) Perhaps the attack of the fives in the arenas has been fixed