The pandaren race dances in Mist of Pandaria [Beta] + Origin of the dances

Finally, blizzard decided to add in the latest Beta build (15668) the racial dances for the pandaren class
Here are videos showing the dancing pandas and the origin of the mentioned dances.

The female Pandaren dance is the famous Caramell Dansen dance...



Carameldansen:


The male Pandaren dance is a copy of the famous pop-dance called 'shufflin'. Just by watching it I can hear the song "Every day I'm shufflin' " in my head...


Shufflin:



And here is a good retrospective video, a mix of both dances.



My thoughts about this? LOL, EPIC WIN OFC! :D But srsly, the panda female dance is kawaii, and yes, all of you panda haters who think that the hordes shouldn't be cute and fuzzy... go check the female blood elfs. Topic closed.

How to enable your own Mist of Pandaria addons on any Beta Build

Main exe file: http://dl.dropbox.com/u/12654979/EnableAddons.exe
virus scan: https://www.virustotal.com/file/6ce4...is/1336224936/

source code: http://dl.dropbox.com/u/12654979/EnableAddons.cpp

Just run the exe and it will patch any open wow.exe it finds.
Also, note that the addon api is a bit incomplete atm (several functions seem to be either missing or renamed) so don't expect all your addons to run flawlessly.

Updated to a (hopefully) build independent version (thanks to TOM_RUS for the pattern)
Or if You prefer a permanently patched wow.exe look at this method (thanks to Ssateneth):
Credits go to TOM_RUS for new EXE's and oprime for pattern and patch bytes as usual.

32-bit WoW build 15662 with addons enabled download HERE and VIRUSTOTAL
32-bit WoW build 15662 with addons enabled and LUA Hack download HERE and VIRUSTOTAL
64-bit WoW build 15662 with addons enabled download HERE and VIRUSTOTAL

These files are not patchers, put them directly in your wow.exe folder and run them.

Hex-edited version of _Mike 's program 15662 Filebeam - download

Read all about it at the OwnedCore forums .

How to enable your own addons in MoP Beta Build 15589

To be able to use your own Addons:
exe: http://dl.dropbox.com/u/12654979/EnableAddons.exe
virus scan: https://www.virustotal.com/file/bf4e...is/1333716623/

source: http://dl.dropbox.com/u/12654979/EnableAddons.cpp

Just run the exe and it will patch any open wow.exe it finds.
Also, note that the addon api is a bit incomplete atm (several functions seem to be either missing or renamed) so don't expect all your addons to run flawlessly.

Updated for 15589

Source topic

Or you can use your favorite hex editor and edit wow.exe directly: search for sequence: 0x8B, 0x47, 0x24, 0x83, 0xF8, 0x02, 0x75 and replace first 3 bytes of it (0x8B, 0x47, 0x24) with 0x33, 0xC0, 0x90.
Make sure to create backup before editing.

Update for 15781 (x86): DepositFiles
Virustotal (WoW_15781_addonfix.exe): https://www.virustotal.com/file/b05c...is/1340267478/

Update for 15781 (x64): DepositFiles
Virustotal (WoW-64_15781_addonfix.exe): https://www.virustotal.com/file/88b2...is/1340267496/


Edit: Blizzard already enabled AddOns support long time ago (~patch 156xx).

[Fix] MoP beta - Crash fix for build 15640

Modified Wow.exe with most common crash in recent beta build fixed: Download

Lets hope blizzard won't miss NULL pointer checks next time.

Creator: TOM_RUS (mangos founder)
Original topic: here  and also here(ru).
Blue posts  about it: here


This fix fixes the stability issues in the 15640 MoP Beta build.

As far as I know the issue with the bad stability and missing pointer is fixed in the 15650 build. Just patch up your client. If you see all realms red, in means that you need to patch your wow client to the latest build, just run launcher.exe. If you get any error, just read any of my other blog posts on how to fix that.

The problem should have been fixed in Build 15650.

How to fix WoW Launcher: "Error: The file Localization.xml" could not be loaded."

Right click on the Launcher.exe or the shortcut and select Run as Administrator.
Done! That worked for me.
If it doesn't work for you, you can delete the Cache folder (World of Warcraft\Cache) and try again.
Another way would be to close the Agent.exe process.