Warning: is_writable() [function.is-writable]: open_basedir restriction in effect. File(/tmp_r) is not within the allowed path(s): (/membri:/membri2) in /membri/x2s2hx/bugtracker/includes/class.flyspray.php on line 997
FS#96 : Ban per nick

2Steps2Hell's -BanBot-

A low resource c++ urban terror bot that keeps track of players on specified servers and applies bans keeping the servers hacker clean :)
Tasklist

FS#96 - Ban per nick

Attached to Project: 2Steps2Hell's -BanBot-
Opened by Simone (Zamy) - Friday, 05 August 2011, 14:13 GMT+2
Last edited by n3m3s1s (n3m3s1s) - Friday, 21 October 2011, 15:49 GMT+2
Task Type Bug Report
Category Backend / Core
Status Closed
Assigned To Simone (Zamy)
Operating System Linux
Severity Medium
Priority Normal
Reported Version ver 1,2b1
Due in Version 1.2
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Attualmente, col ban per nick banna anche gli admin.
Da riflettere se fare solo per gli admin un controllo, o una cosa un pelino più sofisticata.
This task depends upon

Closed by  n3m3s1s (n3m3s1s)
Friday, 21 October 2011, 15:49 GMT+2
Reason for closing:  Fixed
Additional comments about closing:  https://gitorious.org/urtbanbot/banbot/c ommit/dd06f2b18875ea6b2671c88277157d1d38 c498f4
Comment by n3m3s1s (n3m3s1s) - Friday, 09 September 2011, 14:02 GMT+2
Che controllo sofisticato c'è da fare? semplicemente controlli la guid del player con il nick dato. Se è admin non lo banni. Semplice.
Comment by Simone (Zamy) - Friday, 09 September 2011, 20:15 GMT+2
Il discorso per cui il raccio è stato bannato, era per un 'aggiornamento' dati di un ban. In questo caso, di uno appena bannato col suo stesso nick.
Per questo stavo pensando a come implementare la cosa.
Comment by n3m3s1s (n3m3s1s) - Thursday, 20 October 2011, 16:50 GMT+2
nick bannato in db ed entra un'admin

Loading...