Pengoros

In that case you will need to delete the BuffBarsSettings.plugindata file found in your Documents/The Lord of The Rings Online/PluginData/{account}/{server}/{character} folder.

Lupini

Thanks so much for this. So far on both captain and hunter, it's great.

One question, is there a way to add something back once I've set it to ignore? Or should I just start over with a new bar?

woal

I can't get the plugin to load to get to the options screen. Or are you talking about something inside the main lotro options? I'm running lotro on a 52" monitor and so I have a lot of the font sizes turned down.

Fixer

This is from a random image i found from a WoW player as you can see it shows only the buff icon and the duration time under of it.

The same can be for debuffs just with the right debuff frame border color.

Pengoros

Can you point me in the direction of another plugin(wow or whatever) that does this so I can see what you are talking about?

Fixer

Great plugin!
although, I havent tried it yet since im using EU client but it seems great.
However, i would like to ask you if you could make an option to show only the buff/debuff icon and under of it the timer like the most mmos buffs frames

Pengoros

Do you have a Turbine folder in your Docs/The Lord of the Rings Online/Plugins folder?

Pengoros

Somehow you have an invalid font set. You should be able to open the options and for each effect window choose a new font.

Xannthar

Hey Pen, love the addon from the vid but I'm having the same problem. I have buffbars in the addon list but I get the above error when I try and load. I unzipeed the folder from the link "LuaDocumentation" and put it in the "my documents/lord of the rings online" folder, however I still receive the same error.

EDIT: Not sure if it makes any difference or not but I was able to install and load the plugins manager, I don't know if it has any need for the API docs or not but that addon is working

woal

I'm now seeing this error:
"...line\Plugins\PengorosPlugins\BuffBars\EffectIt em.lua:258: attempt to perform arithmetic on local 'timerWidth' (a nil value)"
then I get a message that i can't load the plugin. After that, every so often the same error comes up a few times in a row, like it's still trying to load? I had this working right after launch, but now I'm seeing this anytime I try to use it.

Valdacil

Wow, that's a strange bug, Turbine. I'll have to test what you said. Thanks for the tip.

Pengoros

This bug affects all plugins using lua quickslots. Hopefully turbine will fix it in the next update. When this happens swapping hotkey 1 and 2 and then swapping them back will fix the problem without having to open up yours skills window.

JemAs

Thank you for this great plugin!

Valdacil

Excellent work. One of my favorite plugins.

I believe I found a stange bug, however. I discovered this on my warden, though I haven't tried to reproduce with any other class. I put a stack of potions in the Quickslot bar. Then if say I had put 3 poison cure potions there, and use all three suddenly my leftmost button on the main turbine bar (the one w/ the main menu and all the other graphics) becomes unusable. It also appears like there is something in front of the button, however the tooltip shows the skill I just can't click on it (or it doesn't register it's clicked).

At first I assumed some other window in front so I used "/ui layout load" to load my last saved layout. When I do this, my leftmost button on the main turbine bar (hotkey 1, the one I couldn't click before) because the greyed out stack of potions I just used up on the BuffBar Quickslot Bar. I then have to go into my skillbook, find the skill and replace the greyed out potion in hotkey 1. This makes hotkey 1 usable again.

So it looks like something to do with running out of a stack of potions on the BuffBar Quickslot bar messing up Hotkey 1. This has happened multiple times... always same condition. i use the last of a stack of potions from the Quickslot bar and Hotkey 1 becomes unusable.

Pengoros

I saw this when we ran BG the other night too. I wasn't able to log the effect though to see what was causing the problem though.