2 Questions:
1)
Lately, i've been on a mission to try to find a setting that lets me adjust incoming health on the frames (Color, Placement, enable/disable, etc). To be more clear, if I cas't renew on myself (or any frame for that matter), a hot tick (+1275) in green shows up in my player frame (or the frame to which i cast to)... please tell me that's adjustable?
It's overwhelmingly distracting in raids to see green numbers from aoe heals, hots, etc., flying around on my frames! I'll be in heaven if that's adjustable, or even the ability to disable :D
I feel like I shut it off in PB3, but it's been so long I couldn't even say with much certainty.
2)
Is there a way to shut off auto-switching to targets that cause you damage?
Thanks for all your dedication to your addons and the addon community!
-Stoobs
1: go into texts for the frame and dissable combat text.
12x Skinner\Skinner-b4.14480.2.lua:516: attempt to index field "obj" (a nil value)
Skinner\Skinner-b4.14480.2.lua:516: in function <Skinner\Skinner.lua:488>
(tail call): ?
Skinner-b4.14480.2\SkinMe\Skada-1.3-6.lua:28: in function "skinFrame"
Skinner-b4.14480.2\SkinMe\Skada-1.3-6.lua:55: in function <Skinner\SkinMe\Skada.lua:4>
(tail call): ?
<in C code>
Skinner-b4.14480.2\UtilFuncs.lua:93: in function <Skinner\UtilFuncs.lua:91>
Skinner-b4.14480.2\UtilFuncs.lua:150: in function "checkAndRunAddOn"
Skinner-b4.14480.2\AddonFrames.lua:150: in function <Skinner\AddonFrames.lua:109>
(tail call): ?
<in C code>
<string>:"safecall Dispatcher[2]":9: in function <string>:"safecall Dispatcher[2]":5
(tail call): ?
Ace3-r1036\AceTimer-3.0\AceTimer-3.0-5.lua:164: in function <Ace3\AceTimer-3.0\AceTimer-3.0.lua:138>
Locals:
nil
1x Skinner\Skinner-b4.14333.5.lua:513: attempt to index field "obj" (a nil value)
Skinner\Skinner-b4.14333.5.lua:513: in function <Skinner\Skinner.lua:486>
(tail call): ?
Skinner-b4.14333.5\SkinMe\Skada-r328.lua:24: in function "skinFrame"
Skinner-b4.14333.5\SkinMe\Skada-r328.lua:44: in function <Skinner\SkinMe\Skada.lua:3>
(tail call): ?
<in C code>
Skinner-b4.14333.5\UtilFuncs.lua:91: in function <Skinner\UtilFuncs.lua:89>
Skinner-b4.14333.5\UtilFuncs.lua:148: in function "checkAndRunAddOn"
Skinner-b4.14333.5\AddonFrames.lua:150: in function <Skinner\AddonFrames.lua:109>
(tail call): ?
<in C code>
<string>:"safecall Dispatcher[2]":9: in function <string>:"safecall Dispatcher[2]":5
(tail call): ?
Ace3-r1035\AceTimer-3.0\AceTimer-3.0-5.lua:164: in function <Ace3\AceTimer-3.0\AceTimer-3.0.lua:138>
1. Ability to put items in the action bar that you normally couldn't. For example when you are farming mats...I currently use button forge so that I can see how many Elementium Ore I have farmed without opening my bags. I can place an Elementium Ore in a slot and see the count.
2. Make a bar popup on proc. Rift has this feature where a button will popup when an ability procs and after the button is pressed it disappears. An example of when this would be great is Pyroblast. I only use Pyroblast when it procs...so when pyroblast procs it could popup centered above my action bars and when the spell is cast it disappears (or if the timer were to run out it would disappear as well).
Just some thoughts on what could make an already great addon even better...keep up the good work!!!
Im no expert on wow API, addons, lua and so on and what can and cannot be done, but im pretty sure both of those are down right impossible to do.
I definitely love Skada simply because it so light weight and intuitive. I currently use it for tanking and one of the things that bugs me is its hard to go back to the Threat Mode (module whatever) when I go to check the dps or damage taken etc. Threat isn't on the Skada:Modes menu since it only displays like the first 10 modes in alphabetical order, so threat isn't on there. My current workaround has been to rename the Threat module to "All Threat". For those interested in how to do it:
local mod = Skada:NewModule (L["All Threat"])--(L["Threat"])
My completely frivolous and pointless question is can I get Skada:Modes to Sort the modes differently rather than alphabetically. I tried this(my code is red):
function Skada:AddMode(mode)
--SOME CODE
table.sort(modes, function(a, b) return a.name < b.name end)
[COLOR=Red]table.insert(modes, 1, "All Threat")[/COLOR]
for i, win in ipairs(windows) do
win:Wipe()
end
This didn't work because it looks like Skada likes to wipe the current mode list repeatedly and refresh it alphabetically once again. Full Disclosure I know next to nothing about Lua or most programing.
Anyone have an idea?
A tip that might help is to turn of unneeded modules to make the list shorter.
Um no, an audio warning for an interrupt where 1 tick of it going off will wipe the raid is pretty damn useful. DBM has this feature for every major interrupt, it's a good feature, a useful feature, argue if you wish but you are just being stubborn. Anyway my code worked perfectly so if anyone else wants to use it feel free.
Get over urself will ya, it was a simple question for crying out loud...
Using the latest version of Skinner, I am getting the same transparent backgrounds again. Going to revert back to previous tukui file from Skinner again and report back if that fixes it.
Its not TukUI specifik, i don't use it and was affected aswell.
What amazes me are authors who ignore reasonable questions and are apparently too important to even reply with a simple "we have no plans to include that functionality".
By the way, there are also no warnings for Shadow Nova on Halfus, Depravity on Cho'Gall in addition to Blast Nova on Nefarian, making this addon pretty useless for anyone that interrupts in current content.
You come in and demand "answer me right away!!" and get pissed when u dun get an instant answer, these authors do this on their spare time, for free and share with the rest of us at no charge. Even if they are shown as online dosen't mean they are actively reading right now, i always show as online cos im always logged in and have a tab with the forums open, but i read them about once a day. Ontop of that they might not reply right away after reading a post, they might read it, look into some code, talk to their co-authorsm, checking options, thinking about it if it matches what they want in their addon, maybe checking if others would want/need it to and so on before making any call about the stuff in the post.
As for specific warnings about the interrupts, isn't the castbars enough? Since you should always be on your target anyway.
0
1: go into texts for the frame and dissable combat text.
0
That looks like its done by a bossmod not a unitframe addon.
0
0
0
0
Here ya go.
Edit: Seems the problems are specific to the new beta/alpha versions being posted.
0
1x Skinner\Skinner-b4.14333.5.lua:513: attempt to index field "obj" (a nil value)
Skinner\Skinner-b4.14333.5.lua:513: in function <Skinner\Skinner.lua:486>
(tail call): ?
Skinner-b4.14333.5\SkinMe\Skada-r328.lua:24: in function "skinFrame"
Skinner-b4.14333.5\SkinMe\Skada-r328.lua:44: in function <Skinner\SkinMe\Skada.lua:3>
(tail call): ?
<in C code>
Skinner-b4.14333.5\UtilFuncs.lua:91: in function <Skinner\UtilFuncs.lua:89>
Skinner-b4.14333.5\UtilFuncs.lua:148: in function "checkAndRunAddOn"
Skinner-b4.14333.5\AddonFrames.lua:150: in function <Skinner\AddonFrames.lua:109>
(tail call): ?
<in C code>
<string>:"safecall Dispatcher[2]":9: in function <string>:"safecall Dispatcher[2]":5
(tail call): ?
Ace3-r1035\AceTimer-3.0\AceTimer-3.0-5.lua:164: in function <Ace3\AceTimer-3.0\AceTimer-3.0.lua:138>
Locals:
nil
0
Im no expert on wow API, addons, lua and so on and what can and cannot be done, but im pretty sure both of those are down right impossible to do.
0
http://img198.imageshack.us/img198/4336/combhelp.jpg
Moving the frame with the bars up a bit if so they don't overlap.
0
http://www.wowinterface.com/downloads/info18169-CombustionHelper.html
(bg/border of the "always up" window)
0
A tip that might help is to turn of unneeded modules to make the list shorter.
0
Just gotta ask, why not just use the "lock" thats already built into BT?
0
Get over urself will ya, it was a simple question for crying out loud...
0
Its not TukUI specifik, i don't use it and was affected aswell.
0
You come in and demand "answer me right away!!" and get pissed when u dun get an instant answer, these authors do this on their spare time, for free and share with the rest of us at no charge. Even if they are shown as online dosen't mean they are actively reading right now, i always show as online cos im always logged in and have a tab with the forums open, but i read them about once a day. Ontop of that they might not reply right away after reading a post, they might read it, look into some code, talk to their co-authorsm, checking options, thinking about it if it matches what they want in their addon, maybe checking if others would want/need it to and so on before making any call about the stuff in the post.
As for specific warnings about the interrupts, isn't the castbars enough? Since you should always be on your target anyway.