LogWatcher by syn

[MurphysLawAgain]

Into the normal NWN talk bar. either /w or use Whisper as a conversation type with .reset damage or .reset stats

[synan]

Version 1.1 is out and gives you:

- color coded damage counters
- smaller size

Enjoy!

[requiem]

wow. guess i'll give this a try now.

[requiem]

Very nice synan this thing is awesome. one thing though it displays my AB but not my SR? the character I was using it with has a 70 SR. or is that only against enemies that cast spells?

[cataclysmic]

Req

The SR wont displayt anything when using ya tank, it is for casters, It shows the SR of the last creature you cast a spell at, after in brackets it shows your SP roll so you can see instantly if you beat it and by how much.

In the case of a turner it would show Creature TR with your Turning Power after in brackets.

In other words, tanks get an AB show and Casters get an SR(SP) Show

[omino23]

I installed and am using this and have to say I am most impressed. No problems with install and running it works great. My only issue seems to be with getting the parser display info to stay where I want it. I am running nwn on a lap top and I can use both the large screen setting where the parser info should "stay where you put it" and also the smaller 800 setting where it will not stay where it was placed on the desktop. I have tried playing with putting the parser in different locations but when I start nwn even if I get it exactly where I was hoping it would show up it looks for lack of a better word "blinky" (like it is semi transparent and blinks back and forth). I know my desktop size and either of the nwn settings are not the same but I can run it in the 800xsomething mode and also the thousandsomething x something mode (don’t have my laptop or nwn open right now) but in either case I cant get the parser info to come up where I want it and look good. I can get the parser to be clear and run if it is in the middle of the screen blocking my view of combat. Any advice?

[cataclysmic]

I put it at bottom right of my screen and in the larger screen settin, not the 800x summat one, if it is blinking on you ya got same prob as Mr.BadExample had but woithout the blue screen, just alt tab back to game should clear it. If it actually moves position try useing the next resolution up. Only other thing I can think of is you are placing it at the very edge of the screen, this can sometimes make it jump to a different loacation for some strange reason, try making sure there is at least a bit of a gap between log watcher and very edge of ya monitor screen

[synan]

There's a know issue about fugue timer making the lower damage row disappearing in the 1.1 version. Looks like I made the window a bit too small

Anyways, will be fixed in the next version.

Cata explained the resolution thing quite well, I will only say that you can get the right position of the logwatcher on resolutions other than 1024x768 by sacrificing 60 seconds of your time and try to see where it jumps and then alt-tab the game and adjust the logwatcher window a bit. It will take a few tries but you'll get the exact position where you have to put it for it to be in the right place in other resolutions (another place for every resolution ofcourse).

This is because placement of windows is made by pixel distance from the edge of the screen (left and top if I'm not mistaken) and that doesn't change, but the number of pixels change when you switch the resolution (from 1024 to 800 for instance).

[synan]

Version 1.1.1:

- minor update, fixed the fugue timer pushing the last damage row out of the window


Enjoy!

[omino23]

I edited my desktop background picture to have a little red line where the edge of the log parser will go and now have no problems, thanks again for providing so much information.

[synan]

omino23 said:

I edited my desktop background picture to have a little red line where the edge of the log parser will go and now have no problems, thanks again for providing so much information.

Haha, a very nice hack

[bort]

Hey Syn, I'm working on the Fugue timer for my parser, and wondered how you'd coded around Insta-res epics (Contingency, Eternal Return, Possum's Farce) and also stones of rebirth, as these seem to reset the Fugue timer when they go off (unlike res scrolls afaik)..
Do you parse for the message these events send to the logs and stop the timer or do you have some other method?
Cheers,
-Bort

[synan]

bort said:

Hey Syn, I'm working on the Fugue timer for my parser, and wondered how you'd coded around Insta-res epics (Contingency, Eternal Return, Possum's Farce) and also stones of rebirth, as these seem to reset the Fugue timer when they go off

Hm, wasn't aware of that, never had that information. Is this certain? I'm guessing there should be a way to check for that. I would check the logs but my home connection is gone for now and I can't really get to any logs

[bort]

I tested it by sending an immortal wizard (with contingency) out into Vashyk's ruin and getting killed.
At this point my parser picked up on the "someone killed me" message in the logs and started my fugue countdown timer but I also got straight back up thanks to contingency.
There was a message in the logs at this point mentioning something about Contingency, but I don't still have that log to get the exact message. I'm pretty sure there are similar messages for Eternal Return, Possum's Farce and possibly Stones of Rebirth.

I ran back to the crossroads, waited until my timer had roughly 30 seconds left on it and went back into Vashyk's ruin and got killed again.

If the fugue timer hadn't been reset, I would have got up again when that 30 seconds ran out (due to immortality, otherwise I would've fugued), but instead I lay there for the full length of a fugue timer again.

I'm going to do more testing, but that's as much as I've done so far.

[synan]

Thanks for the info, that means we only need to compose a list of instarez items/effects and check for their actions in the log.

I'm trying to get something done regarding concealment but I'm looking at an excerpt from a huge log and can't really get a pattern that could be used, nor a "safe" number of attacks after which the concealment is definitely down.

Hit is when the hit is in the % that isn't affected by conceal and they beat your AC/roll a 20.

I'm not sure I understand this right. Could you try to explain it a bit? Is the concealment mechanism just coded without logs showing it (meaning the attacker only gets to roll to beat your conceal 50% of the time if your conceal is 50% but there is no actual roll on your side to see if the conceal should kick in) ? If it is so, I don't think there is any way you can say for certain when your conceal is off.

Some devel help clearing things a bit perhaps?