Earlier, we put up a post saying that World of Warcraft's 2.4.3 test patch would be coming soon. Well, the patch isn't quite here yet, but the announced changes for the patch are. Find the 2.4.3 PTR patch notes after the jump!

It's time for another bug report on Blizzard's World of Warcraft. This time around Faxmonkey from the Blackrock realm posted that Totemic Recall still has a global cooldown even if it was mentioned in the 2.4 patch that players can perform the exact function without a global cooldown.

He was wondering if this was intended or not by the developers. Blue poster Hortus was there to reply to this concern. Find out what he said after the jump!

If you've been playing Blizzard's World of Warcraft recently, then you might have noticed that there are quite a few bugs that the developers still need to iron-out. Before you go reporting the problems you've found on the forums, you might want to check out Blizzard QA Hortus' updated list of known issues for patch 2.3.3. For the list of the changes, head on over the full article.

Blizzard has just announced that the World of Warcraft Public Test Realms 2.3.3 patch has been released. Blizzard QA Wenzann posted in the U.S forums the things included within the patch: a few general changes on loading times and three bug fixes.

Read more on the patch notes in the full article.

As player Icki reported recently over at the World of Warcraft forums, there seems to be a serious bug with the Rogue class' shadowstep skill in the Test realms. The bug apparently enables rogues to literally shadowstep their way through different zones. More details on the bug are available in the full article.

In World of Warcraft, Nymbia observed that the GetBindingAction command was returning empty strings. Asking at the forums whether this was an intentional move by the developers, Blizzard Poster Slouken gave a quick reply saying that this bug is fixed in Patch 2.3.2.

Addon coders have to keep up with the times. Blizzard dishes out new changes like there's no tomorrow, and gladly it doesn't forget to update its mini developer kit for the World of Warcraft addon authors. Macro and UI community manager Slouken fired a broadside update at the World of Warcraft Forums, stating that the Interface AddOn Kit has been made compatible for patch 2.3.

And now that patch 2.3 is currently running on the Public Test Realms, this gives authors a chance to readjust their UI addons where necessary and play-test their builds before going to final or release versions.

First time addon coders might have to browse around the UI & Macros Forum before attempting anything drastic. A simple rearrangement of the interface would sound like a good start, but always remember to run the kit from the main installation directory of World of Warcraft.

Remember, it's not supposed to be run from the PTR directory (character files and accounts get mirrored there), but the main installation directory of World of Warcraft. Make the needed changes there, then run the addon in the PTR client for testing. Easier said than done.

It looks like Blizzard is working overtime churning up patches for its bestselling MMORPG, the World of Warcraft. Patch 2.2.2 has just gone up on the live realms and now patch 2.2.3 has gone live on the Public Test Realm (PTR).

Blizzard posters Hortus (on US Realms) and Salthem (on Europe Realms) made the announcement earlier, together with the patch notes:

Bug Fixes

• Clients utilizing OpenGL video modes will no longer experience graphical anomalies and missing textures after minimizing/maximizing the window.
• Fixed an issue that caused Fel Eye Stalks during the Legion Ring event to not despawn when the event is completed.
• Fixed an issue where zoning after mounting and summoning a pet was disconnecting players.
• Fixed an issue where the Shift key would get stuck in game.
• Using a /equip macro while affected by certain crowd control spells will no longer cause the items in the macro to be stuck in your inventory.
• Using very low values for SetScale() will no longer cause Mac users to disconnect from the game.
• Default sound channels have been changed from 12 to 32.
• Microphone resources will no longer be claimed by World of Warcraft when Voice Chat is disabled.
• Sounds will no longer stutter and pause if large amounts of creatures are being hit with AoE attacks from multiple sources.
• Sounds caused by spells cast on or by the player will now play more consistently.

Just bug fixes for this patch, and according to another stickied thread by Hortus, there will be no premades for patch 2.2.3. The blue poster made another thing clear - "There will be no authentication server update for 2.2.3". Here's what that means:

• If you have changed your password since July you may not be able to log into the test realms.
• If your account was inactive or banned in July you may not be able to log into the test realms.
• If you use pre-paid cards to fund your account you may not be able to log into the test realms.
• We expect the next Authentication update to be immediately prior to 2.3

Got all that? Go on over to the World of Warcraft PTR and do your part. In the meantime, we'll be checking out more WoW news so stay tuned.

The advent of the Logitech G15 keyboard can be considered an innovation to the gaming industry. This nifty gadget can be programmed to do things while away from the keyboard, thus presenting a big advantage to gamers who own the G15. The question: is the use of the Logitech G15 allowed in Blizzard's World of Warcraft? The answer: both yes and no.

The use of the keyboard is okay per se, however if the G15 is programmed to do stuff while the player is away, then that's where accounts get bannable. The key word, according to a blue post in the WoW forums, is "unattended".

A blue post by Issuntril illustrates the point well:

Indeed, the key word is "Unattended".

While I can certainly see the advantage of say, been able to create large amounts of water while away from your keyboard, this is still classed as automated play, and as such is against the Terms of Use.

In short, the keyboard should not be used to perform any action which a player cannot perform himself in-game using the regular macro interfaces. Obviously there is no in-game function which would allow you to cast multiple spells in the way you have specified, meaning it is not allowed with the keyboard.

So well, there you have it. Part of Logitech G15's tagline is The Logitech® G15 gives you a winning advantage, and everyone knows it’s more fun when you win, but players should take note that too much advantage just gives you the banhammer instead.

Among the discussions that goes into World of Warcraft, one topic that's gotten the attention of the devs is the matter of User Interface (UI). With that said, we'll be making mention of Cogwheel's post from months back, which detailed a comprehensive list of UI-related suggestions for the game by the players.

The post has recently gotten the attention of Slouken - Blizzard's resident UI guru - who replied with a series of comments on what UIs the Blizz devs would indeed be implementing in the upcoming patches.

Given that the list was scattered through various posts at the WoW Forums thread, we've got WoWInsider to thank for summarizing the list into one cohesive form. We'll start off with which UIs Blizzard has decided not to use:

• Declined:
• Generic /sequence command
• Spell Queuing
• Vendor value without being at a vendor
• API to retrieve DND or AFK status message from another player
• Finer-grained action button enable/disable events with some logic moved C-side
• /stopcasting
• /swapgroup
• Some way to iterate over the pet spell lists of pets you're not currently using (client doesn't have this information)
  
• In Patch 2.3
• Eliminate the need for /stopcasting in macros that have multiple instant, non-GCD spells
• /petautocasttoggle
• /targetlastenemy, /targetlastfriend
• There is a new Frame member function: registered = Frame:IsEventRegistered("event")
• There will be a function to query which frames are registered for an event: frame1, frame2, ... = GetFramesRegisteredForEvent("event")

View the full list plus a few notes right at the full article!