• 0

    posted a message on Pre-3.2 player name auto-completion
    Quote from Phanx
    It's still horrible, though. The pre-3.2 autocompletion was perfect. I don't know why they'd change it, especially to something so awkward.


    It's apparently a bug:

    World of Warcraft Client Patch 3.2.0 Known Issues

    [...]

    The new name drop down feature has disabled the auto-fill feature

    Presumably the auto-complete trying to fill in the second word of anything you type is also a bug, but there's no official mention of it I've seen.
    Posted in: Addon Ideas
  • 0

    posted a message on Fragile
    For tanking one of the most useful mods I ever tried was Fragile. It was, in essence, BanzaiAlert in reverse -- if another party member got agro it would give you basically the same alert BanzaiAlert does. For a tank, where situational awareness is the bulk of your job (granted, in the AoE-fest that is most of Wrath, somewhat less so, but still...), it was hugely useful as it's not always practical to be staring at your unit frames watching for an agro highlight when five big uglies are trying to pound in your ursine cranium.

    Unfortunately Fragile, much like my father-in-law, has gotten elderly and more then a tad unreliable. It hasn't been updated since 03-27-2008, well before the pre-3.0 combat log and threat reporting changes. To the best of my knowledge there is no similar mod out there. Pretty much everything is, sensibly enough, focused more on telling squishies when they have agro rather then tanks when squishies have agro.

    If anyone knows of a mod I missed that does this or a similar job, or can be made to do so, I'd appreciate it if you could let me know. If not, well maybe someone will find it a worthy project to pursue.

    Anyone doing so would, of course, have my eternal gratitude.

    For at least a year.

    Maybe two.

    Can't really commit to two, though.

    Not for sure, anyway.

    You know how it is. Contractual obligations, lawyers, summoning demons, signing in blood, it's all so messy. Besides, everyone knows Aion is going to destroy WoW anyway, right?
    Posted in: Addon Ideas
  • 0

    posted a message on The New Curse Client
    Though there seems to be some confusion about whether it's the Curse site or Curse client under discussion, you might want to be aware of this ("Curse Gaming Seems to have been hacked") thread on the WoW forums.
    Posted in: Updaters
  • 0

    posted a message on Squire - lightweight mount helper
    I noticed today, whilst running around doing holiday stuff (in STV, specifically, flying from Grom'gol to Booty Bay was the first time I noticed it), that while I'm taking a taxi the key with my Squire macro would be continuously cycling through my available mounts. This stopped as soon as I landed and the macro seemed to otherwise be working just fine.

    I'm not really sure it's even an issue, nor, given how rarely I take taxis, when it might have started, but I thought I'd mention it for whatever it's worth.
    Posted in: General AddOns
  • 0

    posted a message on Captcha/wowmatrix
    From the "What are the odds?" department (note the filename being downloaded):
    Posted in: General Chat
  • 0

    posted a message on Direct Quote from Cairenn - Important
    Quote from Belazor
    What I'm sort of curious about is, how will they enforce this?


    I don't think they need to.

    1) ModX comes out that violates one or more of Blizz's rules.

    2) Blizz sends the author or ModX a letter asking them to comply.

    3a) Author of ModX changes whatever it is Blizz didn't like and all is well.

    Or -

    3b) Author of ModX ignores Blizz and/or tells them to put their request where the sun don't shine.

    4) If 3b, Blizz adds ModX to their 'Banned Mods' list using the ToC name/version and/or filenames of the mod.

    5) Blizz puts in place some sort of "get off our banned list" procedure.

    6a) Author of ModX follows the "get off our banned list" procedure and all is well.

    Or -

    6b) Author of ModX decides to say "screw it" and drops development of their mod.

    Or -

    6c) Author of ModX looks at how Blizz's banned mods list works and thinks "Noobs, this'll be easy to get around!".

    7) If 6c, Author of ModX releases a new version of their mod with a changed ToC/filenames to get around Blizz's rules.

    In taking active steps to circumvent Blizzard's banned list system the author of ModX has shown intent and handed Blizz's legal depart all of the ammo they need to bury them under a mountain of lawsuits and cease and desist orders for the rest of their natural lives.

    The "banned mod" system doesn't need to be particularly sophisticated nor enforcable in any technical sense. Active steps to circumvent it constitute intent and any "I didn't know!" or similar arguments go right out the window and all that's left is to argue over whether or not Blizz has the right to dictate the rules under which mods can run in their sandbox.

    And I don't know of anyone reasonable who thinks that's an argument Blizz would lose.
    Posted in: General Chat
  • 0

    posted a message on DynPerf - Automagically update video settings based on frame rate.
    Quote from Adirelle
    It should not. DynPerf restores your settings when it is disabled and on logout.


    I believe I made the change after a 134 crash, so it never got the chance. Not my brightest move, perhaps, but the settings aren't where I had them and they do work quite a bit better. .
    Posted in: General AddOns
  • 0

    posted a message on DynPerf - Automagically update video settings based on frame rate.
    Quote from HunterZ
    Weird, it works fine for me via ButtonBin.


    And in Fortress as well.

    Oddly, Dynperf caused a bit too much stuttering on my system so I ended up removing it for now. Since doing so, however, my framerate has been higher and steadier even at the much-higher-then-I-typically-use settings it had things on when disabled. I assume some setting or flag it changed is left in the config.wtf and my video card approves, but I've no idea what it might be.

    Whatever the case, thanks.

    Edit : This list might be of use to others.
    Posted in: General AddOns
  • 0

    posted a message on SimpleSelfRebuff - official topic
    Quote from Adirelle
    Hrm... and do the warlock stones and rogue poisons work ?


    I didn't get a chance to test extensively -- I'm spending most of my time on my druid and priestess right now -- but the stones do appear to work correctly.

    As far as poisons, my rogue doesn't have any yet, so I couldn't test those.

    edit : I wasn't sure if SSR would conjure stones if there weren't any. I assumed not, so tested with stones already in my inventory. Doubt it matters, but figured I'd mention it.
    Posted in: General AddOns
  • 0

    posted a message on SimpleSelfRebuff - official topic
    With r208 both the warlock and rogue errors are gone.
    Posted in: General AddOns
  • 0

    posted a message on SimpleSelfRebuff - official topic
    With r207 my warlock gets this error --

    [2008/11/26 09:38:10-2701-x1]: SimpleSelfRebuff-r207 \SimpleSelfRebuff.lua:731: Argument #2 to BuffClass:new() should be a string, not "nil"
    <string>:"safecall Dispatcher[1]":4: in function <[string "safecall Dispatcher[1]"]:4>
    <in C code>: ?
    <string>:"safecall Dispatcher[1]":13: in function `?'
    CallbackHandler-1.0-3 (Ace3):91: in function <...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:86>
    (tail call): ?:
    SimpleSelfRebuff-r207 \SimpleSelfRebuff.lua:1619: in function `RegisterBuffSetup'
    SimpleSelfRebuff_ItemBuffs-r207 \ItemBuffs.lua:128: in function <...face\AddOns\SimpleSelfRebuff_ItemBuffs\ItemBuffs.lua:6>
    (tail call): ?:
    <in C code>: ?
    <string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5>
    (tail call): ?:
    AceAddon-3.0-5 (Ace3):365: in function `EnableAddon'
    ...:
    <string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5>
    (tail call): ?:
    AceAddon-3.0-5 (Ace3):365: in function `EnableAddon'
    AceAddon-3.0-5 (Ace3):377: in function `EnableAddon'
    AceAddon-3.0-5 (Ace3):435: in function <Interface\AddOns\Ace3\AceAddon-3.0\AceAddon-3.0.lua:421>
    <in C code>: in function `LoadAddOn'
    Interface\FrameXML\UIParent.lua:991: in function `UIParentLoadAddOn':
    Interface\FrameXML\UIParent.lua:241: in function `CombatLog_LoadUI':
    Interface\FrameXML\UIParent.lua:389: in function `UIParent_OnEvent':
    <string>:"*:OnEvent":1: in function <[string "*:OnEvent"]:1>
    
      ---
    My druid no longer gets an error and buff selection looks to be correct again. My mage and priestess remain error free.

    Those four are all at 70+. In case it's helpful I'll go through my other characters as well.

    My Rogue (only level 10, so maybe not useful) has this error --

    [2008/11/26 09:45:42-2705-x1]: SimpleSelfRebuff-r207 \SimpleSelfRebuff.lua:731: Argument #2 to BuffClass:new() should be a string, not "nil"
    <string>:"safecall Dispatcher[1]":4: in function <[string "safecall Dispatcher[1]"]:4>
    <in C code>: ?
    <string>:"safecall Dispatcher[1]":13: in function `?'
    CallbackHandler-1.0-3 (Ace3):91: in function <...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:86>
    (tail call): ?:
    SimpleSelfRebuff-r207 \SimpleSelfRebuff.lua:1619: in function `RegisterBuffSetup'
    SimpleSelfRebuff_ItemBuffs-r207 \ItemBuffs.lua:128: in function <...face\AddOns\SimpleSelfRebuff_ItemBuffs\ItemBuffs.lua:6>
    (tail call): ?:
    <in C code>: ?
    <string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5>
    (tail call): ?:
    AceAddon-3.0-5 (Ace3):365: in function `EnableAddon'
    ...:
    <string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5>
    (tail call): ?:
    AceAddon-3.0-5 (Ace3):365: in function `EnableAddon'
    AceAddon-3.0-5 (Ace3):377: in function `EnableAddon'
    AceAddon-3.0-5 (Ace3):435: in function <Interface\AddOns\Ace3\AceAddon-3.0\AceAddon-3.0.lua:421>
    <in C code>: in function `LoadAddOn'
    Interface\FrameXML\UIParent.lua:991: in function `UIParentLoadAddOn':
    Interface\FrameXML\UIParent.lua:241: in function `CombatLog_LoadUI':
    Interface\FrameXML\UIParent.lua:389: in function `UIParent_OnEvent':
    <string>:"*:OnEvent":1: in function <[string "*:OnEvent"]:1>
    
      ---
    My paladin (39), warrior (31), and death knight (58 ) have no errors.

    I hope this helps, and thanks for the druid fix and all your work on this great mod.
    Posted in: General AddOns
  • 0

    posted a message on SimpleSelfRebuff - official topic
    With the latest beta on my druid I get this error and there is no longer an option for MotW/GotW:

    [2008/11/25 19:37:33-2686-x1]: SimpleSelfRebuff-v2.0.4-beta-3 \buffs\druid.lua:33: Argument #2 to GetCategory should be a string, not "1126"
    (tail call): ?:
    <in C code>: ?
    <string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5>
    (tail call): ?:
    AceAddon-3.0-5 (Ace3):365: in function `EnableAddon'
    AceAddon-3.0-5 (Ace3):435: in function <Interface\AddOns\Ace3\AceAddon-3.0\AceAddon-3.0.lua:421>
    <in C code>: in function `LoadAddOn'
    Auc-Advanced-5.1.3715 (SnaggleTooth)\CoreScan.lua:64: in function `LoadAuctionImage'
    Auc-Advanced-5.1.3715 (SnaggleTooth)\CoreScan.lua:527: in function `GetScanData'
    Auc-Advanced-5.1.3715 (SnaggleTooth)\CoreAPI.lua:368: in function `QueryImage'
    ...dvanced\Modules\Auc-Util-SimpleAuction\SimpFrame.lua:100: in function `GetItems':
    ...dvanced\Modules\Auc-Util-SimpleAuction\AucSimple.lua:72: in function `ProcessTooltip':
    ...:
    <string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5>
    (tail call): ?:
    AceAddon-3.0-5 (Ace3):365: in function `EnableAddon'
    AceAddon-3.0-5 (Ace3):377: in function `EnableAddon'
    AceAddon-3.0-5 (Ace3):435: in function <Interface\AddOns\Ace3\AceAddon-3.0\AceAddon-3.0.lua:421>
    <in C code>: in function `LoadAddOn'
    Interface\FrameXML\UIParent.lua:991: in function `UIParentLoadAddOn':
    Interface\FrameXML\UIParent.lua:241: in function `CombatLog_LoadUI':
    Interface\FrameXML\UIParent.lua:389: in function `UIParent_OnEvent':
    <string>:"*:OnEvent":1: in function <[string "*:OnEvent"]:1>
    
      ---
    FWIW my Warlock has a similar error, my priestess, and mage do not.

    I'm guessing this is probably a problem on my end, if you could point in the direction of what's causing it I'd appreciate it.
    Posted in: General AddOns
  • 0

    posted a message on DynamicPerformance Wrath update
    FWIW, if you look in the comments section of the Dynamic Performance page at Curse, there has apparently been a "fan update".

    I haven't tried it yet myself, but given how nice the original was to have on my iffy system, I'll be giving it a go.
    Posted in: AddOn HELP!
  • 0

    posted a message on Bartender4 - Official Topic
    Quote from Nevcairiel
    I didn't have any issue with the shredder. All Vehicles i had to use while questing worked perfectly. You can control the pitch using your mouse, and the spells using the buttons.


    FWIW, yesterday I tried doing the quest in Borean Tundra where you have to rescue the Kodos and ride them back to the quest giver in a set time. When I had done this on my druid previously everything worked fine, I got on the Kodo and my bar changed to the couple of quest skills you have on the Kodo. However when I got on the Kodo on my priestess my bar/skills didn't change and I couldn't do much of anything.

    I was able to fix it by temporarily disabling the state code. On my priestess, other bars aside, Bar 1 (offensive spells) is the default, Bar 4 (healing spells) replaces it if the target is friendly. When I was targeting the Kodo Bar 4 showed, when I got on the Kodo Bar 1 showed, with all the usual spells and none of the Kodo skills -- hitting the buttons did nothing. Disabling that state code fixed the problem.

    If you want to know the particular state code I'm using, please let me know and I'll look.
    Posted in: General AddOns
  • 0

    posted a message on Main map keeps zooming :(
    Quote from Farmbuyer
    I briefly had this problem many months ago; it turned out to be a bug in the Wowhead Looter data gathering addon. It's long since been fixed, but other mods might be doing the same thing.


    Thanks for the suggestions. It appears the problem was being caused by FreierGeist InstanceTime, which I never would have even suspected.
    Posted in: AddOn HELP!
  • To post a comment, please or register a new account.