Effective Immediately, this user is on a 72 hour ban watch.
__Tigarius__ was Tigarius@user-95.bbd07tcl.dsl.pol.co.uk * Tigarius
Make sure that the user is actually Tigarius prior to placing the kill (set an exact gline on the full hostmask to assure that it does not affect anyone else, like Andrew who shares his ISP).
This user is on ban for posting death messages in his quit message regarding another user while still on our network. As you know, these messages are displayed to all users in all rooms matching where tig was... and this is not the type of atmosphere we can have on the network.
Earlier yesterday, I had to ask him repeatedly, then /kill him, for flooding another user on the network to the point of near-disconnection by way of PING requests. Flooding, as you all know, is strictly forbidden in the network /rules, so he's run out of chances.
Not to mention when I asked him to drop it, he had the balls to tell me not to talk to him at all, because I "ignored him" while he was shunned. 😆
[ 09:57 ] : __Tigarius__[Tigarius@12Stones-PSO-Chat-47F2742.bbd07tcl.dsl.pol.co.uk] has quit .
Yes Sir! 😉
His actions were uncalled for yes, but i think it would be unfair on him, compared to the action of other people, including those of last nite.
Tig and Fook are allways arguing with each other, also Axel and Fook last nite. :no:
but usaully its a room issue. they were just room arguments.
when someone starts to ping flood someone / make death threats in quit msgs it becomes a server issue. i like tigarius but he gets out of hand when hes fustrated.