• 0

    posted a message on LittleWigs
    Quote from FuxieDK »

    Seems fixed now :)

    Guess I didn't reply in here, but I did make some tweaks to it. Glad it's working right now.
    Posted in: Raid AddOns
  • 0

    posted a message on LittleWigs WotLK
    Quote from 7destiny »

    Ormorok casts spikes 9-23 seconds, and Spell Reflection Bar 5 seconds.

    Eww, 9 seconds between spikes eh? Guess my earlier warning system is out the door. Oh well, I guess I'll take out the spikes soon message since it won't really work for something that has that large of a swing in casts.

    As for the Spell Reflection, if you look at http://wotlk.wowhead.com/?spell=47981, you'll see the aura lasts 15 seconds, but only has 4 charges, so once the last charge is used up the aura would get removed. The bar as it is now, should be a 15 second timer, but get cleared if the aura get's removed before the end of the 15 seconds.
    Posted in: Raid AddOns
  • 0

    posted a message on LittleWigs
    @Marklar: I can't really think of anything. Any options that are set are set through BigWigs and would get saved as such. You could try to maybe delete your BigWigs.lua & .bak file in your savevariables, but it does sound pretty odd that they would get activated for one but not the other, especially when you can see them on the menu.
    Posted in: Raid AddOns
  • 0

    posted a message on LittleWigs WotLK
    This thread is intended for people participating in the Beta to discuss boss encounters and possible boss warnings/bars.

    To run the LittleWigs WotLK modules you'll need to download them from SVN. The modules can be found in the svn://svn.wowace.com/wow/little-wigs/mainline/branches/WotLK/LittleWigs_WotLK repository. Anyone can download files from here anonymously. If you need to know how to checkout, http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-checkout.html. For the time being all the modules will be contained in one folder. Also don't forget to make sure you have the latest BigWigs and it's dependencies. Also keep in mind that if for some reason BigWigs or it's dependencies break, so will LittleWigs. I'll do my best to help fix those things, but they might be out of my league.

    All modules should be considered BETA. Please post combat/transcriptor logs for Lich King 5-man instances (I prefer transcriptor). Please name your log files as follows:

    Structure: [YYMMDD]-[InstanceName]-[Normal|Heroic].[LUA|TXT]
    Example 1: 080628-Utgarde Keep-Normal.lua
    Example 2: 080731-Utgarde Pinnacle-H.txt
    or some very similar structure.

    It may be very important to know the date that the log is from, so that if boss changes in a patch we can make sure we're working with current logs.

    Also one last request. If you are in the beta and some module doesn't work as you expect it or would like it to, don't bother posting a comment unless you have a log file from the run where the issue occurred. I and others don't have the time to hunt down issues without a log file to reference to see what might have changed.

    Here's the state of things. Bold bosses mean I think they are mostly complete, but possibly untested, other bosses listed means there is just a module with death announcements, bosses not listed don't have anything yet.

    Coldarra

    • The Nexus
      • Grand Magus Telestra
      • Anomalus
      • Ormorok the Tree-Shaper
      • Keristrasza

    • The Oculus
      • Drakos the Interrogator
      • Mage-Lord Urom
      • Keristrasza
      • Varos Cloudstrider
      • Ley-Guardian Eregos


    Dalaran

    • The Violet Hold

    Dragonblight

    • Azjol-Nerub
      • Krik'thir the Gatewatcher
      • Hadronox
      • Anub'arak

    • Ahn'kahet: The Old Kingdom

    Howling Fjord

    • Utgarde Keep
      • Prince Keleseth
      • Dalronn the Controller and Skarvald the Constructor
      • Ingvar the Plunderer

    • Utgarde Pinnacle
      • Svala Sorrowgrave
      • Gortok Palehoof
      • Skadi the Ruthless
      • King Ymiron


    Ulduar

    • Halls of Lightning
      • General Bjarngrim
      • Volkhan
      • Ionar
      • Loken

    • Halls of Stone
      • Sjonnir the Ironshaper
      • Maiden of Grief
      • Krystallus


    Zul'Drak

    • Drak'Tharon Keep
    • Dundrak
    Posted in: Raid AddOns
  • 0

    posted a message on LittleWigs
    Quote from Lindalas »

    Does the Hero Mech plug-in have a display that shows who has what polarity? My unit frame of choice filters out that so I can't see it (I can see myself off course). If it doesn't it would be awesome!!!

    Currently it should display some timer bars for everyone that has a positive charge. I have some ideas how to enhance this. But I need to double check the log files, and don't have logs for that encounter here at work.
    Posted in: Raid AddOns
  • 0

    posted a message on LittleWigs
    Quote from FuxieDK »

    Now the "Multiple waves" count-down after wave 6 & 12 doesn't disappear when mini-boss dies..
    It only dissappears when counter reaches 0...

    I think I see the issue, let me know if this sounds right. When you finish wave 5 and you are starting on the boss at wave 6, you get a bar for multiple portals, which I don't think you should. Is that what's happening?
    Posted in: Raid AddOns
  • 0

    posted a message on LibBars-1.0 Background Color
    I wanted to be able to set the background color for the bars, here's what I did, sure there are better ways.  But I'll leave that to the developers, just throwing out the idea and a patch file to make it work.

    Usage would be as follows:

    local bar = self.Bars:NewTimerBar(name, text, time, maxTime, icon, flashTrigger)
    bar:SetBGColor(r, g, b, a)


    Just some other notes that I've noticed.  When the group is set to grow down, it draws the shortest timed timer on the bottom, but after that fades it resorts so the shortest timer is on the top.

    I can't SetFill in the group, only in individual bars. Also, it's my opinion that a timer is a timer and should always count down the time, even if the bar is set to fill rather than empty.
    Posted in: Libraries
  • 0

    posted a message on LittleWigs
    Quote from FuxieDK »

    Ehm.. The last 3-4 days, the 140-seconds coundown between wave 6 & 7 and between 12 & 13, doesn't appear anymore :(

    Thank you, this has been fixed in r78992.
    Posted in: Raid AddOns
  • 0

    posted a message on LittleWigs
    Quote from Kaerus »

    seeing:

    LittleWigs_CoT-2.0\\BlackMorass.lua:284: attempt to call global 'fmt' (a nil value)

    and other similar errors in the BM module. other lines include 233 and 285-290

    Dah, silly me. Fixed now.
    Posted in: Raid AddOns
  • 0

    posted a message on LittleWigs
    Quote from zarnyeq2 »

    ya i know it didnt really belong here, it didnt really belong anywhere, BUT i used one of the ones that had a lot of similiar events (black morass) so i built it into little wigs like that. i wish i could have goten the shieldsmash and life drain bars to work. and i wanted others to benefit from my work.

    Just get a SVN account, it's free (takes a bit of time, but free), then you can just put up your own module like I said, shouldn't be too hard at all.
    Posted in: Raid AddOns
  • 0

    posted a message on LittleWigs
    Thanks. profalbert fixed it for me. I'll start running them through the parser first.
    Posted in: Raid AddOns
  • 0

    posted a message on LittleWigs
    zarnyeq2, while I applaud your effort, I don't think this is the right thing to be apart of LittleWigs. However there are lots of other 3rd party modules like, BigWigs_NajAssist for example. You could just make this it's own module yourself and call it BigWigs_Sharrtuul or something, and then people could take advantage of your work.
    Posted in: Raid AddOns
  • 0

    posted a message on LittleWigs
    Quote from Astaldo »

    I'm using the embedded version (as it comes from files.wowace.com) and the activation is indeed on mouseover
    (and the double message, which I didn't realize was a problem tbh :) - clear now with hindsight )

    Definitely no fault of your own to make that mistake, but I'm not sure that I can resolve things in LittleWigs, think we'll have to wait for an update to BigWigs that uses boss id's instead of just names. For now I've added a warning message. Thank you very much for your transcriptor log, it was helpful in multiple ways :)
    Posted in: Raid AddOns
  • 0

    posted a message on LittleWigs
    Ok at this point I don't see a way to make sure that only one Kael'thas module is load, except for people to run them Load on Demand, if they are run in the LoD fashion, then the two should never load at the same time.

    As a stop gap type measure I added a message when the LW Kael module enables to print a warning to chat to tell them to make sure that the other one isn't loaded also.

    I think I have an idea of how to disable the other one, but I need to do some testing. And tweaks might have to go into both Kael'thas modules in order for it work in both zones. We'll see.
    Posted in: Raid AddOns
  • 0

    posted a message on LittleWigs
    Somehow the Kael module from TK is still jacking things up.  I'm not exactly sure how that is possible unless maybe people are activating it by hand.  The modules should only self-activate if your A) Mouseover/Target the boss and B) are in the proper zone.

    @ompa:  But at least you can see from the transcriptor provided that when he does cast pyro he doesn't not cast it at a specific target, so there is no way to tell who is target, doesn't really matter much, since from what I read you can't really do anything about it.

    -Edit: Yep check this out from the transcriptor log
    "<1.7> *** Kael'thas Sunstrider mod enabled ***", -- [1]
    "<1.7> *** Kael'thas Sunstrider(MT) mod enabled ***", -- [2]
    Two modules are getting loaded.
    Posted in: Raid AddOns
  • To post a comment, please or register a new account.