I have tried to latest version of Recount in MoP Beta and it will not update past the initial number. There are a ton of LUA errors and I have to turn off the LUA Errors reporting. Not sure what's going on, but it's the only add-on I have installed as well.
Thanks for this. Looks like Blizzard added an execution time check for lua functions, but that check is bugged on macs and not on PCs. Based on the kinds of reports I have seen, my current assumption is that Recount's function calls do fall into the allowable time-frame on typical systems. I will monitor the situation to see if that assumptions holds.
Mac users will have to wait until Blizzard fixes the Mac client as blue has indeed confirmed that it is a currently a bug.
PARTY_MEMBERS_CHANGED and RAID_ROSTER_UPDATE are gone.
Replaced by GROUP_ROSTER_UPDATE.
GetNumRaidMembers() and GetNumPartyMembers() are gone as well.
If used with > 0 as a raid or party check this is done with IsInRaid() and IsInGroup() in MoP (2nd one is not exclusive, can return true while in raid as well)
MoP beta: If you log in with Recount (r1201) enabled, and while standing in a phased area, the WoW client will crash assert while loading addons.
The root bug here is probably Blizzard's, since a) no addon should be able to crash the client, and b) there are other addons affected by this same issue.
Still, if you can happen to find a workaround, it'd be much appreciated since Blizzard appears to be taking their time fixing this assert.
Two places I've specifically verified this interaction, both on the Wandering Isle:
1. North of the crash site, next to Ji Firepaw, when he wants to give you the Urgent News quest
2. East of the crash site, next to Delora Lionheart, after turning in Urgent News.
Many of my addons do not have this issue, so its probably one of the less commonly used APIs; one that is called by Recount during loading; and one that could conceivably be impacted by phase state.