Jump to content
Sign in to follow this  

Kwee Q. Peddlefeet Will Despawn in Patch 1.13.5

Recommended Posts


Even though Love is in the Air 2020 ended some time ago in WoW Classic, players are still able to get the +200 Health buff from Kwee. Blizzard looked into this and found the very same bug present on the reference server, but they also confirmed that it was originally intended for Kwee to despawn after a week, so they are fixing this in Patch 1.13.5.

Blizzard Logo(Source)

Heard a rumour he was still handing out buffs. Working as intended?

Story time! Gather 'round if you’d like to hear some fun history.

When the 2020 edition of Love is in the Air ended in WoW Classic, we noticed a behavior we didn’t all expect: the faction leader that won the popularity contest continued to have Kwee Q. Peddlefeet in front of them, and you could continue to target Kwee and /kiss in order to get a +200 HP buff.

We looked into this, and it appeared that this was authentic behavior. We looked at the holiday data and we tested it on our reference server, and we got the same results. In original WoW, Kwee Q. Peddlefeet was first designed to stay with the winner of the popularity content for a full year, up until the start of the next Love is in the Air.

But we then asked around (and read some posts online, both new and very old), and found people who believed that Kwee was only supposed to hang out with the winning leader for one week after the end of Love is in the Air. One of these was the original designer of the event, who happens to still work on World of Warcraft, and he enabled us to dig more deeply into it.

In data, it turned out that there was indeed a case to be made for Kwee despawning after a week. The main indicator for that was an old bug that was recorded in the case the event ended in a tie. That bug was from 2006. We found other clues in a bug where on on three EU realms only (Anub’arak, Rashgarroth, and Ysondre BTW), there were Valentine’s Day decorations still present in Stormwind Castle for much longer than expected in 2007.

Reading those contemporaneous notes leads us to this conclusion: the designers’ intention was that Kwee would persist for one week after Love is in the Air ended, but it took some bugfixing to make that always the case. Kwee’s behavior was probably inconsistent on different realms, and game masters may have done the clean-up by hand in 2006 on different realms. Of course, the only reason they would have done that would have been that someone told them that Kwee wasn’t intended to be up forever.

By implementing WoW Classic as we did, we’ve re-created an experience that some realms had in 2006.

So, in this next patch (1.13.5), we’re bringing the related bugfixes to WoW Classic. The design intention was:

2/11: Love is in the Air begins, voting can begin.
2/16: Love is in the Air ends, voting ends, a winner is declared, and the victorious Kwee stands by them.
2/23: The victorious Kwee can no longer respawn, which means he won’t re-appear after the next Tuesday reset.

