I wrote an addon named CombatAlarm (http://wow.curseforge.com/addons/combatalarm/) that may do what you want, but it's possibly broken now, and it is a terribly written addon. I all but abandoned it before BC ended, but I updated it when I came back at the end of LK. It might work, but be warned that no attempts were made to throttle events, and the spaghetti code involved is highly inefficient, but if all else fails, and if you can stand the worse addon written by yours truly, then I hesitantly suggest CombatAlarm. The usual software disclaimers apply; I'm not responsible if this addon overheats your CPU or otherwise destroys some hardware or stored data (no this is not serious, unless it really happens). Also I won't pay your repair bill once CombatAlarm blows up in your face right when you get some encounter's critical debuff (and yes, I'm really serious about this one. I'm a poor worgen.). Disable showing errors, as I never addressed an existing stack trace related to my laziness about displaying formatted combat log messages; I cheated, but it didn't work. I think this only applies if you choose to display the event's combat log message via your scrolling combat text display, And one more thing - forgive me for my sin against humanity that I have committed by writing this atrocity, and especially for keeping it around like the coding packrat I am.
What CombatAlarm does -- as well as DebuffAlarm, AuraAlarm, and the planned ScriptableAlarm -- is it plays sounds, displays icons or text, and in ScriptableAlarm (the other addons paint the background too) individual widgets per each alarm paint your entire screen's background some user-defined transparent color, blended with other active alarms (there will be a healthy selection of blend methods), and without obstructing the view of your surroundings too much (you can adjust the opacity of alarms individually or adjust the base opacity value to effect all alarms together). Right now AuraAlarm is the only "<blank>Alarm" addon that is up-to-date and written. Also, it has some annoying bugs and design flaws I never addressed before I got going on my tooltip addon and leaving AuraAlarm behind to collect dust.
Honestly AuraAlarm needs rethinking all together, and that is where ScriptableAlarm comes in. With it a savvy user can have the addon sound an alarm based on a custom lua script's return value -- if true the alarm's lit, and if false it's not active. The idea is you have the addon alert you as loudly as you want, and under any condition that the WoW API allows. That was sort of the idea behind CombatAlarm -- a highly generic addon in principle -- but the combat log isn't exactly a reliable source all the time, and it's very costly for an addon to process in the way CombatAlarm does, attempting to catch every single event and process it in real time. And the worse part about combat log events is that some auras don't appear in the logs, such as LK's necrotic plague, hence me abandoning the combat log based DebuffAlarm in favor of AuraAlarm, which just polls aura data.
In ScriptableAlarm you should be able to base an alarm on a combat log event, any other frame event, or you can poll unit data at each WidgetAlarm update. Then ScriptableAlarm will display the alarm based on your script's runtime conditions. Practically anything you can do with an addon that alerts you to some event or condition should be doable by some lower-level configuration of ScriptableAlarm, and later down the road there will exist optional user-friendly option tables with predefined and behind-the-scene alarm scripts that are custom fit to the user's needs, such as injecting specific spell IDs or whatnot into predefined, and addon provided code templates.
But yeah, back to directly answering your question instead of giving possibly false hopes about the ultimate upcoming alerter addon (cough-ultimate-cough). Try CombatAlarm if you're absolutely desperate and out of choices (a small technical note, you'll need to obtain some knowledge about how combat log events are designed if you don't already know. Let me know through a PM if I can help in any way with the learning curve involved, but bring a combat log of the related events). Here's a resource that may come in handy (http://www.wowwiki.com/API_COMBAT_LOG_EVENT) And lastly, If you're interested in more powerful and advanced alarms, then keep an eye on the Wowace forum's General Addons discussion for my inevitable chatter with my boring and lone self about the development of ScriptableAlarm. That's likely next on the agenda after I restructure a library of mine.
If for some reason CombatAlarm is your last hope, and you then discover that it has acquired an addon-crippling bug since last expansion, then let me know and I'll see about fixing it for you -- with hammers and duct tape of course.
- Registered User
Member for 13 years, 7 months, and 15 days
Last active Fri, Oct, 4 2013 14:29:59
- 0 Followers
- 373 Total Posts
- 0 Thanks
Jan 12, 2011_ForgeUser189254 posted a message on Need Addon To Sound Notify Purge/Dispel/Cleanse - And ResistPosted in: Addon Ideas
Jan 11, 2011Posted in: General ChatThere is a private messaging system, you know. Most of your post felt like it was addressed to a specific person, and I have no idea what half of it was referring to...
Besides the parts directed towards the author(s) of LuaTexts, this was also directed toward the Wowace community in general, or anyone interested in something similar to LibScriptable, if not the library itself. I want to see something done with LibScriptable, but if it turns out there's a better design awaiting authorship, that's exactly where I want this to lead. I want scriptable addons to be common amongst even the tinyest group of addon programmers. I make no claims to LibScriptable except through its use in my addons, where I don't want to break users' scripts by breaking compatibility with earlier revisions, and that's all I ask. I find I can trust the Wowace authors and others interested now. I also feel I can not trust everyone, but I'm encouraged that #wowace is active enough that questionable commits can be looked into quickly, or reported to LibScriptable's maintainer, whether it's me or someone else.
I'm saying I am incapable of running this by myself, due to my disorganized nature, and that is why I'm giving it to you all. Instead of doing what I've been doing by crying for support from the community, making offers to join in the authorship, etc.. I'm giving it to the first best candidate who's interested in taking on a library based on the principles of promoting programming for the curious passerby, and staging an advantage geeks can exploit for greater wins.
I know some can't stand the idea of promoting programming like that, as it draws some tragic tales about bad code and habits, but I feel it is all for the better future of software creation. The community seems to be great about their critiques on addons hosted by Wowace, and together you can usually convince an author there's a better way if it exists; same goes for LuaTexts scripts. Sometimes these authors are not convinced; that's their administrative choice. Even though I support wide open projects, there must be someone in charge calling the shots with the final word. I'm not even sure what that person does, and I don't feel confident enough to take on that role myself. Hence me scrambling to find a replacement, or at least help from someone experienced in this sort of thing.
I think there are some great programmers around here -- much better than I. I'm still learning programming in general, and I don't claim to have a working knowledge of Lua's finer details. I find I'm kind of sloppy at times, but I try to return to code every so often to see if I had a brain hiccup when I programmed it, which happens pretty often I'm afraid. I ruminate over programming problems, and am pretty slow most of the time. I do claim some programming talents, but I'm just shy of being talented. Sometimes I'm a total idiot, but I'm smart enough to know that I'm in over my head with this library, especially by myself. The best thing I can do for the library is find a better maintainer than I, because I'll surely give LibScriptable and its addons a bad name and drive addon authors away with broken releases.
Jan 11, 2011Maybe I'm wrong, and it would all be better off left alone. Maybe the whole idea lacks feasibility in action. I ran into my concern and I thought it best if I brought it up with Shefki mainly, but also other interested individuals.Posted in: General Chat
Jan 11, 2011Posted in: General Chat"If you don't add this feature to your addon, I'll write my own addon" is hardly a threat, unless your goal in writing addons is to obtain a monopoly in some particular realm of functionality and/or win some kind of popularity contest. I don't think there's anything anyone could say to me that would get me to add code to my addon that I didn't want to add, or that I hadn't even read. Every single addon I've written was written because someone else's addon didn't do what I wanted. It's not an insult or an ego blow if someone else writes their own addon because mine doesn't do something they want.
It wasn't a feature; it was an imperfection, one that I was happy to accept a fix for in the end. I admit I could have been more defensive, but I try my best not to get into arguments with people. I wanted to see what he had, but his approach left me in a bad place. Also, even though the addon was rather simple, I worked on it, and I wanted some credit. He was threatening to trump me with his status around the community for a mere checkmark in his already lengthy list of addons he's either credited for writing or for contributing to. He wanted his name in the TOC file is all, and I was more than happy to give him that, just not like that. So maybe I want my addons to succeed. What's wrong with that? I made the choice to accept the "offer" because I didn't want to see the addon die, which is what he was threatening.
I have to disagree with you that multiple LuaTexts, or a thousand different Linux distributions, is actually a good thing, or at minimum not a bad thing. For example, there's a lot of confusion when you're googling for a problem you have an error code for under Linux, only to find pages and pages of every other distribution but yours, and for some reason, due to file relocation or something, the other guides don't help much; the user may give up trying. Wait till the official LuaTexts forum becomes the choice for sharing scripts, and they find that those scripts aren't compatible most of the time. People will have to reiterate every so often that there are many LuaText brands, and no author can agree on anything other than that Name() is better looking that UnitName(). Of course I have my own version of Name(), which allows you to choose between PVP name and unit name. So there's somewhat of an incompatibility that users may run into. Adding functions is one thing, but modifying LuaTexts functions themselves without accommodating compatibility with the original, is not what I want to do.
I think we can all agree that users helping users is a good thing for our mental health, and they can't help each other if they are constantly corrected on what LuaTexts implementation they're referring to.
Your argument that mere documentation will suffice lacks confidence in users' ability at not reading a thing before they make assumptions based on experience with other flavors of incompatible LuaTexts. What if the user is using Pitbulll4 and Cowtip, but he can't remember which LuaTexts behaves in a certain way; thus there's confusion. What if, what if, what if... I'd drive you crazy if I uttered it once more.
I'm just proposing that some sense of order come to the LuaTexts brand. In my vision, authors are always free to add their own functions to their addons, but not directly to the LuaTexts brand without at least consulting Shefki and offering that function to other LuaTexts authors and users for community approval, and hopefully adoption by other addon authors. I'm guilty of this btw; I added functions to PluginLuaTexts.
What I'm suggesting is that these variations become topics of discussion, and some resolution is made to promote compatibility at least as far as LuaTexts is involved.
Jan 11, 2011I brought up the topic of LuaTexts' future. The premise is LuaTexts is beginning to leak into other addon discussions, and some confusion is just barely starting to form between the differing LuaTexts implementations. I am promoting the next stage in LibScriptable's development; I'm giving it to the community. And I'm offering at least one solution to preventing LuaTexts from becoming a bad taste in people's mouths -- use LibScriptable's LuaTexts plugin as a semi-official platform for use by addon authors when writing LuaTexts addons.Posted in: Unit Frames
I'm not sure if what I'm advocating is in tune with others' opinions on the future of LuaTexts, but I am sure something needs to be addressed before it spirals out of control. I'm willing to give up maintainership of LibScriptable if it means someone can pull off a central entity for LuaTexts, while still supporting the various particulars of various addons. Eventually someone needs to take this off my hands anyways, and I'm hoping the community will bite my bait and realize that, hey, there's some advantage to this in-game lower-level UI modification that's worth some healthy attention. Some of you already know this, or you wouldn't be using LuaTexts to begin with.
Jan 11, 2011Edit:Posted in: General Chat
Basically what I said here is that I want the community to take over LibScriptable once I restructure and clean it up. Oh and I wrote some other stuff that ended up being too emotional. Apologies to anyone who actually read that wall of text. But be warned, I'm a total moron sometimes and am prone to idiocy. If you see past all of that, and realize that hey this is a decent person overall, regardless of the mental illness, and regardless of his crappy writing, then I think you're alright, and you don't have to support my addons any way for me to say that. I admit they're not perfect, some really bad and in need of a deletion, but then again others stand out in some unique way.
Jan 7, 2011Since I'm planning on providing presets, I'm open to suggestions for lines or full displays. Just post your code here or save file on some pastey site, like pastey.wowace.com (I think), and link it here.Posted in: General AddOns
If you don't know how to code it, make a very detailed description of what you want to see, and any effects (hidden if <expression>, outlined, textures, etc..) and I'll see what I can do.
Jan 6, 2011StarTip can display anything Cowtip can and more. I'm not going to hold your hand while you customize it, though. I have much lesser headaches to deal with.Posted in: General AddOns
This addon is for programmers mainly. I'll look into ways of making it more usable for non-geeks, but it's primarily meant for coders. If you want to customize it, then you're going to need to know what you're doing.
Jan 6, 2011Well, I can't be much help as far as your problem goes. I suggest you click the button "Restore Defaults" and forget you ever touched those edit boxes. I'm not going to walk you through programming.Posted in: General AddOns
As for language support, that's upcoming. I'm going to try and provide a whole array of different translations, or that's the plan.
And I've been thinking a lot about usability today. I just started writing the Layouts module, which will open up the possibility of providing different presets. So I can collect some of the most popular tooltip designs (layouts) and add the best to StarTip, providing a simple drop down menu for selecting your default layout.
Jan 6, 2011Maybe I'll break this all down into smaller libraries. I know, I know, some of you already suggested this. :)Posted in: Libraries
LibScriptablePlugins-1.0 -- All the plugins. These are what populate run environments with functions or other fields.
LibScriptableWidgets-1.0 -- Scripted widgets such as WidgetText for marquees, WidgetBar, WidgetHistogram, WidgetImage, etc..
LibScriptableLCD-1.0 -- This would be the whole package of plugins, widgets, and utilities, plus the LCD-specific LibCore rather than LibCoreLite
LibScriptableDisplayUtils-1.0 -- Things like LibTimer, LibEvaluator, etc.. Another source of good utilities is LibScriptablePluginUtils-1.0
Edit: Oh and I'd like to change to Wowace repo as well. So I see a big change in order.
Jan 5, 2011I think I want to get rid of this entire thread. Would someone please delete it? I'll start another with less noise. I'm ready to leave experimental status behind, and honestly this entire thread was not meant to support in any way the library's users. I'd like to start fresh with the support thread.Posted in: Libraries
Jan 5, 2011Well, if you're going to go modifying stuff, you'll need some coding skills. I make no claims that this addon is user friendly when it comes to customization.Posted in: General AddOns
But to answer the question, you'll want to hide the left side too by returning an empty string like you're doing on the right side.
Alternatively you can simply return nil on the right side, uncheck Right Updating, and that should do what you want. So basically where you see 'or "None"' change it to 'or nil'. You have two occurences to change.
- To post a comment, please login or register a new account.