[senseit]

Originally Posted by rautamiekka Would be good if I could ban according to the ID instead of the UserID or name of a connected Player; had to manually insert the ban into db.

Using the most recent version you should be able to ban using any type. It's now using OnClientBan, so even sm_ban, etc will appear. Make sure your plugin is up to date.

In regards to the database, you are correct there is room for some optimization there in the SQL. I'll change that on the next update if there will be one.

[khh0315]

i want to add sm_addban.

[Jim E. Rustler]

Originally Posted by senseit next update if there will be one.

Damn, sounds like there will be very few if any updates to this in the future. I had such high hopes for it too. Back to SourceBans for me then.

[StrikerMan780]

If you could, can you please make this compatible with existing MySQL Bans tables? Make the table be named mysql_bans, rather than my_bans. Also, Even if you don't use the IP Field, could you at least have it there for compatibility sake, so I can manage the bans via SourceMod WebAdmin?

[lyric]

hi, we use this. but when we ban someone the player name is never stored in the database? is there a reason that the player_name column exists in the database if the players name is never stored in it? all other information stores fine.
thank you

[lyric]

player_name isn't even stored why is that? also, it looks like the banned_by, ban_reason are suspect to sql injections which is a security issue, why is this even allowed here?

this plugin is dangerous for anyone to use, i would stay far away from it unless these issues are fixed though the author stated he doesn't care to fix the issues. can this be put in trash since it's got a sql injection problem and author don't care?

[Nikey646]

Originally Posted by lyric player_name isn't even stored why is that? also, it looks like the banned_by, ban_reason are suspect to sql injections which is a security issue, why is this even allowed here? this plugin is dangerous for anyone to use, i would stay far away from it unless these issues are fixed though the author stated he doesn't care to fix the issues. can this be put in trash since it's got a sql injection problem and author don't care?

Both ban by and reason are controlled by admins, why would you give an untrustful person admin in the first place, and what are the chances that an admin will ban for " '*Sql Delete All* " or be named that....

As for your previous post, the reason the player name isn't stored is because it gives the public a SQL Injection chance....

[ES3TH]

Hi, can you add the possibility to write bans into a sqlite database? I used STB2 to store temporary bans into a sqlite db. I modified it, so it can save permanent bans too, not only those up to one year as it was provided by author, but that plugin doesn't write admin, banned player name and reason of ban as your plugin which writes bans into a mysql db.

[eric0279]

with the help of google, I modified a little by adding multi language :

https://github.com/Owned67/MySQL_Ban

Demo :
http://blablabla.olympe.in/bans.php


If people want to improve or modify it ... join me on GitHub

There are just these two codes are not translate with no knowledge :

PHP Code:

if($currentPage>1){
                                echo '<a href="',$pageUrl,($currentPage-1),'">Previous</a>&nbsp;';
                            }
                            $totalPages = ceil($pageResults/$config['perpage']);
                            for($i=1;$i<=$totalPages;++$i){
                                echo '<a href="',$pageUrl,$i,'">',$i,'</a>&nbsp;';
                            }
                            if($currentPage<$totalPages){
                                echo '<a href="',$pageUrl,($currentPage+1),'">Next</a>&nbsp;'; 


[eric0279]

banned_by result hostname :s

How to modifiy for admin user ?