Regarding Temple of Kotmogu:
The 'Temple of Kotmogu' pattern for zhCN is missing!
There is currently (220.127.116.1109-PTR) no way (at least for me) to log-in with the zhCN client on PTR.
I need 2 strings from zhCN: (orb TAKEN / orb RETURNED)
"(NAME) has taken the (ORBCOLOR) orb!"
"The (ORBCOLOR) orb has been returned!"
If you know the pattern please post here (or use http://www.wowace.com/paste/ because the forum has some probs with some character sets) or change it directly on the repository (file BattlegroundTargets-localized-carrier.lua). Thanks.
- Curse Premium
Member for 13 years, 1 month, and 15 days
Last active Wed, Mar, 2 2016 10:57:33
- 0 Followers
- 471 Total Posts
- 0 Thanks
Nov 25, 2012try this:Posted in: Grid & Grid2
The toc is 50100 for the upcoming 5.1 Patch. Enable 'Load out of date AddOns' for current live server.
Oct 21, 2012@arkdelkaos:Posted in: General AddOns
The font problem is fixed.
Oct 19, 2012@kerckof:Posted in: General AddOns
I have no clue how you get that error. (Do you changed SavedVariables? From which version do you upgrade to r149?) ... anyway:
I added an integrity check (a simple type() check) to avoid unauthorized modification or corrupt data and make sure such error never happen again. :)
Oct 17, 2012@Galvin:Posted in: General AddOns
Thanks for finding this. Fixed. http://www.wowace.com/addons/battlegroundtargets/files/
Don't know. The font is GameFontNormal. I take a look at it.
Sep 21, 2012BattlegroundTargets-50001-3: http://www.wowace.com/addons/battlegroundtargets/files/Posted in: General AddOns
Sep 19, 2012H0PE:Posted in: General AddOns
I have no plan to add such options.
The taint issue should be fixed.
The classToken ( 9th return value from GetBattlefieldScore() ) is now checked against the classes table to avoid such errors ("" or invalid strings). fixed.
Sep 18, 2012Strange. BattlegroundTargets does not touch a single glyph function/event/variable/whatever.Posted in: General AddOns
I never had any ADDON_ACTION_FORBIDDEN / ADDON_ACTION_BLOCKED messages involving BattlegroundTargets.
I need more info. How can I reproduce that error message?
edit: think I found something. maybe...wait
Sep 13, 2012_ForgeUser136437 posted a message on [Grid] Modules: Threat,RaidIcons,MTs / Indicators: Text3,SideIconsPosted in: Grid & Grid2
Sep 3, 2012Well, I wrote this little addon (or fix) because Blizzard forget to add a Clear Button to the TradeSkill frame.Posted in: General AddOns
Every other ingame search field has a Clear Button... expect the TradeSkill frame...
Because of that the TradeSkill searchfield (+TradeSkillClearButton) works a bit different compared to other searchfields (with a default Clear Button). This differences are really tiny, but I do not want to mess around in the TradeSkill searchfield focus/text display to make it work like others. By the way: not all search field with a default Clear Button works the same way (compare Backpack and EncounterJournal)...
TradeSkillClearButton simply adds a button and is not changing any default things in the TradeSkill frame.
TradeSkillClearButton is only visible if the searchfield has focus or is not empty.
If Blizzard adds a Clear Button to the TradeSkill frame this addon is history anyway.
Sep 1, 2012BattlegroundTargets-50001-1: http://www.wowace.com/addons/battlegroundtargets/files/Posted in: General AddOns
Aug 31, 2012_ForgeUser136437 posted a message on [Grid] Modules: Threat,RaidIcons,MTs / Indicators: Text3,SideIconsBoth are updated (GridIndicatorSideIcons/GridIndicatorCornerIcons), but I can not reproduce your bug.Posted in: Grid & Grid2
Please update Grid and GridIndicatorSideIcons/GridIndicatorCornerIcons and try again with only these addons enabled.
If you still can not see the tabs for these mods than may be something is wrong with the SavedVariables file.
Aug 30, 2012Update is here:Posted in: General AddOns
Lombra, I found this differences to 4.3.4:
- The arguments and how to use the function GetAchievementCriteriaInfo() has changed a little bit with 5.0.
- Some GetAchievementNumCriteria(statID) does not return correct values (e.g. 1774 and 1775).
- A wrong criteriaID in a GetAchievementCriteriaInfo(achievementID, criteriaID) call can produce a bug. Which happens if you iterate over GetAchievementCriteriaInfo(achievementID, criteriaID) with a fixed number insteed GetAchievementNumCriteria(statID), which is necessary to overcome the possible wrong return value from GetAchievementNumCriteria(statID). This means, it's necessary to write code that bugs to get the correct value. :)
- GetAchievementCriteriaInfo() calls are now as fast as prior 4.1. That's very good.
- To post a comment, please login or register a new account.