Chat Handler [Unmaintained]

The "Anti Server Listing" part, what does it look for exactly? If I type "123,000" on my server, I get a warning for advertising.

 

You're right. I need a better match pattern for this. I'll try to post an update later.

 

Im not sure whats causing this but I get big lag kicks when this error happens..

log is attached this is on my second server.

 

Fix your Evolution plugin first or remove it and post if the error still occurs.

 

we are working on the evo and evo is not on the 1st server and get similar errors
we are aware if evo crashes we fix it before it does....
I have the echo1 caped at 115 player because when it gets higher then that with players then the friendly fire goes nuts I guess with all the extra player..

 

Well in the log you posted this evo plugin is throwing a ton of errors and the .Net exception can very well be caused by another plugin.
The problem with the .Net exception errors is that its impossible to locate the error if i dont know in what exact situation its erroring. Oxide's error reporting is pretty bad at the moment.

 

This "Evo" plugins is "throwing" ton of errors because im working and testing a lot of crap on it and mostly throw each time is uploaded however like my fellow Upperking is trying to explain the errors is not throwed only in the server where i'm testing my plugin also in the other server where there is no trace from my plugin or anything. And about the .NET exeption i think there is some problem your pluging working with http://oxidemod.org/resources/logger.670/ . However we removed it but still im not shure from what it is probably from something that is interiupting with your plugin....

 

yes i know that why its hard to figure out who and whats causing it. I wish I could see exactly whats causing it because it causes a domino effect then all the plugins one by one start to fail..

[Oxide] 11:09 PM [Error] chathandler: [string "chathandler.lua"]:449: attempt to call method 'GetString' (a string value)

 

Does it still error a .net exception after removing the logger plugin?
Both plugins are interacting with the chat so it might indeed be a compatibility issue.

 

Mostly the .NET errors was going insane when the logger was enabled however when it was removed the things chill out. So yeah I'm also thinking that maybe is causing some compatibility issues with it but is also possible to have some rare cases of other issues with plugins interrupting with chat.

 

Make it better then, one part were it can be improved is in the CallLuaFunction method in the class LuaPlugin.
Instead of throwing the exception you could have it do the logging there for debug purposes, or have it log the function name and args.

 

You dont always have to do it better in order to criticise it.

 

Domestos updated Chat Handler with a new update entry:

Bugfix and improvements

 

when a nickname is, the characters "{}", it turns out like this:

[DOUBLEPOST=1415570110][/DOUBLEPOST]Filter words is not quite working properly. It replaces even the word for word.
For example:
["бля"] = "***"
In chat:
"Взрослых нужно уважать и немножко оскор***ть"
[DOUBLEPOST=1415570272][/DOUBLEPOST]And more. You can make the words in the filter case-insensitive?
For example I have a list of words in 3 variants of one word:
["БЛЯ"] = " я у мамы дурачек ",
["Бля"] = " я у мамы дурачек ",
["бля"] = " я у мамы дурачек "

 

The error when something contains {} is a Oxide core bug. You can workaround that by now by setting logging to oxide false in the config. Wordfilter is working fine and it is already case insensitive, it simply doesnt work for non latin characters like russian. There is no way for me to change that.

 

Domestos updated Chat Handler with a new update entry:

rust update

 

Domestos updated Chat Handler with a new update entry:

permissions

 

Oxide] 4:06 PM [Error] chathandler: invalid arguments to method call
at NLua.Lua.ThrowExceptionFromError (Int32 oldTop) [0x00000] in <filename unknown>:0

 

These kind of errors are often caused by other plugins who arent working properly.