valhalla

hallo. LotroLCD is nice plugin, only do not function also European servern. can be reprogrammed it also runs there? thx

vindalfur

Hi,

Making LotroLCD work with the French/German clients is a bit of work, the best way would probably be to switch to using the same language files as CStats uses with Regular Expressions but even then I would probably need to subscribe to a euro account to test with both languages.

I don't know when I'll have time to do this since I'm still working on getting all the functionality of LotroLCD into the in-game plugin.
--------------------------------------------------------------------
Bonjour,

La fabrication de LotroLCD avec clients français/allemands est un peu de travail, la meilleure manière serait probablement de commuter à employer les mêmes dossiers de langue que des utilisations de CStats avec des expressions régulières mais même alors je devrais probablement souscrire à un euro compte à l'essai avec les deux langues.

Je ne sais pas quand je peux faire ceci mais probablement pas pendant un moment puisque je travaille toujours à entrer tous les dispositifs dans le dans-jeu plugin.
---------------------------------------------------------------------
Hallo,

LotroLCD Function mit den französischen/deutschen Kunden zu machen ist ein Stückchen der Arbeit, die beste Weise würde sein vermutlich, zur Anwendung der gleichen Sprachdateien wie CStats Gebrauch mit regulären Ausdrücken zu schalten, aber sogar dann ich würde vermutlich zu einem Eurokonto zum Test mit beiden Sprachen unterzeichnen müssen.

Ich weiß nicht, wann ich Zeit habe, dies zu tun, da ich noch an dem Kommen der ganzer Funktionalität von LotroLCD in das Inspiel Einsteck arbeite.

Cutholen

Hey,

I have a Problem, the Plugins wirks perfect on my G19 LCD, but ingame LUA Windows shows nothing.

Look at screenshots:



I have a second account, there it works... only on one account it doesn't work.

EDIT:

Okay i found the problem:

C:\Users\xxx\Documents\The Lord of the Rings Online\PluginData\Account 1\AllServers\LoadData

ist written, when you login account 2 you need to delete the

C:\Users\xxx\Documents\The Lord of the Rings Online\PluginData\Account 1\AllServers\LoadData

File and then start LotroLCD then it works.... everytime you login a other account you must delte the Loaddata Files....

Evendale

This parser is really useful, and works perfectly for me 90% of the time.

A couple of minor issues though:

1) When a Rune-Keeper first places their rune-stone down there is one line in the combat log that says "You are healed for xxx". This line breaks the parser every time, and you have to restart LotroLCD to get it working again. A fix for this would be nice so I can keep parsing when I'm grouped with RKs ;P

2) It's probably really hard to work out when Combat ends, but I think it could be improved a bit. In particular, being healed shouldn't prevent the parser from thinking combat has ended (as Minst/RK/Capt HoTs can tick away for a long time after combat ends).

