Slouken: PLAYER_REGEN_ENABLED bug fixed in patch 2.1

Posted Apr 5, 2007 at 1:59AM by Karl B. Listed in: Titles, News Tags: AFK, Blizzard, Slouken
Ó


World of Warcraft - Image 1


Another bug has reportedly been fixed for World of Warcraft patch 2.1. The bug in question concerns the PLAYER_REGEN_ENABLED event which, as pointed out by WoW forums member Trevion in the official WoW forums, does not fire when a player is in combat and leaves an instance. Here are a few observations posted by Trevion regarding the bug:

Enter an instance such as Stockade and enter combat with a mob, then exit the instance .. or simply /afk out of a BG while in combat. You will notice for a moment that InCombatLockdown() is true then it will switch to false but PLAYER_REGEN_ENABLED never fires. This could simply be a semantic problem, but if so is there an event for when the lockdown is about to begin and after it ends?

I have seen the following documented:

  • PLAYER_REGEN_DISABLED is sent before protected frames are locked down
  • PLAYER_REGEN_ENABLED is sent after protected frames are unlocked
and
  • PLAYER_REGEN_DISABLED : Fired whenever you get aggro, as normal regen rates are disabled during combat.
  • PLAYER_REGEN_ENABLED : Fired after ending combat, as regen rates return to normal. Useful for determining when a player has lost aggro.

Anyway, as we have said, the bug is now fixed for WoW 2.1. According to Blizzard poster Slouken, players will get PLAYER_REGEN_ENABLED before PLAYER_LEAVING_WORLD fires.

Via WoW Forums

 
 
 

Comments

No Comments, be the first to Comment

Add New Comment




You must be logged in to post comments




Add QJ.NET
Add to My Yahoo!
Google Reader Subscribe with Bloglines
Add  to your Kinja digest Subscribe in NewsGator Online
Subscribe with Pluck RSS reader Add 'www.qj.net' to Newsburst from CNET News.com
Subscribe with SearchFox RSS del.icio.us www.qj.net
Add to Technorati Favorite! Add to My AOL
furl! it Stumble for Treehugger!