next »

[tynman]

I cant seem to find how to adjust how long warnings stay active?  Seems that ppl have warnings for weeks on our server .



Also I was hoping someone could tell me how to change the title of who is doing the action like !w . would like it to say B3 Admin , or |BC|Admin. ?


many thanks .

[click]

admin.xml. or something close to that.

[ThorN]

Some warnings are supposed to stay active for weeks. Each warning has a different delay. Some warnings are so offensive that they stick around a long time.

[tynman]

That is true but I made the rules cant I adjust to how long each is active ?

I mean I understand keeping it active for weeks for things like racism but I have some custom rules that I dont think they need to last that long.

and is the second possible ?

since im asking so much I have another Question I am having problems kicking ppl from the server . it says it kicked such and such just doesnt get him out . a few times this has happened and i used his @ and list and typed his name .

didnt see anything on that question either.
many thanks

[Cheekymonkey]

yeah I was on a server today where the admin warned someone for being idle...  the third warning sayed he was going to be kicked.. all the way up to the 6th..     neither kicked him.. 

[xlr8or]

@tynman: In b3/conf/plugin_admin.xml is a section:

Code:

<settings name="warn_reasons">
<set name="generic">1h, ^7</set>
<set name="default">1h, ^7behave yourself</set>

The 1h stands for 1 hour, that's how long the warning will be alive.

it's all here: http://www.bigbrotherbot.com/b3.html#warnings

[flinkaflenkaflrsk]

yeah I was on a server today where the admin warned someone for being idle...  the third warning sayed he was going to be kicked.. all the way up to the 6th..     neither kicked him.. 

I did notice this behaviour on our server also. The bot warns for spectator mode and should kick after 3 times but it doesnt for some reason.
eventually did a manual !kick but i still wanted to look into this. Maybe someone else also had this problem?

[xlr8or]

Okay, this probably needs to be added to the documentation for poweradminurt. Here's the deal.

PoweradminUrt makes use of the warn_reason 'spectator' that is configured in the plugin_admin.xml
By default the warning is set to expire in 5 minutes. If you do a quick calculation how the default poweradmin settings for the specchecker work you can see that the first warning issued is already expired at the time the third warning is being issued... Hence it will never reach the 3 active warnings for 'spectator' to have a legit kick...

Here's what I suggest you do to make the warnings stick longer. Open b3/conf/plugin_admin.xml and look for the next line:

<set name="spectator">5m, ^7spectator too long on full server</set>

Change it to:
<set name="spectator">1h, ^7spectator too long on full server</set>

That will make the specchecker work... I'll add it to the documentation of the latest poweradminurt version soon.

[flinkaflenkaflrsk]

aaah that explains it!

I remember it did work when we entered 1 customer warning and then the bot added another 2

thanks