- Curse Premium
Member for 11 years, 11 months, and 1 day
Last active Sun, Apr, 29 2018 03:51:07
- 0 Followers
- 73 Total Posts
- 0 Thanks
Dec 20, 2010Is this ever going to get fixed? The wowace search is so horribly broken that it's actually more detrimental that useful - it gives users the impression that many hosted addons don't exist there.Posted in: General Chat
IMO just rip out the whole thing and replace it with an embedded Google search -
Here's the HTML for a Google Custom Search I created in 5 minutes that could be dropped into the website and already gives better results than the current search engine:
Oct 26, 2009I've noticed that enabling RecountDeathTrack (with no other changes to my Recount configuration) causes Recount's memory usage to grow exponentially over the course of a 4-hour 10 man raid. I normally only reset Recount at the start of a raid, and let it run the whole time, and without DeathTrack this is never a problem.Posted in: General AddOns
However with RecountDeathTrack loaded, the memory utliization of Recount skyrockets, and this leads to super-slow reload/logouts, and a memory exhaustion crash next time I login. I just did one where the Recount.lua output after my 4hr 10 man was over 500MB in size, where it's normally on the order of 10MB, with absolutely no difference in Recount settings (the only difference being whether RecountDeathTrack was loaded or not).
Please fix this apparently memory leak so this addon can be usable.
Jul 9, 2009Posted in: General AddOnsQuote from ElsiaThe guts of RecountFailbot is LibFail, it's as good or as bad with regards to fails as the lib which I don't maintain.
A constructive approach is to identify which fails are missing and report them to the libfail maintainers. This will help all addons that rely on the lib, not just RecountFailbot.
tbh, it's not worth my time to help the libfail devs re-invent the wheel when EnsidiaFails already does an outstanding job at detection, esp since the only added value would be the ability to display the summary results in the Recount window. IMO it's better to simply drop the libfail dependency and just have a Recount plug-in to EnsidiaFails that can leverage the existing detection and provide the Recount reporting.
Jul 8, 2009Hi - I'm a long-time user of stand-alone Failbot, and it's successor, EnsidiaFails.Posted in: General AddOns
I like the idea behind RecountFailbot and the nice history/summary mechanisms it inherits from Recount, but unfortunately it appears to be missing detection for many of the categories of fail detected by the stand-alone addons mentioned above.
Any chance RecountFailbot (or LibFail) could be updated with a more comprehensive set of fails, or possibly plug into EnsidiaFails as a data source to get these? The output would be much more useful if it wasn't missing so many types failures.
Mar 24, 2009Hi - Great addon, I use it constantly.Posted in: General AddOns
Minor feature suggestion for OpenAll:
The "Open All" functionality is wonderful, but I'd like control over the *order* in which it opens mails (esp when retrieving attachments). Currently it always starts with the oldest message, but I'd really like the ability to start with the newest message, and I suspect other users would like the same.
This is important for two reasons: (1) sometimes I don't have enough bag space for all the attachments in my mailbox, and (2) with enough messages in my box, the truly oldest messages are truncated serverside, so the current behavior of "oldest message" is effectively "oldest message visible clientside", which amounts to a somewhat random point in the middle of my mailbox. When I'm retrieving many of the same item from the mailbox (eg after buying out several dozen auctions identical non-stackable items, exceeding the client-side visible mailbox), starting from the newest message keeps together the items I purchased together (albeit in reversed order), whereas starting from the oldest potentially results in a random subset of the items based on where the truncation occurred and my bag space.
Regarding UI, I suggest an additional option toggle/checkbox for OpenAll like "Start from oldest message" that would control whether it starts from the oldest or newest message.
Jul 1, 2008A few other general feature requests for the buff screen:Posted in: General AddOns
* Add tracking for the mage buff "Amp Magic", since some raid encounters that's recommended across the raid (and a major pain in the *** to buff, since its all single target). "Dampen Magic" might also make sense from a symmetry perspective, although its less commonly used in raiding.
* in raids add the group number somewhere in the buff display (making it easier to determine which groups are lacking stuff)
* upgrade the buff screen so that clicking on someone's name targets that person. This would help with applying missing buffs
May 28, 2008Hi - wonderful addon, but one significant (and hopefully simple) request:Posted in: General AddOns
Please add the prot pally blessing "Blessing of Sanctuary" to the list of recognized pally buffs.
We often raid with enough pallys that much of the raid gets sanctuary, but BigBrother's lack of support for it makes the pally buff screen significantly less useful for pre-pull checks -- because any raid members with that buff are indistinguishable from someone missing a pally buff, unless you check them each individually (defeating the purpose).
- To post a comment, please login or register a new account.