And that’s how it will go next time.

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Starym
      After the sudden and tragic passing of well-known streamer and personality Byron "Reckful" Bernstein, in addition to basically the entire WoW community paying their respects on twitter, facebook etc, we now also have some really amazing reactions in-game as well. While there were plenty of wonderful threads on retail WoW as well, the response in Classic was special. Many, many servers have seen gatherings of players paying their respects in the Cathedral of Light in Stormwind, or in Grommash Hold in Orgrimmar.
      It is truly heartwarming to see such kindness and respect, and somehow it seems even more fitting when it's presented in the game itself. We join everyone in the WoW community in mourning the loss of Reckful, and are very thankful and impressed by the dedication all of these players showed by honoring their fallen brother.
      Many more people than presented here showed up, but these are just some of the images that were captured and still showcase the tremendous support shown.
      Sulfuras, Alliance and Horde:
      Faerlina, Heartseeker:
      Grobbulus, Bigglesworth:
      Mankirk, Nethergarde Keep:
      Shazzrah, Zandalari Tribe:
      Herod, Kromcrush:
      Razorgore, Gehennas:
      Mograine Alliance:

       Mograine Horde:
      It didn't matter how many people actually attended, the thought itself is still truly an amazing one:
      Atiesh, Deviate Delight:
    • By Starym
      Here comes another addition to the "not a bug" list, as Blizzard have clarified that the extra elemental damage from weapons like Thunderfury or Warblade of Caer Darrow, while weird, is working as intended, aka like it did in Classic. Check out the detailed description explaining how it's actually logged as physical damage, but still affected by things like elemental protection potions:
      Elemental Damage (source)
      We wanted to take a moment to clarify that the extra elemental damage from weapons such as Thunderfury, Blessed Blade of the Windseeker, Iceblade Hacker, and Warblade of Caer Darrow are behaving as expected in WoW Classic and do not actually cause additional non-physical damage to the target. They do however still inflict extra damage in the amount specified in the tooltips. This is not noted in the combat log separately and is simply calculated as additional physical damage added to the weapon’s attack.
      That being said, it has been noticed by players that when using an elemental barrier such as a nature/frost/fire protection potion or a shield that absorbs a specific element, you will see an “absorbed (X)” message in the combat log. This is also correct and working as expected, and such effects will reduce the damage of attacks by such weapons by the amount of extra elemental damage specified in the weapon tooltip.
      Ultimately the way these weapons function is a very old quirk/bug with how original World of Warcraft was built. While definitely strange and unintuitive, these weapons are behaving exactly as they did in the original game and we have no intention of changing them to behave differently in WoW Classic.
      I hope this helps provide some clarity around this very odd quirk inherent to these types of weapons!
    • By Starym
      With the Gates of Ahn'Qiraj event coming up in Phase 5 later this month, there's a lot more focus on realm transfers, as entire groups/guilds might be going for that Scarab Lord title and mount on a low pop server. Today we have some clarifications from Blizzard on how realm transfers are going to work, specifically for those chasing the Scarab Lord title, noting that you cannot get the rewards from finishing the quest line for 90 days after transferring.
      Realm Transfers (source)
      With the upcoming Ahn’Qiraj event in WoW Classic, we’ve seen players discussing transferring to a different server to become the Scarab Lord. We’d like to clarify that there is a 90-day period following a character transfer, during which a player is prevented from opening the gates and obtaining the mount.
      If you transfer to another realm, you will still be able to complete the quest within 90 days of the transfer, however, you will not receive the rewards associated with being the first to turn it in. We want to allow players to transfer, but that should be so they can play with their friends, not disrupt another realm’s Scepter race.
      We hope this clears up the concern.
    • By Starym
      Blizzard shared more thoughts about bots and their banning thereof, specifically the fact that they've been removing more and more bot accounts, even after the big banwave from earlier this month, with as many as 40,000 more having been removed since then, across all regions.

      This all comes after a statement of intent against botting, which wasn't taken very seriously by the community, which was then followed by a 30 instances a day limit, and then the 74,000 account banwave (which was actually a cumulative total from a few months).
      Actions Against Exploitation (source)
      Since the launch of WoW Classic, we’ve taken action daily against accounts that were botting, hacking, and selling in-game services for real money. This continual effort has resulted in the average daily number of accounts actioned consistently increasing in the Americas, EU, Korea, and Taiwan. In May of this year, we witnessed a surge in the number of botters, and our intensification of efforts to eliminate them brought our average of actioned accounts upwards into the thousands per day.
      Since our last post about this issue on June 17, we’ve continued to remove exploiters at a high pace, typically 2,000-3,000 per day, with over 4,000 accounts actioned on some days. This daily effort has resulted in actions taken against over 40,000 accounts since June 17 in the Americas, EU, Korea, and Taiwan.
      We’re dedicated to driving the the exploiters away wherever we can, as we continue to make our response to this one of our highest priorities. This is a long-term effort that becomes continuously more difficult, as exploits and those who use them are driven by real money profit motives. We take action constantly, 24/7, to enforce the Blizzard End-User License Agreement. Any account that violates or assists others in violating license limitations on hacking, cheating, and other unauthorized use of the game is subject to suspension and removal.
      As always, we greatly appreciate your reports. Player reports have been and will remain highly valuable to us, as we must evolve our detection and response methods to stay ahead of the organizations who would otherwise degrade the game for legitimate players.
      Thank you very much.
    • By Starym
      After some confusion over why the majority of nature resist gear wasn't available either before or during the AQ patch, Blizzard have replied with the exact times the gear was implemented and why, as well as provided a list of the specific items that won't be coming with the next phase and patch, as they were always intended as catch-up gear introduced in Naxxramas for people to more easily clear AQ.
      Nature Resist Gear (source)
      Overall, the nature-resist gear that was released in original WoW in patch 1.11 was catch-up gear. It was released along with Naxx to help close the gap for guilds who were still dealing with trying to get certain pieces from Green Dragons and Maraudon because they were stuck on Huhuran.
      To be specific, here’s a list of pieces that are not in WoW Classic 1.13.5:
      Type Name Source Plate Ironvine Belt Blacksmithing Plate Ironvine Gloves Blacksmithing Plate Ironvine Breastplate Blacksmithing Leather Bramblewood Belt Leatherworking Leather Bramblewood Boots Leatherworking Leather Bramblewood Helm Leatherworking Head/Leg Ench Savage Guard Quest (Zandalar) Ring Band of Cenarius Quest: A Humble Offering Cloth Sylvan Shoulders Tailoring Cloth Sylvan Crown Tailoring Back Gaea’s Embrace Tailoring Cloth Sylvan Vest Tailoring We’re still considering precisely when to release this gear, given their usefulness and purpose. As with original WoW, that time will come later, after AQ is opened and being raided.
  • Create New...