What is this file and why am I getting this error?

Quote:error parsing pbucon.old
index and length must refer to a location within the string.
parameter name: length
pb_sv_plist result detected

Sometimes the scanner will stop working and fail to see words etc that people type. While other time it won't start at all.

I THINK i have everything installed correctly. However I checked the pbucon.use file on the server and the sessions limit was set to 0 (yet it still works fine and does the right thing MOST of the time, and when i changed it to 1, it wasn't working at all!)

ANND the pbucon.use file in the MORKEye folder has absolutely nothing in it (it's blank). Yet sometimes it still works and does an EXCELLENT job keeping the server clean. If I could work out these two issues it would be awesome!

PS - One minor question too, is there a way to get rid of the constant
.
.
.
.
in the log folder? That makes it use SOO much space that i wish I could have back! Thanks alot!

to stop seeing the error messages you need to turn off 'diagnostic logging' in the XML settings... You can also turn off the '.' (ticks) in there as well... As for the pbucon.use file, it's meant to be empty, it just has to exist in your games PB folder.
Lastly MORKEye should manage your session limit for you.

Ah, so there is no way to actually fix the error? That was more what I was wondering then anything.

When I uncheck log tickmarks, they really don't go away... Any help?

all the error is actually saying is the pbucon.old file doesn't exist therefore there's nothing for the program to parse... And the reason it doesn't exist is simply because pbucon has nothing to report at that time... When this happens in diagnostic mode I treat it as an error and report it. Its just an indicator of what's happening internally an needs to be taken in context with other errors as on on its own it means very little.

As for the 'ticks' I will look into it... they are just a confidence check when things are quiet and since each one takes up 1byte of space and they happen once every 2 to 3 seconds then it would take 10,000 ticks to create 10kb of data I don't see how they would cause a filespace issue... I've had this software ruining for weeks on a busy server and only generated logs of a few Mb in size.

I figured the tick thing out. In the actual scrolling monitor on the program they don't go away, but on the log.txt file they go away, so all is good and dandy on that end!

However, i'm starting to see words slip through the cracks even though they are exact matches. Like for example i added 'bs' to the list, and there have been a number of occasions where it goes through, or doesn't even recognize that the person said anything. Is this a glitch or some minimum character length that i don't know about?

Each word in the banWords.txt file currently needs to be 3 or more characters in length. I will look at the code to see if I can reduce this to incorporate 2 letter words. However two letter banWords will have to bypass the heuristics as it will cause too many false positives.