PDA

View Full Version : Filters.conf - need a little help



Blade_DSS
12-28-2001, 02:37 PM
I am working on putting together a nice, alphabetical, commented list rare spawns in the Filters.conf file. I already have a older list that has a majority of spawns in it already. I am cleaning up some spelling mistakes and organizing it with plans to repost it back up here to the board.

I do have a question regarding how the file is parsed.

For example, if you have the following:

[Alert]
Xalgoz

This will not only report the head vampire of kaesora, Xalgoz, but will also circle Minion of Xalgoz as well on the map and in the Alerts. Is there a way to differentiate?

Blade_DSS

jection
01-01-2002, 09:07 PM
not sure... but would love somone to post a good working filters.conf

Zaphod
01-01-2002, 10:36 PM
In your example it will match any occurances of Xalgoz that occur anywhere in the filter string. Make sure that this is what you want. If you want to limit it to just those occurrances in the Name field you might want to use:


[Alert]
Name:[^:]*Xalgoz[^:]*:


Basically this reads as match the literal string "Name:", followed by 0 or more non-colons, followed by the literal string Xalgoz, followed by 0 or more non-colons, followed by a colon.

Look carefully at the information in the latest filters.conf.dist file. You also may want to lookup information on POSIX style regex, if the appropriate info files are installed you can find it by using the command:


$ info regex


and navigating around the information contained therein.

Enjoy,
Zaphod (dohpaZ)

Soladan
01-03-2002, 11:43 AM
Where can I find the format of the filter string?

I'm assuming it is something along the lines of...

Name:{mob_name}:Race:{mob_race}:Class:{mob_class}. ...

or something like that. Is it documented somewhere?

edit: I see that this info was recently added to the filters.conf.dist file.

KennySP
01-03-2002, 11:52 AM
Read the filters.conf.dist file for the syntax.

PawnOrc
01-03-2002, 12:55 PM
Please make your new list available so others can benefit. Also, if you know of anyone elses list that looks good, please provide links. Lots of us mutton heads could use some help in the filter department.

cjd1
01-04-2002, 09:39 AM
Right-click on a spawn in the spawnlist to see it's entire filter string which gets matched against the pattern in filter.conf.

Blade_DSS
02-08-2002, 09:07 AM
I followed the posix syntax (at least I think I did) and it is still not working correctly from what I can see. Here is a filter example:

Name:[^:]*Deep[^:]*:

I have this in both Alert and Caution and not only do I get "Deep" to register, but also "deepwater barracuda" blinks as well.

Any help? I want to get this filter file cleaned up so I can get it to everyone.

/bump

Blade_DSS

Mr Guy
02-08-2002, 09:33 AM
Ok breakdown:

First showeq filters are case insensitive so 'D' matches 'd'

Secondly break down of your syntax:

Name:[^:]*Deep[^:]*:

Name: #(easy hard match to Name:)
[^:]* #0 or more characters that are NOT a semicolon
Deep #hard match, but remember insensitive so matches deep dEEp dEeP....
[^:]* #again, matches 0 or more non semicolons
: #semicolon


Whats messing you up are those wildcard matches. You know the name is delimited by semicolons, but you also know that it's of pattern :SPACENAMESPACE: Those wildcard matches give you flexibility if you don't know the exact name or want to match more than one name. IE deepwater goblins AND deepwater barracuda AND etc... Since you only want to match a very specific name, just nix the wildcard matches for an exact match:
Name:\sDeep\s:
which reads:
Name:SPACEDeepSPACE:

Another interesting match would be if you wanted something that ended or started with something, but you don't want it to match if it appears in the middle. Then you would use the word boundry escape: \b

Name:[^:]*\bgrif[^:]+:

That should force a word to begin with grif and have something after it. In other words, griffon would match, so would grifin, but Komgrif wouldn't, nor would grif itself.

I haven't tested \b in showeq, but it ought to work.

Blade_DSS
02-08-2002, 09:52 AM
Using the following example you gave:

Name:\sDeep\s:

Shouldnt then also:

Name:\sdeepwater barracuda\s: match as well. When I enter this string it doesn't.

What I am trying to accomplish is to setup literal text strings for all of the named mobs in the game. In a couple of cases I will need to add race as well due to the fact that some mobs are duped (as in Goblin Warlord in Runieye and Goblin Warlords in LoIO). I am close, I can feel it.

Additionally, I have the case sensitive matches turned off in the showeq.conf.

Dedpoet
02-08-2002, 12:11 PM
I was playing with my filters last night and ran into this same thing. Don't put a space after your first colon. As an example, I was hunting crag spiders in East Karana and my working Hunt section looked like this (items in parantheses are my comments - don't type those):

[Hunt]
Name:crag spider, a (makes all crag spiders flash white)

Or this:

[Hunt]
Race:Giant Spider (makes all giant spiders of any kind flash white)

This did NOT work:

[Hunt]
Name: crag spider, a #note the space after the colon.

Also, I found the best way to edit this file is to not have seq open, and use an offline text editor to do it. Seq will overwrite your changes if you edit while it's open and then exit. Edit your file as shown above - you can put in your [Alert] section if that's your preference, save the file, then fire up seq.

/em goes back to lurking.

-Dedpoet

BlueAdept
02-08-2002, 05:28 PM
Since filtering was brought up again, I thought I would remind everyone that my filters.conf file, zone specific filters, libeq.a and some other stuff are on my web site.

http://www.seqstuff.cjb.net (forward to main) or
http://www27.brinkster.com/blueadept (main) or
http://www.crosswinds.net/~libeqa (mirror)

If you find any mobs that are incorrect or should be added email me at [email protected] and Ill get them on there.

Currently I do not have ANY luclin rares. If anyone can help send me them it would be really beneficial to everyone.