Jump to content
FORUMS
Sign in to follow this  
Starym

Rallying Cry of the Dragonslayer Resets to Stay as They Are for Now

Recommended Posts

hAdGCz5.jpg
 

This is a pretty weird and very specific one: a lot of people have been resetting the Rallying Cry of the Dragonslayer buff you get from killing Onyxia or Nefarian and getting to reuse the heads again. This is being done by a Priest of the opposing faction mind controlling the npc mid-event and then the players who started the event killing him. In case you weren't aware, the heads from the bosses only drop for the first kill and there's a possibility of a shortage on servers, so this technique is very useful.

The blue response is a lengthy and very informative one, basically stating that this could become a problem for several reasons, was definitely possible in Vanilla, but won't be changed for now:

Blizzard LogoRallying Cry (source)

We’ve recently seen an increase in concerns about players resetting the Rallying Cry of the Dragonslayer buff by killing the associated NPC.

It’s important to note that this behavior is accurate to original WoW, and was possible in 2005 and 2006. Nonetheless, it’s the sort of thing that wasn’t widespread back then, and we believe that if it had been, it would have been addressed. In general, cross-faction collusion is antithetical to WoW gameplay, and the specific circumstance where players pay a member of the opposing faction help them kill their ally feels inappropriate.

There’s a related concern here – it’s entirely possible for players (who don’t know what their allies are doing or want to police what their allies are doing) to kill the hired priest, and then find themselves in conflict with their own faction-mates. We don’t like to see these sorts of hostilities within a faction of players.

Nonetheless, any change to WoW Classic has to be very carefully considered, so for the time being, we’re going to leave this functionality in place. We will continue to monitor this situation, and we may have to change it in the future. We will not suspend players for resetting the buff or attempting to prevent others from doing so. We will continue to take action against players who send hostile or offensive chat messages.

Thank you for your feedback on this.

 

Share this post


Link to post
Share on other sites

So " In case you weren't aware, the heads from the bosses only drop for the first kill and there's a possibility of a shortage on servers, so this technique is very useful." Isn't totally true. The heads drop EVERY time you kill them, you just can only turn in the quest once per character.

The shortage is that eventually everyone will have turned the head in and that is where the choke point is, because you need to have someone at the level for the quest. The real use of the reset cutting the CD out so that the raid group going at 7 can drop theirs then a group going at 8 can drop too. Often times heavy population servers are fighting the CD more than they are a shortage of heads to drop.

I think this will be changed, because just like honor farming pre-mades, the modern community doesn't let "silly" bugs like this rest without min-maxing and spreading them. The game hasn't changed, the way we approach games absolutely has.

Share this post


Link to post
Share on other sites
58 minutes ago, Laragon said:

The game hasn't changed, the way we approach games absolutely has.

Sort of a jump-off from your statement, but it made me think about the fallacy Classic puts forth:

The thing people sought from Classic was never really a product, they really longed for their past; an individually specific, emotional response to experiencing a life-changing adventure for the first time. The concept of recreating that original experience is as artificial as Jurassic Park.

When Classic was announced, I knew it would be a legitimate product. I also knew it was a pacifier for those who would chase that first-time feeling forever, even if it meant always resenting the most recent manifestation of their beloved alternate universe. By creating Classic, Blizzard was able to segregate this perpetually dissenting portion of the player base into their own contained environment.

I think the community at large is better off.

  • Like 2

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.

Guest
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.

Loading...
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Stan
      Some WoW Classic realms are experiencing long queue times these days and Blizzard revealed they've been working on bringing some relief from the queues to these realms in the near future.
      Firemaw (EU), Incendius (US), and Faerlina (US) currently have extremely long queue times rendering many players unable to join raids unless they log into the game 3 or more hours before raid start.

      Incendius queue times posted by redditor Omgzjustin. [Source]

      Faerlina queue times. [Source]
      Blizzard today said they're working on rolling some changes to reduce the queue times, so either they will offer Free Character Moves from select realms or increase server capacity. More details will be available soon.
      Placeholder for tweet 1246211466266435584
    • By Stan
      Onyxia has been recently defeated in WoW Classic by a raid group comprised of Druids only.
      Reddit user fouronnes and his raid with 32 other Druids have downed Onyxia in WoW Classic.

      Twitch Clip

      Logs
      The raid was able to defeat the boss in a little over 10 minutes. Logs can be accessed by clicking on the image below.

      Source)
    • By Stan
      Queue times return to some WoW Classic realms with a high population amid the coronavirus lockdown and character transfers. Firemaw (EU) players report 3-4 hour queue times on a Sunday, urging Blizzard to lock the realm and a similar situation is occurring on Incendius (US).
      Redditor ANTRagnarok came up with a graph while waiting in the queue and it turns out you must log in at 4:45 p.m. if you want to make it to the raid that begins at 7:30 p.m.

      Players are urging Blizzard to lock Firemaw (EU) on the official forums and offer free character transfers, as many do not want to transfer to different realms using the paid character service.
      The situation was apparently worse the day before with queues exceeding 3,000 players which resulted in 5-6 hour queue times. Redditor Aoussar123 reports that people are idling in cities hitting the space bar every once in a while to stay logged in which makes things even worse.

      Incendius (US) is facing a similar situation, but the queues aren't as bad as in Europe. The realm was beyond capacity full even before paid character services, then came transfers from Faerlina, Skeram, and other realms, rendering Indencius beyond unplayable according to Redditors. Players reported 2-3 hour queue times on Incendius during raid time.
      Blizzard has so far not responded to any of the reports and we will keep you updated should they come up with any solutions in the near future.
    • By Stan
      UPDATE: The issue has now been resolved.
      Blizzard (Source)
      The aforementioned fix was completed with restarts at 6:00 a.m. AEDT, and the Battleground Holiday has been operating as expected on Oceanic realms since then. The first Battleground Holiday has been delayed in Oceania due to a bug. Blizzard is currently working on a fix that may require Classic realm restarts.
      Blizzard (Source)
      The first Battleground Holiday should have gotten underway on Oceanic realms at 12:01 a.m. AEDT (about 4.5 hours ago). That has not yet happened, due to a bug.
      We’re working on a fix, and the fix may require realm restarts of Oceanic Realms, which we would undertake very soon if necessary.
      We apologize for the delay.
    • By Stan
      Blizzard today announced they suspended numerous WoW Classic players that were found to be using anti-AFK cheats or bots that automated movement, mainly in Alterac Valley.
      Anything that degrades the gaming experience for other players will result in harsh penalties, according to Blizzard, and they will continue to issue suspensions based on player reports, so if you see someone circumvent AFK rules, make sure to report them!
      Blizzard (Source)
      Yesterday, we issued numerous suspensions to WoW accounts that were found to be violating our Code of Conduct. Affected players were e-mailed with details about the violation and suspension – a great many of which were found to be using anti-AFK cheats or bots that automate movement, especially in Alterac Valley.
      This was the most-recent in a series of similar actions we’ve taken to address unfair gameplay in WoW Classic.
      Please be reminded that using third-party programs to automate any facet of the game, exploiting bugs, or engaging in any activity that grants an unfair advantage is considered cheating. Exploiting other players is an equally serious offense. Scamming, account sharing, win-trading, and anything else that may degrade the gaming experience for other players will receive harsh penalties.
      We’ll continue to monitor reports of and take actions against players who circumvent AFK rules. If you come across a player violating the Code of Conduct policies, please report them.
      Thank you.
×
×
  • Create New...