What is the difference between the az end and the TC end of World of Warcraft? The relationship between Mangos, TC, SW, AZ, and AC
Hello everyone, I am Aixi. Many friends in World of Warcraft do not understand the difference between the AZ end and the TC end. The editor has searched a lot of information and simply told you that today is the Aixi story meeting. It's time to listen to the story!
(The following content is just what Ren has learned, just take it as a story and listen to it)
Before the release of WOW, the beta version of the client has already attracted the enthusiasm of enthusiasts. Among them, the most technical batch has already started to make emulators to try to experience WOW in advance. This is the original simulator . There are many kinds of original simulators, and Mango is one of them . At that time there was no tc and az, everyone was in Mango
Mango is a general-purpose online game server in name, but it is actually a wow server that imitates the official.
With the update of the open version of wow, Mango 's opinions began to split. Many people think that imitating officials is a principle, which cannot be modified, but some people hope to add more interesting settings and ideas to it. So the tuand split, those who insisted on imitating officials stayed in the mango , those who wanted to engage in black technology split out, and established a new tuand called TrinityCore, they were the most technically powerful group of ren in the original mango tuand . After the mango tuand split, splitting happened again soon after. The unknown reason is just speculation, and it may be that the attitudes of the remaining people towards the future have begun to diverge. After all, there is only so much official content, and the imitation of official content can easily come to an end, and the rest of the work is just to mechanically fill in the content and fix bugs. So in the end Mango Tuand was split into two parts again, and a part of Tuand members with strong technical ability made a series of "final versions", namely Mango Zero/ Mango One/ Mango Two/
The Mango Three series
has experienced two splits. After the best and relatively good members left, the remaining Mango members only had beliefs and low technical skills. They changed the name of tuand to C Mango (meaning continuously updated Mango , which probably means to distinguish it from Mango Zero , which washes its hands after one vote ), continues to update its own mango . C mango tuand is relatively formal in organization, technically terrible, and many old bugs cannot be fixed. It can be seen that they are working hard, but the effect seems to be slammed by the new version of Mango Zero , which is only updated by one ren - the latter is used for As the base of many well-known high-quality 112 xx , the former can only be used to develop a stand-alone version for personal entertainment . Now that the story of Mango is finished, let’s go back to the story of TrinityCore. After TrinityCore split from Mango Tuand , they immediately engaged in a lot of black technology. So their products are very popular in the market and gradually become the mainstream in the xx industry. But, soon, their tuand
The team's idea of "pursuing more advanced technology realization" has brought new problems: the bugs they fix are very limited, but they create a lot of bugs in the process of researching new technologies. Although they have a lot of black technology, they are bought at the cost of low repair . If you want to open a server, it will be very painful to use TrinityCore to open a server-either you will never update and fix it alone, or you will keep updating and pay for TC’s continuous rewriting of the framework, redoing your own functions again and again Exhausted.
In this case, there was a server that chose the former, resulting in a stable, highly repaired end . This server is SunWell, referred to as sw. They used one of the versions of tc as the base, no longer chasing the update of TrinityCore, but focused on repairing and optimizing, so they got a terminal that exceeded the market average . However, excellent things need to be guarded by a mature human heart before they can be transformed into huge benefits. However, sw's tuand does not have a mature human heart, so after a period of time, the source code of sw was circulated. Of course, the degree of repair that can be spread is very low. After all, repair is not only a matter of the core, but also a matter of the database. But even so, the code flowing out of sw is enough to bring about a revolutionary impact.
So in a short period of time, there have been websites that update sw, and a lot of terminals that use sw . And TrinityCore was abandoned by people . However, the sw website is not equal to the sw database after all , nor is it mature and maintained by an organized tuand . After a period of time, it finally came to an end and was no longer updated.
After the demise of sw, the inspiration brought by sw did not disappear, so a new, organized and energetic tuand appeared. They take "developing to provide a better terminal " as their team concept, and they are AzerothCore, or az for short.
Just like sw, they choose a version of tc and stop chasing its version, while incorporating a lot of advanced parts of sw source code. This makes the source code update of AZ project followers reliable and stable, and it can be expected that the repair of AzerothCore will get better and better (although it has not exceeded the level that sw xx once had - and the level of source code outflow from the sw website has long been Beyond the).
At the same time, they designed a rough but simple module function, and hooks all over the kernel, so that most of xx 's characteristic functions can be made purely in the form of modules-this can improve the efficiency of bug fixes on the one hand , and more importantly, It can help each xx to easily follow the official update of AzerothCore and update without having to deal with a lot of conflicts every update. In this way, the xx level of the AzerothCore camp can be easily and continuously improved with the work of the AzerothCore tuand . Finally, because sw has stopped updating, and tc is always being updated, AzerothCore will also gradually include the advanced functions of tc, and add new things of tc on the basis of not always subverting the old framework like tc. This will certainly make az's function update progress far behind tc, but az's excellent stability and developability can make up for this regret. AzerothCore is still a freshman tuand
, developed module functions but there are no modules worth using, but today, AzerothCore's module ecology is very mature. There are many types and quantities of shared modules, and AzerothCore officially collects them regularly.
To sum up, in the 335 version, AzerothCore tuand is a tuand with gradually increasing advantages for both stand-alone players and xx server openers . So more and more secondary development Core products based on this tuand . And only developers who are very confident in their own technical ability and believe that they can maintain a series of people alone will choose a more stylish SW base, or a TC base with more black technology. However, in versions above 335, xx and developers have no choice. Because Madmax’s ren ability is limited, it is impossible to open Mango Four, Mango Five, and Mango Six with the official server version, and C Mango is struggling with 112 imitation officials. Therefore, TrinityCore, which pursues stronger technology, is the only choice—keeping up with the official server version is itself one of the technical challenges, and it is the direction TrinityCore chooses to face. Although for the high version, some things like AshamaneCore and AzerothCore have emerged based on a certain version of TC , but their tuand
It is not as strong as AzerothCore, and cannot reach the level of AzerothCore. It can only be said to be a slightly better choice than TC, and the advantage is not too great.
And AzerothCore itself only does 335.
As for versions like AC-Web, they all have their own bases. Generally speaking, it is based on TC in the early stage and AZ in the later stage.
Summary: The repair of TC is not as good as that of AZ. Whether it is from task repair, professional skill repair, dungeon repair, or field mob AI repair, the only difference
is the mission and mob AI. This is also understandable. TC is based on learning. Master, most of the repair tasks and mob ai are mysql data updates and I don’t care too much. What’s more important is that the new direction of tc is 9x, which is different from az’s focus on 335. It is naturally best to open the server az, after all, the maintenance iteration is more active. tc is equivalent to a framework, and az is a landing project. You must use az to open the server, and use tc if you want to learn by yourself and fully control this code. But if you have a c++ foundation, tc is the most comfortable to repair, because its code logic is more suitable for programming. If you don't have a foundation, az is more suitable for you, because there are big guys who can extract the mod and add it directly to run it.
This is the end of Aixi's story today, just listen to it, after all, it is too long-term and the specific situation is unknown