Given (2), one really nice feature that could be added (if you're planning on continuing to work on this) would be a toggle where you can set the parser to stop checking for combat ending (ie: not consider combat over until you switch the toggle off). Similarly, a button to specifically end combat would be nice as well. I don't know if that would be easy or hard to do given how the data is fed to the in-game plugin.

vindalfur

1. I was not aware of that, would it be possible for you to send me like 10 lines from your combat log where this happens?

2. Working out when the combat ends is a bit hard but there is a "silver bullet" which I have been planning to implement, basically I can make the LUA plugin tell the C code when the game itself considers the combat to be over, the only time this would not work is when you get stuck in combat in the game :P

2B. I think if the silver bullet is implemented there should be no need for an end combat button but I think a "clear all/reset" button would be useful that's already on my todo list.

vindalfur

I thought I had fixed that bug, I'll re-open it and investigate, thanks for letting me know.

Jarl

Hey,

Cutholen

One more bug, in the LUA Windows you can only have numbers with 5 digits... the 6 digit ist cutted off..

vindalfur

Thanks,

I've added the issue to my bug tracking database.

Cutholen

The Chilled Barrow-wight hits you for 63 points of Common damage to Power.
The Barrow-wight Caller wounds you for 54 points of Shadow damage.
The Barrow-wight Bowlord wounds you with a minor melee attack for 223 points of Shadow damage.
You wound the Barrow-wight Bowlord with a melee attack for 236 points of Westernesse damage.
Dingenskirchen heals you for 57 points of Morale.
Cyreana heals you for 182 points of Morale.
Veltin heals you for 43 points of Morale.
Veltin heals you for 47 Power points.
You must face target.
The Barrow-wight Bowlord wounds you with a mighty melee attack for 435 points of Shadow damage.
You wound the Barrow-wight Bowlord with Sound the Attack for 402 points of Westernesse damage.
You wound the Barrow-wight Caller with Sound the Attack for 363 points of Westernesse damage.
The Chilled Barrow-wight hits you for 63 points of Common damage to Power.

------------------------

Dingenskirchen is the name of the stone. After that line it crashed

Evendale

I thought it was the following that caused the parser to crash:

You are healed for 62 of wound damagepoints.
ButtPlug heals you for 62 points of Morale.
ButtPlug heals you for 62 points of Morale.
ButtPlug heals you for 62 points of Morale.
ButtPlug heals you for 62 points of Morale.
ButtPlug heals you for 62 points of Morale.
ButtPlug heals you for 62 points of Morale.

It seems to be immediately when the stone is placed that the line comes up in the combat log. I don't think the succeeding lines cause any issues.

The line doesn't even make grammatical sense so it's possible it was a bug that got added in the last update or something. CStats seems to just ignore it.

vindalfur

I recently did some work on better detecting healing stones and trying to associate them correctly with the healer, it's probably that code that's causing the issue, X-mas and work is taking up much of my time now but I'll try to have something out as soon as possible.

PS. That's the worst name ever for a healing stone :P

Thraxz

You aren't kidding about that name... yikes, some people's kids...

Anyhow, I 'solved' the issue of the healing stone errors by rolling back to an earlier release for those that want it. (It was driving me crazy).

What's driving me crazy about the last few releases though is that the readme launches with the parser script program every time I start it, and I cannot close it without it also closing the script program too. Having to alt-tab through this readme everytime is not cool as I do a lot of alt-tabbing .

Also, I'm not at all sure of how your parser works, but is there a way to get it to look at the last 1-2 seconds of a battle (after it's been concluded) and remove any time where there is 0 damage dealt. I understand that it's really hard to predict when battle ends, but I see a very consistent 2s of time pass after combat ends where it's ticking off time that's the target is dead but I'm registering 0 DPS and totally throwing my DPS measurments for a loop (to the tune of 100-150 DPS drop). Also, it consistently fails to end combat if I have a bleed on me. The target will be dead, I'll be out of combat but taking something like 47 damage per 2 seconds so the parser is registering me as 0 dps and messing with my statistics for the duration. I'd just as soon lose the targetDPS function entirely if it meant that I had more accurate DPS on myself. Right now that only time I really find it useful is when I'm in battle for >90s and that drop off at the end only dings me for 20-30DPS.

Could I also get a detail of how the hDPS is calculated? Is it just averaging the averages I've had over the last few battles or is it summing all the damage and dividing by the sum time?

Thanks a ton for your work on this plugin as it's been ver informative for me.

vindalfur

Hey,

1. What you are seeing is the new UI, people are used to getting a UI when they launch an application so I made something really simple, since I had to have an app I figured I'd use the space to show the readme. Try minimizing the app either from the LotroLCD/Minimize menu or by clicking the LotroLCD icon in the notification area of your taskbar (lower right corner), this enables you to minimize LotroLCD so you don't have to deal with it when alt-tabbing

2. You touch on a rather complicated and debatable subject, namely when a combat ends. The current logic is that a combat ends when ever all mobs that you or one of your pets has damaged or you taken damage from or if you don't take any or do any damage for 30 seconds. The reason a combat does not end when you have a bleed is that the bleed is not associated with any particular enemy and therefor you have to wait for 30 seconds because I can't determine if all enemies are dead. There are currently two ways of improving this, firstly make a list of all bleed/stone/effects which can cause dmg without being associated with any particular enemy and the other is to use the combat state from the in-game plugin to notify the C code that the combat is over.

3. Calculating the correct DPS around the time a combat ends is horrible, the problem is that often the log messages are out of order and lag, hence you might get a notification that a mob died but continue to get dmg messages for up to 2 seconds after the mob is dead. My solution for this is that the combat isn't officially considered over until 3 seconds after a death message is received, however dps stats will not be recalculated unless you take or deal damage in those 3 seconds.

4. History DPS (hdps) is the total dmg dealt since the plugin was started divided by the total time spent in combat, I felt this was more accurate than simply averaging the DPS from all combats.

5. Glad the plugin is of use, hopefully I'll find some time to continue working on it when RL slows down a bit.

Jarl

Evendale

Yes it is a disturbing stone name, but hey, its not my stone.

In terms of combat ending, what you said before about letting the game notify your app when combat starts and ends is definitely doable.

I've been working on a similar plugin (but that allows you to connect to multiple people and share info so you can compare dps in game in real time), and I dealt with combat ending in two ways:

1) By writing to a file everytime combat is entered or exited in game (has to be done in a separate plugin to avoid the save delay of course).

2) Including any damage done 2-3s after this point, but not incrementing the duration by the same amount.

vindalfur

I have just uploaded version 1.1.3, this has been in the works for a while now.

First of all the in-game plugin now supports full IM log functionality, this means timers and messages, see the readme file on how to use timers.

I've also done a major overhaul of the plugin UI, enabling much more customization with additional data elements and tooltips.

Several bugs have been fixed aswell.

Remember to remove any previous versions before running the installers.