![]() |
UPDATED!!! AGAIN!
This is a more effective solution than the standard "ban", and is meant to be used for very annoying troublemakers that keeps re-registering once banned. Anyway - once a user is placed under the "Hellban", the following happens: 1. Every 3:d time the user tries to load a page, he is greeted with a fake "500 Internal Server Error" message. 2. Nobody but moderators and the user himself can see his posts. He is, essentially, under a site-wide ignore. This may not be a 100% fail-safe solution, but a lot of the morons will hopefully get tired and go away. Here is how it's done: 1. Run the following query on your database: INSERT INTO usergroup VALUES("666","Hellban","","0","1","1","1","1","0", "1","0","0","0","1","1","1","1","0","0","1","1","1 ","0","0","1","0","0","0","0","0","0","0","0","1") ; ALTER TABLE post ADD hellban INT UNSIGNED; ALTER TABLE thread ADD hellban INT UNSIGNED; 2. Add this at the bottom of you global.php PHP Code:
PHP Code:
PHP Code:
PHP Code:
PHP Code:
PHP Code:
PHP Code:
PHP Code:
PHP Code:
PHP Code:
PHP Code:
PHP Code:
PHP Code:
|
Interesting.... Might check it out sometime....
|
nice thanx
|
I may install this for those users that keep registering multiple names even though they were asked nicely not to register more than once :D - That will teach them to listen ;)
SaintDog |
Just to be clear, this hack basically puts a certain username in torture mode. Instead of banning him, you let him in and toy with him. But what's to prevent the user from re-registering yet again and escaping the hellban? Or does this hack somehow detect that?
|
Quote:
There is nothing to prevent the user from re-registering, and I don't think there ever will be, as the use can just delete the vbulletin cookie, EXCEPT for the fact that he might not be aware of hellban, unlike the standard ban. This hack is meant to be silent (i.e. the banned used is unaware of it), and only meant for extreme troublemakers. It's meant to make terrorizing the forums a much less pleasureable experience (i.e. annoying error messages and no responses to his flamebaits). Some may discover that they are being fooled, but some (hopefully) will simply be bored and walk away. |
I like this, except for the JOIN on the table that it adds with every showthread. Maybe a more efficient solution would be to modify newreply and newthread so that whenever a 666-user posts, it is automatically made visible=0? Or would that put it in the moderation queue...
Have you run this on a sizeable board and is there much of a hit with the join? |
Quote:
The solution would be to add a "hellban" column to the post table... I'll see what I can do. |
Joins are heavy on the database when they are done on large tables... post and user are 2 of the biggest tables in vB, so it should make things slower.
Adding a hellban flag to the post table would be ok, but bear in mind that even if you take a user out of that usergroup his older posts will still remain hidden. |
Quote:
Oh yes - I guess that makes sense. And so I have learned another thing! :pleased: As for the remain-hidden issue, the only solution I can think of is to add a little admin interface for it, but it seems overkill, as this is pretty much a last-resort-ban. |
Updated with modifications!
[edit] Also, dear admins of this board - you might like to modify the PHP-code template so that the tables are left-aligned and dont look like **** ;) |
I got this error when I tried to run the query.
SQL-query: INSERT INTO usergroup VALUES(\"666\",\"Hellban\",\"\",\"0\",\"1\",\"1\", \"1\",\"1\",\"0\",\"1\",\"0\", \"0\",\"0\",\"1\",\"1\",\"1\",\"1\",\"0\",\"0\",\" 1\",\"1\",\"1\",\"0\",\"0\",\" 1\",\"0\",\"0\",\"0\",\"0\",\"0\",\"0\",\"0\",\"0\ ",\"1\"); ALTER TABLE post ADD hellban INT UNSIGNED; ALTER TABLE thread ADD hellban INT UNSIGNED; MySQL said: Column count doesn't match value count at row 1 |
me too, rick.
|
Quote:
Just create a new usergroup, and then go into phpmyadmin and change the groupid to 666. |
Quote:
|
Quote:
Code:
INSERT INTO usergroup VALUES("666","Ultimate ban","","0","1","1","1","1","0","1","0","0","0","1","1","1","1","0","0","1","1","1","0","0","1","0","0","0","0","0","0","0","0","1"); |
its funny, mine just worked now without me doing anything. well, thanks for the help
|
Still no good for me :-(
|
i got the query to work, but the hack itself wont work for some reason
|
props to you. nice hack.
|
I did a quick & dirty hack that has much of the same effect but without the query JOIN -- (removes a person's posts but lets them see 'em normally so they don't know what happened)...
https://vborg.vbsupport.ru/showthrea...threadid=35589 |
JOINS are only a problem if the field(s) you are joining are not-indexed.
|
Freddie, you so smart... and it appears usergroupid is already indexed. So his original showthread join with the user would not have been a problem eh? Sorry intellected! I see you already changed it to use a new field, post.hellban. If the original way really didn't add much overhead, it was probably the more elegant solution rather than adding a new field to post.
|
I don't know, I didn't look at his code so I have no comment on it's effectiveness at utilizing the database.
|
I think the usergroup is already read at showpost / newreply / newthread time.
So there is that info at postbit level, and we can use it without adding the hellban field to post & thread tables. What do you think about ? Thnx |
Same thing.....same error....can't get the query to work....help plz?
|
I like hellban idea, but there is another way.
If you created 666 usergroup you find in admin/ functions.php PHP Code:
PHP Code:
Or change postbit_ignore template for more suited. |
Quote:
|
n/m, got it to work in phpmyadmin
|
i found a better method if you got admins out there that like members you ban. simalar to the one above but im using it and it works
in functions.php find PHP Code:
PHP Code:
then deleate everything from postbit_ignore |
I loved the 505 error bit, so I only took that bit from this hack, and removed the random number generator so that it happens everytime, and the person is effectively locked out of the board for good. (unless they clear their cookies - but most probably won't even know whats going on).
|
When i tested this on my forum on my machine, after editing the showthread.php i couldnt see the thread at all. every thread was blacked out. i dunno what the problem is
|
Ok, I tried to install this (on 2.2.6), but at the showthread.php part, after I saved the file, no posts where visible....
|
BUMP
|
Major bump
|
Ultra bump
|
Is this thing going to make it to a final? Sounds like an interesting hack.
|
hi
i have this proplem: Parse error: parse error, unexpected ')' in /home/forumcom/public_html/newthread.php on line 228 here is line 228: PHP Code:
|
Can this hack be used for vB3.0.3?
|
Search for the miserable users modification which is available for version 3.0.x and 3.5.x which does the same thing.
|
All times are GMT. The time now is 04:44 PM. |
Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|