{"id":8583,"date":"2018-06-16T12:07:12","date_gmt":"2018-06-16T10:07:12","guid":{"rendered":"https:\/\/spielepost.de\/?p=8583"},"modified":"2018-06-17T18:34:10","modified_gmt":"2018-06-17T16:34:10","slug":"world-of-warcraft-einblick-in-die-probleme-beim-classic-server-projekt","status":"publish","type":"post","link":"https:\/\/spielepost.de\/en\/world-of-warcraft-insight-into-the-problems-with-the-classic-server-project\/","title":{"rendered":"World of Warcraft - Insight into the problems with the Classic Server project"},"content":{"rendered":"

In a fairly detailed blog, the World of Warcraft<\/strong> Developers given insight into the status of the Classic project.<\/p>\n

The community had long wanted classic World of Warcraft servers. Various fan projects with illegal servers simulated the experience, but could never offer the full program or were closed by Blizzard due to copyright infringements.<\/p>\n

Last year on the BlizzCon<\/strong> there was finally the official announcement that Blizzard would tackle World of Warcraft Classic.<\/p>\n

World of Warcraft Classic - A huge project<\/h2>\n

However, the project is more extensive than some might think and the team is writing about it.<\/p>\n

Even if some laypeople simply imagine setting up a server, backup of the program code from WoW 1.0<\/strong> search from the archive and upload and end. Unfortunately, it doesn't work that simple.<\/p>\n

\u201cBack then\u201d there was not only a completely different hardware, but the operating systems have since changed from 32 to 64 bits. Not to mention the support of modern graphics cards.<\/p>\n

So the team didn't just have to choose the entry point, Patch 1.12: Drums of War,<\/strong> but also bring the program code to today's level. Also, the current programming tools from Blizzard are very different nowadays. For example, the login system or anti-cheater measures look very different today.<\/p>\n


\n