• 0

    posted a message on Dominos - A main actionbar replacement
    Bag and menu bar are really a must have, since many default hotkeys may be remapped.
    Highlight plugin is handy sometimes, but not compulsory, since looking at the AB instead of buff frame is a habit and nothing more. Same goes for roll bar.
    Castbar, IMHO, is not necessary at all, since it doesn't support target, mirror and pet cast bar.

    Frankly speaking, I always preferred Bongos to Bartender, but now I am hesitating a bit, because Bongos feels kinda overfeatured and Mangos lacks bag and menu bars.
    Posted in: General AddOns
  • 0

    posted a message on Dot Timer w/ Mind Blast & SW:D Cooldowns
    looks promising. I hope it will be helpful in PvP as well
    Posted in: Addon Ideas
  • 0

    posted a message on BadBoy: An extremely minimal spam blocker & reporter
    <Funkydude: Reviewed and added>
    Posted in: General AddOns
  • 0

    posted a message on StatBlocks v1: Official Thread
    Everytime i log in, i receive errors, saying "StatBlocks\StatBlocks.lua:149: attempt to index field 'font' (a nil value)". Though the Global Font option is set to the registered in LSM 3.0 Calibri set.

    Also, there is no alignment setting in the clock module )

    Otherwise, the best onscreen text addon.
    Posted in: General AddOns
  • 0

    posted a message on "Highly Configurable!" -- ugh
    There are still addons like Sage unitframes, which are absolutely adorable and have only necessary options.
    Posted in: General Chat
  • 0

    posted a message on Ace2 and Ace3 addons.
    You should delete folders of your broken addons, then download archives from files.wowace.com or wowinterface.com and extract them in addons folder. Everything will work fine, they just need a bit of reinstalling after 2.4
    Posted in: General Chat
  • 0

    posted a message on hosting -> thataway
    Quote from Vint »

    This would also be a "con" as, if it doesn't show up in WAU, if someone is setting up their ui from scratch, and using WAU to download/unpack/unembed their ace addons... they wouldn't be given the full list of working addons to choose from.

    If someone is building UI from scratch he can spend a couple of minutes downloading necessary addons and its dependencies manually.
    Posted in: General Chat
  • 0

    posted a message on hosting -> thataway
    In my opinion, the best way (already mentioned earlier) to clean up files.wowace.com is really to make smth like /archive directory and move addons to it when outdated and backwards when updated. XML file, generated for WAU, mustn't include this directory

    PROS: if addon works fine, it doesn't need to be updated and therefore doesn't need to be on WAU list. If it is updated, it appears in WAU and everyone is happy. Besides, this way you can set TOC limit even to 20300.

    CONS: well, i'm no script writer so i can't estimate difficulty of the task. But something tells me it is easier than looking for authors of each addon or deal with all that whining like "why don't you care about us users?"
    Posted in: General Chat
  • 0

    posted a message on Desktop Screenshots - Show us your non-WoW!

    what is the name of this visual style?
    Posted in: General Chat
  • 0

    posted a message on PitBull Raid Frames and 132 crash
    Quote from Jerry »

    Client crashing must be reported to Blizzard. There is very little that can be done from addon's side.

    well, i don't mind getting a response like "disable the addon", but the problem is that i want to use pitbull raid frames
    Posted in: Unit Frames
  • 0

    posted a message on PitBull Raid Frames and 132 crash
    Lately i've been experiencing error #132 crashes when Pitbull Raid Frames are turned on. It happens soon after i start playing and is caused by almost any in-game action - opening talent window, repairing, taking off at wind rider etc. Crashes happen even when i am not in raid but have raid frames enabled. If they are disabled (i use sRaidFrames as temp. solution), crashes never happen.
    all crash logs look pretty much the same. it says

    The instruction at "0x006BDCDD" referenced memory at "0x1F7F6000".
    The memory could not be "written".

    (referenced memory address varies, instruction address memory doesn't)

    Besides, there is always a part of memory dump, which says

    0012FCE0: 44 42 47 3A 41 63 65 45 76 65 6E 74 32 30 46 72 DBG:AceEvent20Fr
    0012FCF0: 61 6D 65 00 38 4D 41 0E 08 4C 41 0E F4 8C EE 07 ame.8MA..LA.....

    I thought it would be fixed in 2.1.3, but, obviously, it isn't.
    Posted in: Unit Frames
  • 0

    posted a message on Tiny Tip & HonorFu graphical error
    turn on reaction text in tinytip options. That helped me
    Posted in: FuBar AddOns
  • To post a comment, please or register a new account.