PDA

View Full Version : RSS Ask the Devs Q&A #1 Answers



Azel
14/03/2011, 19:40
<div>Ask the Devs Q&A #1 Answers
<div class="bbcode_container"> <div class="bbcode_blizzquote"> <div class="blizzquote_container">
Originally Posted by Nethaera (Source (http://blue.mmo-champion.com/topic/163596/ask-the-devs-qa-1-answers))
<div class="message">Q: Will updated textures be applied to the Vanilla and TBC races in the future to coincide with the new Goblin and Worgen race textures? – Tank (Latin America), Welcome (North America/ANZ), Mizah (Europe [English])
A: The art team very much wants to update the older races. We feel like it’s something we owe the game and the players. We’re just looking for the right time to dive into that enormous task, without having to take too much time away from making new creatures or armor. We also have to be very careful to improve the graphics without fundamentally changing the way the models look. Players are quite attached to the look of their character, and they can be pretty sensitive to even small changes. We’re continually reminded of that fact.

Q: Are there any plans to update Outland and TBC zones to facilitate better level flow? – Atreydes (Latin America)
A: We think the flow of the zones works out well. It is true that you can finish the continents before hitting every zone because of the accelerated quest experience (further enhanced by mechanics such as heirlooms) but most players going back through the content on new characters seem perfectly happy to get through it faster than they did with their original character. What we don’t like is the strange way you go back in time when you go to Outland and Northrend and then back to the future (heh) when you go to the level 80-85 zones. That is definitely something we want to fix.


A similar but slightly different question was asked by one of our Russian players:

<b>Q: Will the Outland and Northrend be “renewed”? Will there be new quests? -

Fonte (http://www.mmo-champion.com/threads/868342-Ask-the-Devs-Q-amp-A-1-Answers?goto=newpost)