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.

Some questions have been posted regarding the stopcasting command in the World of Warcraft forums. Player Panacea has been having problems with the command, stating that the stopcasting command only works with every other cast, whether he used a macro or a clique addon.

Blizzard poster Slouken gave his suggestions and input on the matter and some clarifications about the command in Patch 2.3. Read Slouken's input in the full article.

A bug has been detected for World of Warcraft's macro mechanics. According to the report that's been picked up, the macro that allows gamers to dual-wield weapons is having problems recognizing the gear if their names are identical. Using the macro will only swap one weapon from the main hand to the off-hand, and vice-versa.

This problem's already been reported at the WoW forums. Check out the full article to see the full bug details, and Blizzard's official statement on when it will be fixed.

Community Manager Slouken gave word about some of the changes with the chat channels and the "/cast" and "/castsequence" commands in Blizzard's World of Warcraft Patch 2.3 on the Public Test Realms. He said that chat channels are now limited separately and that /cast and /castsequence will no longer toggle commands.

The changes are pretty good as they address some of the more common complaints from the players. Hunters will be particularly pleased by the /cast and /castsequence fixes as it allows them to properly use autoshot.

More information about the changes in the full article.

As most hunters would have probably realized by now, the standard shot rotation macro on Blizzard's World of Warcraft Public Test Realms 2.3 has not been working as expected. Community Manager Slouken has announced that the should be fixed in the next PTR update and the details on this will be announced later when the updated patch notes are released.

For those unfamiliar with the problem, the current macro most hunters are using is "/castsequence Steady Shot, Auto Shot."  This makes sure that Auto Shot always fires after every Steady Shot and maximizes the damage per second (DPS) of a hunter. In the current PTR build, Auto Shot never triggers when using this macro. It only toggles the skill on and off which means it never fires off a shot.

If players have to manually hot-key both skills, they will have to time every shot combination within a half-second to maximize their DPS. Considering hunters shoot thousands of shots in raids, this would be pretty much impossible. It's great that Blizzard has decided to fix this since it will allows hunters to retain their DPS party-role when patch 2.3.0 hits the retail realms.

It might be time to make adjustments to your favorite tracking macros, guys. As Cangoc over at World of Warcraft forums explained, something was up with his character's ability to tag target characters up to 60 yards away. Here was the player's full explanation:

This may not have been a recent change, but I remember that at 60 tab targeting almost always gave me the guy I was trying to get a hold of. Now it seems like it goes out of its way to pick the wrong target. I get guys behind me, guys way off through a wall, etc...anyone but the guy who's right freaking next to me who I'm trying to target.

Blizzard blue-texter Slouken dropped by a little later to explain that as of patch 2.3, the maximum targeting tab range was set at 50, not the 60 that Cangoc reported earlier. As we said earlier, guys who've been using similar parameters as Cangoc will want to keep Slouken's note in mind when patch 2.3 goes live.

If you've been playing on the Public Test Realm server of World of Warcraft and have been getting annoyed at the error messages which occasionally pop up, then you'll be happy to know that you can stop them from showing up on the left side of the screen.

Blizzard Community Manager Slouken on the official World of Warcraft forums told users who wanted to stop seeing error messages to input this command without quotations: "/console errors 0".  We do have to warn players who intend on using this, however, as the console command blocks all error messages, so you probably won't find out if you're having problems with your current set-up.

So try out the command and enjoy the "error message free" gameplay in World of Warcraft.

Players on Blizzard's World of Warcraft Public Test Realm Patch 2.3.0 have found that certain skills erase the bottom left contents of the action bar. This bug has been confirmed for warriors when they switch stances, rogues when they go into stealth mode, and even druids when they shapeshift.

Community Manager Slouken has announced that this problem will be fixed in the next test realm update, which will be going live sometime next week. Until the new PTR build goes live, players may want to refrain from keeping any of the essential skills in the first few slots of the action bar.

From all indications, the PTR patch 2.3.0 testing is going well. Hopefully, Blizzard can iron out most of the bugs soon so we can see Patch 2.3.0 in the actual realms.

 

If you've been having trouble lately with your UI while playing Blizzard's World of Warcraft MMORPG then it might be because of an AddOn you recently installed. However, Blizzard Poster Slouken has proposed some steps on how to identify and record the error through the in-game logs.

To first diagnose the problem, enter "/console taint Log1" in the chat window and restart the game. Try to reproduce the error and then quit the game afterwards so that you can look through the taint.log file in the Logs directory of your WoW folder. You can then turn off the logging system by typing: "/console taintLog 0" into the chat window.

Slouken gave out some helpful steps on how to interpret your taint.log file:

1. First look for a "blocked" message, note the AddOn that's listed there.
2. Search back for the last "Execution tainted" message, and it will probably have that AddOn listed.
3. See what variable was read to taint execution
4. Search back for a "Global variable" message involving that variable.
5. Look at the files and lines listed for each of these events.

Players can easily test out the "blocked" messages in combat by going to the nearest low-level zone and let a weak creature attack you while you test out actions such as targeting, group changes, pet changes, etc.

Slouken suggested that the results be posted on the thread that he posted on the WoW forums (accessed through the via link below). Details and suggestions why the taint was occurring on your client can be listed down on your post as well. As always, Blizzard suggests that people who use the MMORPG's AddOns update them constantly to avoid little errors like these.

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.