WoD alpha diffs (by kd3)
 

kd3 is sending diffs to the mailing list, but afaik they are not posted here on WoWI
I'm going to go ahead and share them and maybe some useful links

http://wowpedia.org/Patch_6.0.1/API_changes
http://www.mmo-champion.com/threads/...22-API-Changes

I also have a beta branch of the wow-ui-source and the wow-ui-textures on github
https://github.com/Gethe/wow-ui-source/tree/beta
https://github.com/Gethe/wow-ui-textures/tree/beta

This may not be entirely be unique to WoD, but why did Blizzard start naming most of their API C_Something?
C_Garrisons, C_Timers, C_LFGList, C_MountJournal...

Organizational purposes, I'd guess is the primary reason. This way they can put all the mount journal functions in a single global (the C_MountJournal table), rather than making them all globals in their own right, and it's a clear indicator that those functions are all part of a group. On the backend, the mount journal API may even be a separate module of some kind, but I don't really know about that.

The "C_" prefix on all those tables is just a naming convention, so it's obvious when you see something named "C_MountJournal" that it's pointing to stuff on the C backend (in this case, API functions), whereas something named "MountJournal" is probably pointing to something in the Lua UI frontend (like a frame or a simple Lua table).

The C_Timer functions will get used a lot.

Is anyone else having problems with the console command 'ExportInterfaceFiles code'? It seems to be a valid command but it drops to next prompt instantly (on live clients there's a small delay while it writes) and I don't see anything created.

Has anyone heard any news on beta keys for addon developers? We could use having some time to update the mods before launch :P

They don't usually enable addons until near the end of the beta cycle so until I can finish downloading it, I asume it's the same for WoD. By that time many more people will have access.

Yeah it's disabled at the moment. They will likely turn it back on when they enable addons.

Yeah you're right, forgot about that detail. /facepalm

C_Timer makes me happy.

The Addon Button is there and it lists the addons I copied into the game folder but they are showing as insecure and by the delay logging in with them ticked .. I am guessing it's probably not a good idea to activate them.

edit: It also looks like they have added the ability to enable/disable addons while in game and changes the Okay button to ReloadUI if you change them.

The AddOns button is there and I can see the list of my addons, but they don't seem to be loaded and some of the other addon-related functionality is not working. The /dump command does nothing and /script displays a reminder:
Oh well. So much for playing with my addons.

There was a Blizzard post on their forums saying they expect to enable addons around the time they start testing raids.

Edit: Link to the post by Zarhym

Perfect, thanks for the link.

Well, that argument goes a bit to waste with the new C_Timer, which is partly implemented in Lua. Unless they expect to rewrite C_Timer.NewTicker in C before release (I doubt), it does not make much sense and the "C_" prefix simply becomes additional bloat on the code.

In any case, C_Timer is awesome!

Does anyone know whether addon authors need an active account this time, for WoD beta access?

Hard to say, me and one of my brothers have access and my other brother didn't, all of us having active accounts. My friend who cancelled his account didn't get access. None of my other friends have commented either way for me to discern a more precise pattern.

Pattern for me: Invite on my active account. No invite on my inactive account.

Hmm, maybe. I have 3 US accounts and 1 EU account but only active one is a US account which is the one that had it activated.

I tought the C_ prefix stands for the class.