6.2.4 Lua API Changes

Interface and Macros
1 2 3 41 Next
In the upcoming Patch 6.2.4, we're moving to a new Battle.net infrastructure. There are changes to many of the Battle.net-related Lua APIs, including Battle.net friends and Battle.net chat. If you maintain an AddOn that makes use of those features, you may want to log in to the PTR and test that your AddOn still functions correctly. To help AddOn authors troubleshoot potential compatibility issues, we’ve highlighted a few of the big changes to help direct you to areas that may need your attention.

Conversations
Support for conversations has been removed. This includes all C-functions (BNCreateConversation, BNGetConversationInfo, etc.) as well as all Lua/XML references to conversations.

Toons
The new Battle.net architecture doesn’t have the concept of “Toons”. Instead, we refer to “GameAccounts”. As a result, many functions with “Toon” in the name now refer to “GameAccount”
Examples:
BNGetToonInfo -> BNGetGameAccountInfo
BNGetFriendToonInfo -> BNGetFriendGameAccountInfo
BNGetNumFriendToons -> BNGetNumFriendGameAccounts

Presence IDs
Previously, “Presence IDs” could refer to either Battle.net accounts or individual toons. Most functions were able to accept either type of presence ID and, when passed the wrong type, tried to guess at what you were trying to do.

Presence IDs have been replaced with bnetIDAccount and bnetIDGameAccount. With this change, we’ve made all functions strict about whether they accept Account IDs or Game Account IDs. In order to make this easier, all Lua variables have been updated to specify which type of ID they are.

You can translate from a bnetIDGameAccount to a bnetIDAccount as follows:
bnetIDAccount = select(17, BNGetGameAccountInfo(bnetIDGameAccount));
You can find a player’s active bnetIDGameAccount from a bnetIDAccount as follows:
bnetIDGameAccount = select(6, BNGetFriendInfoByID(bnetIDAccount));
Current Realm Name
The “realmName” CVar no longer exists. You can get the name of the current realm using GetRealmName().
<3
03/03/2016 10:23Posted by Aerythlea
Support for conversations has been removed. This includes all C-functions (BNCreateConversation, BNGetConversationInfo, etc.) as well as all Lua/XML references to conversations.


Wait, what? Does this mean we can't have the chats with 3-4 of our friends all in the same chat room?
Because, if so, that means cross-faction RP is dead where you need multiple people in the same conversation
Seems so. IIRC only WoW could make conversations, if someone was logged from the Battle.net client they could not join.
Rest in peace cross faction rp :/
Revert the conversation change. You're going to have an angry RP community on your hands.
I think not only RP people right? I mean if you made friends from the opposite faction that means you can't talk with them anymore?
03/03/2016 13:41Posted by Shéele
I think not only RP people right? I mean if you made friends from the opposite faction that means you can't talk with them anymore?


Not if you want to talk with 2 other people at the same time in one chat room thing.
WHY are these changes being made? Cross-faction RP was made possible with this and now you'll simply remove it? Again, WHY?
If you're going to remove this feature can we just scrap the Alliance/Horde language barrier?

Seeings as you all want us on the same side against the Legion, right?
I'm a sad panda now, a lot of my rp is cross faction :(
+1 from me for language barrier removal if you're going down this route.
Yeah! Ditch the Language Barrier! First you've dropped it for Demon Hunters in their class hall, and NPCs ignore it all the time, so why not for everyone else?
So basically you're taking away cross faction communication with several people unless you're a StarCraft player capable of micro at 170 APM to be able to handle 4 people chatting together instead of being in a single chat room?

SHAME *rings bell*

As said above, just take away some more restrictions when it comes to the language barrier if this is where we're headed.
1-upping Moppentoff's post =/.
I really hope this means that Common becomes Common for all factions because otherwise you've just driven a very huge stick through roleplay of neutral factions.
Unless this is soon going to result in removing the language barrier, this is just a massive middle finger to the RP community.
Why not remove the language barrier if you're at it?
This will most likely destroy a huge part of cross faction RP.

As Ursarvis said, Nelf and Belf Demon Hunters can talk to eachother in their class hall.
NPCs can talk to whomever they like so it's quite useless to keep up the language barrier for players.

I say, Blizzard, tear down that barrier!
http://24.media.tumblr.com/tumblr_m7rux0xMLg1rbpxypo1_400.png
Since my fellow rp'ers have already made their points from our point of view, I'll do it for the non-rp'ers. They too might want to chat with multiple people from other factions or servers, why would you want to take that away?

Join the Conversation

Return to Forum