|
|
Post by synan on Dec 7, 2007 17:02:40 GMT
That is cause you didn't get hit, it updates on hit  Actually I would've thought that would be because there's no message in the logs that states "0% conceal" for a parser to pick up on when your conceal runs out. I suppose you could search for attacks against the player (over a certain period of time) and if "target concealed x%" doesn't come up after while, revert to 0%? You are actually completely right, I haven't done the code that reverts it back to 0. Altho if I did, it would still do so only on the next attack that wouldn't have conceal mentioned. I will do it sometime next week, got some other pending stuff. |
|
|
|
Post by synan on Dec 7, 2007 17:08:35 GMT
Just a quick suggestion - it would be nice if you could rename it (and the rar file) to something like 'nwnlogwatcher-1.0'. I actually have three other programs called logwatcher for various things, and 'current-1.0' doesnt tell me much. Looks like a great program, though. I've downloaded it and I'm sure I'll offer a couple of patches. Thanks, Acaos Well, I was thinking about a _real_ name but have failed to think one up. If anyone has any ideas I'd be more then glad to hear them  Btw, links to sshots are also more than welcome! I look forward to any patches you make Acaos, would be a priviledge to include the code. (Didn't know you did python? ) Mrbadexample: just try a few times and see where it ends up when you put it somewhere. You'll hit the right spot and will know where to put it next time. I haven't heard of any gfx problems till now, I'm guessing it's something to do with windows/drivers. Anyways, just learn where it should be and problem solved. |
|
|
|
Post by cataclysmic on Dec 7, 2007 17:30:32 GMT
How about Syn's Discovery? |
|
|
|
Post by jalking on Dec 7, 2007 18:07:48 GMT
used it on two ssith and a desert run today and it seems to work fine...
Only stat that never showed anything (apart from the spellcasting specific ones as I used a tank) was the phys and elemental buffer stats... they never left zero.
I had a couple of surprices when I saw the damage types hitting hardest on some specific monsters, this is a good tool for my AA.
|
|
|
|
Post by bort on Dec 7, 2007 18:20:35 GMT
Actually I would've thought that would be because there's no message in the logs that states "0% conceal" for a parser to pick up on when your conceal runs out. I suppose you could search for attacks against the player (over a certain period of time) and if "target concealed x%" doesn't come up after while, revert to 0%? You are actually completely right, I haven't done the code that reverts it back to 0. Altho if I did, it would still do so only on the next attack that wouldn't have conceal mentioned. I will do it sometime next week, got some other pending stuff. Care to share how you intend on doing this? I know it probably goes against your whole 'rivalry' schtick, but I'm curious if there's actually a reliable way of doing it beyond simply reverting to 0% after a certain number of attacks if the 'target concealed' string doesn't come up Cheers, -Bort |
|
|
|
Post by Trazik on Dec 7, 2007 18:57:38 GMT
A few more suggestions, one from Phalthallus, and one question from me: - would be nice to be able to select different targets and review "what this mob did to me". Presumably this would be done after NWN is shut down, cuz clicking on the window minimizes NWN. - What happens when the cumulative amount of damage exceeds 10 000? It is possible. Many hell runs will achieve this in multiple elements. It just looks like their might be a shortage of space. There should somehow be a way to prevent clicking on the window from minimizing NWN. Xfire can do it, so it is presumably just a matter of figuring out how it is done. Nice work, and looking forward to testing it in hell Trazik |
|
|
|
Post by cataclysmic on Dec 7, 2007 19:10:48 GMT
Jalking - If you were playing a tank then you possibly never had any phys buffs? It refers to spell buffs I believe, using my DD I have seen that my phys resists from gear don't show up but soon as some one casts stoneskin on me bingo next time i get hit the phys buff shows. Would think same for Elem Buffs too, did you have any elemental spell buffs up? Can't remember if I have seen it working with shunt lol. Trazik When amount of damage exceeds 10 000 I believe it reverts back to zero. However I have only ever seen this happen once, during a very painful Min run in which tears kept getting split and yes it was Acid that went over lol. I have done Hell a number of times with the Log Watcher up, as have a number of guild mates and no one has mentioned this as being a problem so I wouldn't think this would be too big an issue. As regards space well it is a little compact mainly to keep it as small as possible so that it takes up as little game screen as possible. Covering half ya game screen just wouldn't work hehe and would kinda make the fact it runs on top of game pretty redundant, and yep I have even had it on in Nessus. As for the bit about what did what to me I'll leave that to Syn hehe. Tis his baby and I aint got a clue bout programming. Any one with turners - One thing to note, am not sure if Syn intends to change the turning check or not but if you are using this with a turner please remember that battletide has an SR check so if ya got that up it will keep bringing up the stats for that spell so when turning if ya wanna see SR ya need to keep checking logs lol. Tis a bit annoying but works fine for now. P.S. The SR bit is also the TR bit it just doesn't say it is TR Edit: The Idiot Guide will be done this weekend and posted here either Sat or Sun lol |
|
|
|
Post by zerragon on Dec 7, 2007 19:21:01 GMT
Excellent work Synan ! Installed and worked like a charm on first try. Will test in on a Nessus run (hopefully) tonight. |
|
|
|
Post by synan on Dec 7, 2007 20:26:07 GMT
You are actually completely right, I haven't done the code that reverts it back to 0. Altho if I did, it would still do so only on the next attack that wouldn't have conceal mentioned. I will do it sometime next week, got some other pending stuff. Care to share how you intend on doing this? I know it probably goes against your whole 'rivalry' schtick, but I'm curious if there's actually a reliable way of doing it beyond simply reverting to 0% after a certain number of attacks if the 'target concealed' string doesn't come up Cheers, -Bort It's not that kind of rivalry If you open the .py file in an editor you will see the entire code is visible, and is released under the GPL license - Free Software. Rivalry in terms of who does what before others is what I meant, and as I am/have been involved in a number of free/open_source projects I have found that to be the main motivation for inovation. I don't currently know if there is a more reliable way than doing just that. I figure if you have conceal you have it on every attack, even the first attack that hasn't got the conceal mentioned should mean your conceal is gone. I might be completely wrong, but I will know only after I siff through some logs and see what's actually happening. Doing all this has made a great impression on me that nwn logs weren't meant to be parsed, it's just way too messy. And all that splitting the log into 4 files? What's THAT all about. The whole logging system is just wacked. So basically, any and every log parser anyone writes is bound to have problems and maybe even unresolvable ones. |
|
|
|
Post by synan on Dec 7, 2007 20:36:32 GMT
- would be nice to be able to select different targets and review "what this mob did to me". I think there already is an offline log parser most people are using that works fine from what I hear, I don't intend to duplicate code. So no, I won't be doing that. Well, not really necessery. I can modify the entire logwatcher window from the in-game talk function. Like .reset works, for example. Well, I will check (I think I did check it already but will again) and it was a matter of space. I will adjust the size to fit if that will be the problem. Cata: It should _NOT_ however revert to 0, that is not even possible. It could be a matter of numbers just beeing hidden to fit the space. I will check on that. I will check if I can somehow do that, but don't hold your breath. GTK is not using the windows API to draw it's stuff and as the whole overlaying the game is actually a "hack" of a sort (even in the xfire case) unexpected things can happen and some limitations might exist to what I can actually do. Thanks! Thank you all for your input and your compliments, I'm really excited about all of this at least as much as you are. ( now if I could just figure how to actually _use_ the damn thing on KDE ... ) |
|
|
|
Post by bort on Dec 7, 2007 20:36:34 GMT
It's not that kind of rivalry Hehe, good to know, was only joking btw I don't currently know if there is a more reliable way than doing just that. I figure if you have conceal you have it on every attack, even the first attack that hasn't got the conceal mentioned should mean your conceal is gone. I might be completely wrong, but I will know only after I siff through some logs and see what's actually happening. If every attack against you mentioned conceal, that'd mean you had 100% conceal. If you have conceal up the logs show either "(mob) attacks (character name) : *hit*" "(mob) attacks (character name) : *miss*" or "(mob) attacks (character name) : *target concealed: x%*" Miss comes up if they beat your conceal but not your AC/or when they roll a 1. Hit is when the hit is in the % that isn't affected by conceal and they beat your AC/roll a 20. When your conceal is down the log shows either hit or miss based on your AC/their roll. Hope that makes sense... Cheers, -Bort |
|
|
|
Post by cataclysmic on Dec 8, 2007 5:27:10 GMT
Re: A problem Semaj was having with the Log Watcher, when he loaded it up he got a blue flashy screen and his frame rates went right down, am not sure what causes this but it happened to me when we first started to test this. I found simply alt tabbing thru to the NWN Game fixes this problem, I had thought it fixed as I haven't had this problem for the last month. I'll make sure Syn knows about it and see if it can be 'fixed'.
In the meantimge if any one else comes across this problem can you let me know thanks
|
|
|
|
Post by Trazik on Dec 8, 2007 7:42:46 GMT
Feedback after using this in Nessus last night ...
Damage output for my RDD (wish I thought to capture it with a screenie):
Physical damage 100k+
Fire 1000+
Cold 10000+
Acid 10000+
Sonic 10000+
Magic 1000+
Elec 1000+
Positive 0
Negative 1000+
Divine 10000+
With numbers like that, they get squashed together and difficult to read. Therefore my colour-coding idea mentioned earlier would really be useful (IMHO).
Death/limbo timer was very useful since we hit 2 really nasty randoms (1 in Maze, 1 in Coil). Number of Kills was a "fun fact" and was nice to compete in a friendly way with my party mates (Turners rule, though).
Nice work!
Trazik
|
|
|
|
Post by Trazik on Dec 8, 2007 11:04:15 GMT
 Phleg run this morning, after I figured out how to capture this (pasted into MS Paint and uploaded to a photo share site). Phleg is not such a long run in terms of time and mobs to be killed. The numbers kind of run together towards the end. Trazik |
|
|
|
Post by mrbadexample on Dec 8, 2007 11:41:34 GMT
Got my issue fixed needed to alt-tab like Cata mentioned. Guess I wasn't really paying attention to much :-(
I would like to make a suggestion could you add descritions to the different rows in the damage counters so that you can tell at a glance what they are?
|
|
