WoW Classic: Der PTR für Phase 5 wurde gestartet

WoW Classic: Der PTR für Phase 5 wurde gestartet
WoW Classic: Der PTR für Phase 5 wurde gestartet
User Rating: 4.7 (1 votes)

Nach mehreren Monaten des Wartens haben die Mitarbeiter von Blizzard Entertainment im Verlauf des gestrigen Abends nun endlich den öffentlichen Testserver für die klassische Spielversion von World of Warcraft reaktiviert und dadurch dann die Testphase für die fünfte Phase von WoW Classic offiziell gestartet. Wer nun gerne selbst an diesen interessanten Tests teilnehmen möchte, der muss in seinem Battle.Net Launcher einfach nur die Spielregion von World of Warcraft auf PTR: World of Warcraft Classic ändern und die für diesen umfangreichen Test benötigten Spieldaten herunterladen. Da die Spieldaten für die klassische Variante von WoW noch immer nicht besonders groß sind und der PTR und der Liveserver sich einige Daten teilen, sollte das Herunterladen und das Installieren der für den Testserver benötigten Inhalte selbst bei schlechteren Verbindungen recht schnell ablaufen.

Was die aktuell auf dem PTR vorhandenen Inhalte für WoW Classic betrifft, so wird dieses kommende Update endlich die finale Variante von Silithus, die beiden Schlachtzüge in Ahn’Qiraj und die Questreihe rund um Szepter der Sandstürme in der klassischen Spielversion freischalten. Die epische Questreihe mit dem Szepter und das damit verbundene serverweite Event sollten einen der Höhepunkte der Lebenszeit von WoW Classic darstellen und eine Reihe von Gilden auf die Jagd nach den notwendigen Ressourcen schicken. Zusätzlich zu den Inhalten in Silithus bringt die fünfte Phase unter anderem auch noch die Questreihen für die T 0.5 Rüstungssets, die zu Patch 1.10 gehörenden Anpassungen an den Beutetabellen von Dungeonbossen, umfangreiche Anpassungen für das Alteractal, die über einen Authenticator freischaltbare Erweiterung des Rucksacks und notwendige Veränderungen an der API für Addons mit sich.

Genauere Informationen zu dieser Testphase und Phase 5 von WoW Classic findet ihr in den folgenden PTR-Patchnotes.

 

PTR Patch Notes – WoW Classic Version 1.13.5:

The next patch and content unlocks for WoW Classic are now available for testing in the WoW Classic Public Test Realm (PTR).

Ahn’Qiraj

  • The 20-player raid zone, Ruins of Ahn’Qiraj is now open in the PTR and available for testing.
  • The 40-player raid zone, Temple of “Ahn’Qiraj will not be available for public testing. This raid will only be available after it is opened on each realm.
  • The “Sceptre” quest to open the gates is available for testing, however, when the gates are already open, it is not possible to trigger the gate-opening event on the PTR.

 

Content Updates

  • The Tier 0.5 dungeon questline, items, and vendor are now available.
  • This update makes Wizard Oil and Mana Oil available.
  • Abyss Crystals can now be rewarded from disenchanting epic items.
  • This update includes WoW patch 1.10 Dungeon loot table adjustments, increasing the drop chance of epic items, and many new caster DPS items.
  • Several Relics are now available.
  • Reputation rewards from Warsong Gulch, Alterac Valley, Thorium Brotherhood, and Timbermaw Hold vendors are updated.

 

Alterac Valley Updates
This patch includes many bugfixes for issues found in the 1.12 version of World of Warcraft. These were issues that were clearly unintended by the design of the time, and are now fixed:

  • Terrain exploits
    • You can no longer climb the waterfall and enter the Frostwolf base near the Relief Hut.
    • You can no longer climb the cliff and enter Dun Baldar near the Aid Station.
    • You can no longer bypass Icewing Bunker.
  • Reputation inconsistencies between Alliance and Horde
    • Alliance now always receive Reputation and Honor for defeating Captain Galvangar, regardless of whether Captain Balinda Stonehearth is alive.
    • Developers’ notes: This now correctly mirrors the Horde behavior, which grants them Reputation and Honor for defeating Captain Balinda Stonehearth, regardless of Galvangar’s status.
    • Alliance Druids can no longer have their actions disrupted by talking to them.
    • Developers’ notes: This now correctly mirrors the behavior of the Horde Elementalists, who were already just as steadfast in executing their intended actions.
  • Exploits for defeating the enemy general.
    • The Horde War Masters can no longer be kited far enough to allow General Drek’thar to be engaged and defeated alone.
    • The Alliance Prospector can no longer be tricked into pulling General Vandar Stormpike out of the bunker so that he can be defeated alone.
    • Developers’ notes: As always, our intention is to accurately represent the 1.12 design intent of the game, and these bugs are clear examples of behaviors that were never intended.

 

Addon APIs

Recently, we’ve seen an increase in the chat traffic generated by addons that synchronize data between their users. While the vast majority of addons do this responsibly, some can be problematic to the point of degrading the game service for all players. We’ve previously hotfixed the server-side of the game to incorporate chat throttles that work to alleviate some of this, but during our investigations, we found common use cases that we can improve for addon authors.

  • Threat
    The community has largely solved threat calculations, and has created robust tools for displaying this in-game. We’d like to improve the addon APIs so they can display this data in an addon without needing to transmit a great deal of chat traffic.
  • Larger combat log range
    We originally restricted the combat log range in the open world to prevent a larger radius of stealth detection than existed in original WoW, but this isn’t an issue in Dungeons and Raids. As a result, addon authors send a great deal of chat to synchronize combat events across the raid. In this patch, we’re increasing the combat log range in dungeons and raids so that damage meter addons can get accurate data without the chat traffic.

 

Authenticator Bag Slots

Since before WoW Classic was first launched, we’ve been very concerned with replicating the original experience while eliminating as many ways that accounts could be compromised as possible. We can’t eliminate them all, and unfortunately, many WoW Classic players have not yet taken steps to protect their account with an authenticator. That leads to difficulty for players when their account is compromised, and they need to contact Blizzard Customer Service to resolve the issue.

In this patch, we’re activating an additional 4 bag slots for any player who has an authenticator attached to their WoW Classic account. In order to help preserve the new-player experience for players who are new to Classic, this won’t be advertised in-game until you’ve reached level 20. Any player with an authenticator already attached to their WoW account will see the additional 4 slots on their backpack when they log into version 1.13.5, and any player who doesn’t will see an in-game “+” on their bag to remind them to secure their account for this reward.

We recognize this is a notable change from original WoW. Account security is very important to us, and we want the reward for securing your account to apply to WoW Classic, as it has applied to World of Warcraft for many years.

 

Bug Fixes

  • Fixed an interface error that occurred when generating a link to a Battle.net Community in-game.
  • Fixed an issue that caused some items with running or mount speed bonuses to not correctly stack multiplicatively.
  • Many large monsters and bosses are no longer missing certain combat sounds.
  • Fixed an issue that caused certain creatures and bosses to be missing screen shake effects during abilities, such as Onyxia’s Bellowing Roar.

These patch notes are a work-in-progress, and are subject to change before the patch goes live. The PTR may be taken down at any time for maintenance, and some content may be disabled or unavailable. We will publish dates for the patch and content unlocks as soon as they are finalized.

Please report bugs using the in-game bug report function. Thank you!

 

 

(via)

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

*

JustNetwork | Just! Stevinho
Registrieren
Username Passwort