LogWatcher by syn

[Yomi]

I was reading through the rules again today and saw that [1.d.i] as well as two mentions of deleveling RDD's messing up the character [1.c.iii and 2.d.iv.1] which is now no longer allowed.

[cataclysmic]

Syn just to let you know the patch didn't fix it, my Log Watcher still says V1.1.1 and still doesn't Death counter and Fugue timer still doesn't work :/

[FunkySwerve]

sti15 said:

I was reading through the rules again today and saw that [1.d.i] as well as two mentions of deleveling RDD's messing up the character [1.c.iii and 2.d.iv.1] which is now no longer allowed.

Thanks, will fix.
Funky

[synan]

I was reffering to something that I haven't seen documented, the way you die has been changed. You now don't acquire the item "Death" but you get killed in this way e.g.:

Bandit killed Child of Syn

Cata:
I have to check why it's not working, worked for me in my test.

EDIT: found the problem, it's my stupidity. Altho I can't fix that, I fixed the problem and it will work as of the next bugfix version. For now it only works for toons that don't have a space in their name. Update due tomorrow.

[synan]

Version 1.1.3:
- fixed multiword toon names having problems with death counting / fugue timer

[rump]

Just a question...Is it possible to have the parser remember the last location it was put in, so we do not have to constantly replace it when we run it?

[synan]

Yes there is. I can do that, altho I can't say when. I'm currently dealing with deadlines and emergencies and spend most of my scarce free time on playing instead of coding.

[Trazik]

Dunno how to go about asking this .... but here goes

AVG found I-Worm/Nuwar.C worm in one of the file we have to download for this tool.

I certainly do not want to misinterpret what this could mean, but people should seriously check the file fc-cat.exe which goes into the GTK\bin folder.

AVG has picked up false positives before, but this is a worm that has been making rounds lately and I suspect it may not be a false positive.

I am a bit puzzled why this was not picked up on Tuesday when I spent the whole night away from HG, scanning my system for visuses and spyware. My problem was my connection, nothing more.

More info here on AVG's website

Trazik

[cataclysmic]

Trazik already told me about this and I'll make sure Syn knows about it incase there is a problem with the Log Watcher. I've already scanned both my own and my wifes system and found nothing so hopefully it didn't come from downloading the log Watcher and stuff :/

Ya'll may wanna check ya systems tho just incase.

[synan]

Okay, I've looked around a bit and here's what I think.

It's most probably a false positive, or the worm somehow infected that file (altho I don't see it's capable of doing that from reading the various technical summaries from various AV vendor pages).

I don't think people need to get alarmed, you've had that installed for months now, and it's downloaded from a verified source, hundreds of thousands use that GTK distribution, and my company uses it for every application we write.

It's most probably Trazik got either infected in another way (I see it spreads via spam links) or AVG is getting a false positive, of which I think the most chances are for the latter.

[synan]

Version 1.2:
- hopefully fixed the fugue/death counter reflecting the changes done to the way you die
- fugue timer now counts from 5 minutes reflecting the changes
- added the option to make it remember it's position, when you place it and run the game whisper ".sticky" (without the quotes)



Found the cause of the issue where damage buffers sometimes wouldn't show, use the !filter imm command (thanks to Acaos for pointing that out!)

Enjoy!

[BigStick]

Synan: Three things -

1.) Awesome work! I had no idea how much I was missing until I started using this.
2.) My version is missing the third line of damage (Total done to me?), but has the first, second and fourth. Any idea why that might be?
3.) With all the requirements that had to be installed to run this app, do I now have what's needed to do my own Python development? I was thinking about teaching myself over the weekend if I could code in it now.

Thanks!

[mrbadexample]

Great work again Syn, I have a few questions for you though.

my first one regards the .sticky command. Does this make the watcher remember it's location at all times or only while it is running? I ran the program and loaded nwn got the watcher in the location I wanted and used the .sticky command. To test it I closed both and started them back up the watcher was back in the middle of the screen instead of where I wanted it to stay. Maybe I'm missing something I'm not sure.

Second question do you or anyone know how to setup nwn to load the logwatcher as well? I've tried to create a batch file that runs both nwn.exe & logwatcher.py only to have logwatcher die with an error I can't read cause it closes so fast.

Edit Finally got a screenshot of the error I was getting, took me a dozen tries

[dragonlance007]

Hey there Synan. I have been using your log watcher for about a month now and have really enjoyed it. Well done mate.

There is only one problem I am having and I am not sure if it has been addressed before (dont have time to read 9 pages of this thread) but whenever I fire up the log watcher and then load NWN and go ingame everything works great but my game is much much brighter than it should be and my gamma correction in the game options does absolutely nothing.

Some times this has happened to me in the past (before log watcher) if an email notification pops up while I am playing or I have to alt tab and come back to NWN but in those cases I could always alt tab or windows key back to the desktop then click the minimized NWN and it would come back up back to normal.

But when I have the log watcher going no amounnt of alt tabbing or going back and forth from my desktop back to NWN will cure it...

I am running an ATI card if that makes a difference -shrugs-

Thanks again for this wonderful and useful tool, if I can get this brightness issue worked out I will be in heaven.

~DL

[BigStick]

DL -

I have brightness issues when alt-tabbing or starting up with the watcher running as well, but my problem is that the NWN screen gets much too dark. Going into the Video options and tweaking the gamma correction fixes it for me however. I have noticed sometimes that the gamma correction tends to "spill over" to my regular desktop on occasion, generally in the case of a NWN crash. Restarting the game will fix this for me.