Stever1388

Both the authors and the other method didn't stop this plugin from crashing my game. The authors method did seem to reduce the frequency of it, but overall it would still crash every hour or so it seemed. The other method would cause BuffBars to not load...

So if anyone is in the same boat as me, here's what I did: In the PengorosPlugins\Utils folder, open the __init__.lua file (with Notepad or something similar) and comment out the very last line that says "PengorosPlugins.Utils.CoolDownManager"; You can comment it out by adding a "--" to the start of the line.

Then go into the PengorosPlugins\BuffBars folder and open the CoolDownList.lua file. Edit out lines 16, 20 through 23, and 27. Without commenting out these lines my BuffBars wouldn't load (not sure how the others were able to get it to load by only commenting out the first thing).

I have not experienced a crash after doing this, and I've been in game for about 6 hours straight now (yes I did take a break). My fingers are crossed.

Garalathdelas

So, at this point, if I use BuffBars mostly for the triggered potion popups there's really no point in loading it at all, correct? Is this something that will eventually be fixable with an update from Turbine?

Setharnas

I can confirm that this works for me - where any previous attempt to get the plugin working again would crash me within a few loots (probably on looting a potion), this one got me through a complete instance without a hitch. YAY!

This wasn't necessary for me, I even restored the lines Pengoros said to comment out. The file is just not called anymore.

Pengoros

There is a lua bug affecting all plugins. Anything using the inventory will crash so unfortunately until there is a patch you won't be able to get the potion popups.

I'll release an update in the next day or two that disables inventory stuff so that CTDs don't happen.

Garalathdelas

I've done everything you have done and it still isn't working for me. Is there any similar plugin that is known to be working properly? I need those potion prompts!

Garalathdelas

When you say 'all is working like a charm now' do you mean that you will be notified to pop potions, etc. without any problems?

Ykses

Don't comment the lines in the "CoolDownManager.lua" file...
But comment the "__init__.lua" file in the same folder
Line 14 :
Also, I've deleted all the code in the "CoolDownManager" file.
But I don't know if it's really needed.
The only code I left in this file is :

And no more CTD
All is working like a charm now (I use Palantir, TonicBars and BuffBars).

Holand

For /pluigns load BuffBars it says:
BuffBars v1.2.0 by Pengoros
Loaded plugin "BuffBars".

For /plugins list it says:
Available Plugins:
****AltInventory (2.03c)
****Bootstrap (1.4)
****BootstrapReloader (1.4)
****BuffBars (1.1.7)
****BusyBee (1.3.1)
****CombatQuickslots (1.1)
****Compendium (1.6.3-beta)
****Crafters (0.954)
****CTime (1.4.5)
****Emo (2.2.2)
****Examples (1.0)
****HugeBag (1.1.21)
****HugeBag Utilities (2.0.2)
****HugeBag Wrapper (1.0.0)
****KragenBars (4.21)
****Lotropad (0.81)
****MoorMap (1.07)
****MoorMapDefaults (1.07)
****MoorMapLoader (1.07)
****MoorMapTerminator (1.07)
****MouseCursorHA (3.01)
****Palantir (1.09.3)
****TheOneBag (1.0)
****TonicBars (2.5.2)
****Vitals (1.0)
Loaded Plugins:
****BuffBars (1.1.7)

And for /buffbar options it says:
... Rings Online\Plugins\PengorosPlugins\Utils\Misc.lua:29: bad argument #1 to 'max' (number expected, got string)

I hope this will help you. Or is it obsolete because of the recently found bug? Now I know why my game crashed two times. Thank very much.

Setharnas

I love Buffbars, but: no, they do not.

I just tried it again. Have played all afternoon with my usual combination of plugins except for Buffbars - nine plugins, among them Kragenbars and Palantir, and not a single crash. Then, on a whim, I re-enabled Buffbars, those code comments from earlier still in place, disabled ANYTHING at all that made reference to cooldowns... Mined an ore node, wham, CTD.

Whatever it is, Buffbars 1.2.0 is currently unusable for me, which basically means playing blindfolded with regards to effects.

Pengoros

There is an issue with lua and plugins that use items. Turbine has acknowledged this and it will be fixed in an upcoming patch. Unfortunately the only work around right now is to disable all of your quickslot bars and turn of pot cooldowns on effect bars. After that the effect bars/sliders should continue to work without causing a CTD.

http://forums.lotro.com/showthread.p...ir-and-others)

grezgorz

Hi Pengoros, I wanted to say thanks for making this plugin. It is one of two that I have used for years and I love it!

I tried commenting out the lines you specified and I still get crashes. Seems to happen in combat only. Any other ideas or should I just be patient and wait for the new version?

Setharnas

I'm afraid that didn't suffice. Even with that fix applied, Buffbars seems to crash the client on opening a loot window with a dropped potion in it. I cross my fingers that you can find the real problem soon, as your work has become essential for me - those small icons under the vitals just don't do it for me.

Zyriel

For whatever reason, using this plugin with RoI causes my client to crash to the desktop. This is the only plugin I had loaded and every time I kill a mob, I get an error window indicating that lotroclient.exe has stopped working and crashes. Anyone else have this issue?

NecroFeline

ty Jasmer about the 'how to lock down' and I read your post about the folder.

Went into my LotRs to have a look and yep the addon is in a Pengoros folder within the Plugins folder.

TheSolar

Well I tried to change it to english but it didn't help. Really weird... This hapen since I got a new PC.. on the old one ther is no issue with this error.

I investigated that there has to be an issue with the comma's in the file BuffBarsSettings.plugindata. If I change the comma (",") to a point (".") in all the Lines where the error shows the line number then the Plugin works until i reload it. Probably this may help you also. I think this locale issue then causes the followup error where the plugin is not able to parse the file with those commas inside... just an assumption