OwnedCore Report #117 - #SomeChanges menu

User Tag List

Results 1 to 1 of 1
  1. #1
    Kenneth's Avatar OwnedCore News Correspondent WTB XRP Authenticator enabled
    Reputation
    1642
    Join Date
    Aug 2012
    Posts
    1,526
    Thanks G/R
    1062/788
    Trade Feedback
    8 (100%)
    Mentioned
    4 Post(s)
    Tagged
    0 Thread(s)

    OwnedCore Report #117 - #SomeChanges

    When Classic WoW first came out we had a movement called #NoChanges which basically meant "don't touch Classic WoW Blizzard, leave it as it is regardless of its faults." This was simply because the community who were die hard Classic fans didn't trust Blizzard anymore. They see retail and see an arcade slot machine version of the old and slow RPG they used to play as a kid. This did not last too long though. From the get go there were changes but they were warranted. Example being all loot being available from the start for your pre-raid bis instead of gradually adding it in so you horde pieces that will get buffed in the future instead of it just being in its buffed state from the get go. There was some blow back to this but most people understood that it was kind of dumb to farm bad gear just because you knew it would eventually become good gear. That's not the vanilla experience because you couldn't have authentically known it in 2005 either. Classic has been out for over 6 months now and Blizzard has been adding little qualities of life over its course and the community seems to have accepted it with open arms now. What happened? Where did #NoChanges go? I think gaming is a min-max culture now and with that comes the realization of just stupid things in the game that should just be fixed. Recently they added more Black Lotus spawns and spawn rates because the servers are much larger than they were in actual vanilla. The community welcomed this change. Now we have some new blue posts with new changes and things are definitely getting a little interesting.





    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.


    This is pretty big news. So AQ is being tested but not the 40 man version. A lot of people are excited about this. For starters ZG was kinda ruined by being able to fully test it before it ever came out according to many. The mystique was lost. AQ 40 not being tested at all is a massive move by Blizzard because now people won't know how scaled it will be. The talk of the town is "Will we get pre-nerf C'Thun?" . If you don't remember back in the real Vanilla days C'Thun was deemed mathematically unkillable and had to be nerfed before it was ever killed once. The question is...was it actually mathematically unkillable? A lot of people say no. With how min-maxed dps gear is in Classic WoW and formerly on private servers a lot of top end Classic raiders believe pre-nerf C'Thun would be smoked by players today. And who are we to disagree? One of, if not the, hardest boss ever in Classic WoW was deemed to be 5 Priest Hakkar. This means not killing any of the priests in ZG and going right to Hakkar. Each priest not killed buffs Hakkar and also adds that priests mechanics. This was thought to be impossible. Yet when ZG came out it 5 priest Hakkar was killed day one. That's right. Day One. Maybe Blizzard has more faith in us and are willing to scale C'Thun up a bit along with the rest of AQ40. The mystique of what a lot of people are calling the guild killer raid would be lost of many go in there and 1-2 shot the whole place.

    Another thing mentioned in Blizzard's blue post is that there will be no layering for the gate opening. This comes as a shock to some and expected to others. On one end the gates of AQ opening is a sacred event in Classic WoW. It's how the server comes together to open the raid as soon as possible but also battle it out to fund the future Scarab Lord. The flip side is if you've done any WPVP on a Tuesday in Blackrock Mountain than you know that these Classic servers cannot handle such large quantities of people in one area right now. It is a complete lag fest to put it simply. The solution may be in Blizzards recent post mentioning a stress test for this exact event.


    Please join us on the WoW Classic PTR at 3:00 p.m. PDT / 6:00 p.m. EDT / 11:59 p.m. CEST on Thursday, June 18 for a stress test. In order to prepare for the AQ opening event, we need to test several aspects of how the game service deals with very high capacities.

    Test Details

    First and foremost, we’d like to see a full realm with a queue of testers waiting to get onto the realm. This will allow us to consider tweaks to the total realm capacity. We’ll open the realm about an hour before the test so that everyone can copy over a character.

    Secondly, we’re going to test our technology for managing the number of players in Silithus. Make sure you’ve got a level 60 character (the PTR copy function will be available, as will template characters with rare quality Dungeon gear), and attempt to join your fellow testers in Silithus. Lower-level characters can also log into the realm, but they won’t be allowed into Silithus.

    If you don’t make it into Silithus, please keep trying to enter the zone. We’re going to start with a typical zone capacity, and then we’re going to increase the number of player-characters that are allowed in the zone.

    What to Expect

    For this event, we’re optimizing aspects of the game service that you will potentially see and feel. In order to maximize the number of players in Silithus, we have to make some sacrifices to things like buff and debuff updates, player movement, general server-to-client communication, and spells.

    We’ll begin testing the AQ opening event by initiating it automatically. Testers won’t have to do anything to make the event happen. This will go on for one hour.

    Some of the performance issues that we’re looking for will result from players running the game on different PC hardware that have different capacities. Your experience and the experience of another player with a much more powerful PC will vary.

    There will be lag. Despite the years of big improvements that have been made to hardware, software, and data throughput, we must accept that packing more and more players together in a small space causes an exponential (not linear) load on the game service.

    And of course, the game can port players out of the zone entirely, similar to how players were ported out of Silithus in original World of Warcraft. Just like we did in 2006, we consider that preferable to a crash.


    Layering

    Today, layering is enabled for some very popular realms, and we’ve engineered the AQ opening event to operate as expected on a realm with multiple layers. Nonetheless, our goal with these Silithus optimization efforts is to make the event run the best it can without adding layers to realms, and we do not plan to add more layers to any realms for the event.

    Please Join Us!

    We look forward to seeing you in Silithus on the WoW Classic PTR at 3:00 p.m. PDT / 6:00 p.m. EDT / 11:59 p.m. CEST on Thursday, June 18!;
    Botting in Classic WoW

    If you don't play Classic than you might not understand the botting situation. It is the wild wild west right now and Blizzard up until this point has done nothing about it. There have been hunters farming Azshara since September who are still there to this day. More recently, as seen in the video above, a lot of botters are now doing full blown instance carries such as ZG, Maraudon, and Strat. At first it seemed like it was just hired gold farmers playing on these mage accounts but recently it has gotten to the point of them abusing things such as fly hacks to complete these runs and put it in pure automation mode. One would assume Blizzard would crack down on the bots themselves but today they made a change that has screwed over the players more than the botters.

    As part of our ongoing efforts to eliminate exploitative and automated gameplay, with scheduled weekly maintenance in each region, we’re implementing the following change to our settings on all WoW Classic realms:
    You may now enter a maximum of 30 unique instances (dungeon and raid) per day, per realm. This restriction complements the current limit of 5 instances per hour. Now, when a player enters a dungeon or a raid, the game checks to see if they have entered 5 instances in the last hour or 30 instances in the last 24 hours, and if they have, they cannot enter the instance until enough time has elapsed. This check is across all of your characters on your realm.

    These limits only apply to dungeon and raid instances, and do not apply to PvP battlegrounds.
    That's right. So instead of killing the botting itself they have put a hard cap on instances PER ACCOUNT per day. This is terrible for the game. Some things this impacts.

    • Real mage carries.


    - Not every server is over ran with mage botters just yet. This means if you have a mage main or alt to make gold but also raid you have to be very careful as to how many instances you go into before a night of raiding or you might be locked out of raid. This goes double for guilds that clear BWL/MC/Ony/ZG in one night. Tanks want fire buff from UBRS before BWL? Have to now account for that as well .

    • Hunters farming DM


    - Like the first point there are legitimate hunters who play the game fair and just farm DM North Tribute runs all day for gold. These are now limited.

    • Jed Runs and others like it


    - Want to farm Briarwood reed on an alt? Want to farm SGC chest on your main? Good luck with this limit.

    • Feral Druids


    - This kills the class that has to work so hard to even be relevant in the first place. Ferals have to farm Gnomeregan for a mace that gives attack speed on use dozens of times before raid because that mace is the only thing that gives them enough damage to be viable in raid. Now? This instance cap completely screws them especially if they only had the time to do this Gnomeregan farm on raid day due to IRL or something.

    At the end of the day this is a band-aid fix to a shark bite. Blizzard should know better than to do this. Bot companies can easily make more bot accounts so if anything Blizz just makes more money off them instead of fixing the issue.

    AV Changes and Bag Space with Account Security

    Lastly were some good changes. AV has had major changes as far as exploitation. Some may consider this a little late but they are good changes nonetheless. On top of this Blizzard is increasing the 16 slot base bag "Traveler's Backpack" to 20 slots if you add an authenticator to your account. Nothing wrong with more bag space in my opinion. Here are the AV Changes.

    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.

    OwnedCore Report #117 - #SomeChanges

Similar Threads

  1. OwnedCore Report #4
    By Kenneth in forum OC News
    Replies: 0
    Last Post: 09-03-2017, 01:18 PM
  2. OwnedCore Report #3
    By Kenneth in forum OC News
    Replies: 2
    Last Post: 08-24-2017, 04:30 AM
  3. OwnedCore Report #2
    By Kenneth in forum OC News
    Replies: 5
    Last Post: 08-18-2017, 11:48 AM
All times are GMT -5. The time now is 02:39 PM. Powered by vBulletin® Version 4.2.3
Copyright © 2024 vBulletin Solutions, Inc. All rights reserved. User Alert System provided by Advanced User Tagging (Pro) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
Digital Point modules: Sphinx-based search