BE filters inconsistency?

[WalkerDown (DayZ) 296]

I'm trying to understand why the BE filters works sometime and sometime else it doesn't, especially with the filter trigger exclusion. Does anyone knows the magic?

Example:

Line in the log the users are being kicked for:

RemoteExec Restriction #8 "Hit" 23:173 Survivor2_DZ - "_this spawn server_playerHit;"

Line that matches the kick (the word "play"), but with the exclusion of the exact variable above:

5 "play" !="_this spawn server_playerHit;"

I've also tried to remove the "=" (should it makes difference between names and contents?):

5 "play" !"_this spawn server_playerHit;"

...the users are still kicked. Does anyone know why? In other circumstances it works fine.

[icomrade 201]

You missed SPAWN...

[WalkerDown (DayZ) 296]

You missed SPAWN...

This is about line #8 (actualli row: 9), it has nothing to do with "spawn", the keyword is "play".

[facoptere 180]

check restriction number. is it still #8 after your first fix?

you missed "_this" also ;)

[WalkerDown (DayZ) 296]

Oh ppl.. i love the fact you try to help, but please reading what i've wrote before? :)

the line is the #8 and it's about the keyword "play" .. it has nothing to do with "spawn" neither with "_this" .. that are on very different lines.

Thanks for have tried to help anyway. :)

[Guest Dwarden]

remember the # mentioned is not line number

kick #0 is line 1

if any line starts with // it adds +1 to counter

so for your modification need cover lines with

5 "play"

5 "spawn"

1 "this"

and add to each

!="_this spawn server_playerHit;"

Edited February 25, 2013 by Dwarden

[WalkerDown (DayZ) 296]

Dwarden, if you read two message above, you'll notice that i've specified the line #8 "ACTUALLY ROW: 9" << :)

...plus "spawn" and "this" are much lower in the file, there's no way you can confuse it with #8 ..unless you lost 99.9% of your brain at poker, or you never learned basic math (actually counting) at school. :)

[Guest Dwarden]

i gave generic explain how the filters line counter works and how to cover all 3 possible spots of kick

i don't have time to analyze every damn post

if you ask about the difference between !"" and !=""

the !"" means partical match and EVERYTHING behind the content of "" will be ignored (so it opens backdoor for exploiting that detection)

that's why exact !="" was introduced but if there is other code or variable around it then it might result into kick (typical example some of the inventory

it's not perfect system and w/o complex RegEx it's limited ...

hence why so many admins utilize 1 "" logging as addition to BE filters (BE filters have advantage to be able block and drop the command before it executes)

and then parse this 1 "" logs e.g. with perl

[Near (DayZ) 0]

thx, we work on it

[WalkerDown (DayZ) 296]

I've found the strange behaviour, at least of that exact occurrence, while updating to 1.7.6 i spent some time to analyze every single filter and i've noticed that two of them were almost identical (well not exactly.. but most of the lines were the same). They were mpeventhandler and remotexec, and here's the strange behavior: some of the remoteexec matches (so that #8 "play" line) are logged into mpeventhandler.log ...for some exotic reason (it doesn't appears to be a bug, it's just how they decided it should works, probably for a matter of consistency).. so i were adjusting the line in the filter that matches with the log, while the filter were in fact in another file, and what add more confusion is the fact that those two files has that line at the exact same row.

[Guest Dwarden]

remoteexec and mpeventhandler logs are separate, don't mismatch them ...

Edited February 26, 2013 by Dwarden

[WalkerDown (DayZ) 296]

The "play" trigger logged into the mpeventhandler.log is read from the remoteexec.txt list, whenever a remoteexec.log exists too. That's why i've lost two days to figure what was wrong, i were adjusting the "mpeventhandler.txt" ...the reason of why it happens is beyond me.

[WalkerDown (DayZ) 296]

Apparently BE logs the trigger in the mpeventhandler.log, whenever the filter is contained in the remoteexec.txt, because the complete line (reported) is: "MPEventHandler RemoteExec Restriction #" ... so instead of being logged in the respective log file (remoteexec.log) it goes to the mpeventhandler.log coz (im guessing here) it matches that event name. Whatever is the reason it's wrong: if a filter is contained into the "sometext.txt" .. it should be logged into "sometext.log" .. and not somewhere else, or you'll loose (like me) days to find what's wrong. The only excepetion is about the variables log.. but only because it has two separate files (for names and values...).

[Guest Dwarden]

what about some 'make sense' bug report type, so Bastian can fix it ... cause honestly I have no idea what you talk about

Edited February 26, 2013 by Dwarden

[WalkerDown (DayZ) 296]

Some of the keywords triggered from the remoteexec.txt filter list, are then logged into mpeventhandler.log (and not in the remoteexec.log as you would expect). Can't be more clear than this. :)

Example:

You put this into your remoteexec.txt:

5 "test"

The user is being kicked for:

MpEventHandler RemoteExec Restriction #0 "Hit" 23:173 Survivor2_DZ - "test"

The above line is logged into mpeventhandled.log (but the filter, has mentioned above, has been read from remoteexec.txt).

Edited February 27, 2013 by WalkerDown

[WalkerDown (DayZ) 296]

OFF TOPIC: dwarden you have a pvt msg .. not sure if you have PMs enabled (or the inbox full of msgs) so i'm writing here.