Yup, pretty much what I found in my testing. The whole table.remove is bad thing. But it's nice to have the extra detail as to why. Thanks for the link.
Originally Posted by Imhothar
Last edited by Karuul; 05-08-2012 at 09:23 PM.
Latest update didnt fix issue with NKThings. Heres screenshot of error NKThings gives if its any help. http://i.imgur.com/QmiJp.jpg?1 Switched back to previous version(1.18) I was using that worked fine before but now is giving same error. =/ Hope to see a fix soon its spaming my chat lol.
Last edited by Zaphrina; 05-09-2012 at 12:52 AM.
I'm sorry to hear that you are still having problems. However the error you are getting appears to be different than the table.remove error that I just fixed. Can you please do the following things?
Originally Posted by Zaphrina
1. Disable KaruulAlert and see if you still get the error.
2. Post the version of both nkThings and KaruulAlert you are using.
The error that was caused by KaruulAlert was "Error: nkThings/events.lua: 136: attempted to index local 'uf' (a nil value)" and was caused by KaruulAlert removing an entry from the events table. As of version 1.24 KaruulAlert no longer removes any entries from the event table and therefore will not cause that error to happen.
LOL, ok man, it's all yours.
Hehe opps. Just sharing the error love.
Is there a way to show debuff counters/stacks on particular (de)buffs, for example on pyro's combust dot and stormcaller's electricute effect. It might be by using the "stacks" field, but I don't know how to use it.
Thanks for all the work you put into this work-or-love Karuul.
There is currently no way to display the number of stacks on the alert itself. I've been thinking about adding it, but haven't gotten around to it yet.
The "Stacks" field allows you to trigger the alert when the number of stacks reaches a certain number.
Last edited by Thorarin; 07-27-2012 at 12:09 PM.
would it be possible to modify the ability ID for heat retention in the saved variable files to show the 30% finisher buff that 5 stacks of heat retention activates instead of the current one?
atm i cant get the addon to display the buff i want so i figured a quick hack-fix would be to modify the ability's ID (assuming thats what it is in the file)
i just cant find a source for ability IDs
Last edited by Glytch; 07-29-2012 at 05:10 AM.
Buff alerts do not work off ability IDs. They work purely based on buff names, plus an optional buff duration if there are multiple buffs with this same name. The duration might solve your problem, but I'm not familiar with the exact mechanics of Heat Retention.
Originally Posted by Glytch
updated to version v1.31.0 and lost all setups.
im getting this error on startup
attempt to index global 'kAlert' (a nil value)
Trying to add new alert gives.
Error: kAlert/alertset.lua:39: attempt to index global 'kAlert' (a nil value)
In kAlert / kAlert.btSave:LeftPress
kAlert/alertset.lua:39: in function 'Add'
kAlert/config.lua:1565: in function <kAlert/config.lua:1410>
I have used the stacks, layers and text options to track expose weakness stacks on the target. I made 20 different alerts in this style
expose weakness 1 with stacks: 1, text: 1, layer 1
expose weakness 2 with stacks: 2, text: 2, layer 2
and so on, all overlapping in exactly the same place. This way it showed only the highest stack currently on the target.
Here's an example of an exported alert.
Expose Weakness 12;12;T;player.target;1;T;F;T;Expose Weakness;a000000000DC62183;0;12;F;F;0;0;Rift;Data/UIability_iconsexposeweakness4.dds;937;755;48;48;1 ;1;12;CENTER;1;;1;1;1;30;T;F;CENTER;30;T;6;F;0
However I have run into an issue with the latest versions no longer updating the stacks. They seem to only update if I clear my target and target again and it's quite annoying. They used to update in real time whenever the stacks got consumed. Any idea why it stopped working?
If I understand correctly, your alerts only update when the number of stacks increase, but not when they decrease?
Originally Posted by Gery
I made some tests with stacks decreasing, but perhaps there is something unique to the expose mechanic that broke your setup after 1.30.0. I will have to look deeper into this.
Correct, the stacks update properly when they increase but not when they decrease. It does update when all the stacks drop though. I tried to look into previous versions so see when the issue appeared but nothing earlier than 1.30 seems to work at all anymore.
Originally Posted by Thorarin