Miserable Users for vB3

Miserable Users for vB3
Version: 1.01
vB-version: 3.0.0
Developer: KuraFire (original for vB2: Zzed)
Install-difficulty: Easiest
File edits: 0
Template edits: 1 (phpinclude_start)

Description of the Hack:
The Miserable Users Hack for vB3 is an upgrade from Zzed's hack for vB2. The vB3 version is streamlined and works without any file edits. It is purely template based.


Templates modified for this Hack:
phpinclude_start

(the above was generated via the Hack Tracking Log, soon to come)


1.01 update: January 5th, 3:10 pm CET
Instead of a custom check for the usergroup data to see whether the user is a Miserable User, vB3's function is_member_of() is being used now, cleaning up the code even more.


Here's what the Hack does: (original Hack thread)
This Hack will allow you to drive away people from your board without banning them. As explained by Zzed, the author of the original (vB2) hack:

Originally Posted by Zzed

So here is what really happens to a miserable user:

- There is a random 60-120 second delay each time they click on a link.
- 90% of times they have no search engine acccess.
- 75% of the times they get the server too busy error.

If they don't get the server too busy error:
- 50% of the times they may get a blank page
- 30% of the times they may get forwarded to the forum main page
- 20% of the time they may be able to see the page they asked for.

This vB3 hack uses NO FILE EDITS. Instead, it's all template based and Usergroup-based, making it even easier for you to manage your Miserable Users.



TO INSTALL:

1)
Create a new membergroup, and name it Miserable Users. Give them no particular permissions if you want, as you can use it as a secondary group (so you can effectively give them 0 permissions whatsoever).
Note: make sure to note down the Membergroup id !

2)
Put this code at the top of your phpinclude_start template:
Note: fill in the membergroup id from step 1 where it says "$miserableid = 8;" (replace the 8 with your id number).

PHP Code:

// Miserable Hack for vB3
    // Ported by KuraFire to vB3, original vB2 version by Zzed
    // #######################################################
    // Put the id of your Miserable Usergroup here:
    $miserableid = 8;
   
 // Check to see if the user is a Miserable User
 if (is_member_of(array('userid'=>$bbuserinfo['userid'], 'usergroupid'=>$bbuserinfo['usergroupid'], 'membergroupids'=>$bbuserinfo['membergroupids']), $miserableid))
    {
        $glitch = rand(60, 120);
        for($x=0; $x<$glitch; $x++)
        {
            echo ' ';
            sleep(1);
        }
    
        $vboptions['floodchecktime'] *= 10;
        $glitch = rand(0, 100);
        if($glitch < 90)
        {
            $vboptions['enablesearches'] = 0;
        }
    
        $glitch = rand(0, 100);
       if ($glitch < 75)
       {
           eval('$headinclude = "' . fetch_template('headinclude') . '";');
           eval('$header = "' . fetch_template('header') . '";');
           eval('$footer = "' . fetch_template('footer') . '";');
           eval('$timezone = "' . fetch_template('timezone') . '";');
           eval('$gobutton = "' . fetch_template('gobutton') . '";');
           $vboptions['useforumjump'] = 0;
           eval(print_standard_error('error_toobusy'));
       }
   
        $glitch = rand(0, 100);
       if ($glitch < 80)
        {
            if ($glitch < 50)
            {
                exit;
            }
         $templatecache['headinclude'] = '<META HTTP-EQUIV=\"refresh\" CONTENT=\"5; URL=$vboptions[forumhome].php\" />' . $templatecache['headinclude'];
        }
    }
    unset($ids, $glitch, $miserableid, $x); 


Done!

Note: this Hack will come in an HTL* package once the HTL is finished.

Toning Down The Pain:

You'll find that this hack is a bit rough on people, and may be getting too obvious. If you want to tone it down, here's what you can do:

Toning down the page load delay:
This line:

PHP Code:

     $glitch = rand(60, 120); 


specifies the random delay, in actual seconds. You can see that Miserable users will have at least 60 and at most 120 seconds loading delay for pages. If you want to dial that down, you could change it to 30, 60 for instance. The first number is the minimum amount of seconds they'll wait, the second is the maximum. A random number in-between the two will be used for each page load.


Toning down the % chance disabling of the Search engine:
This line:

PHP Code:

     if($glitch < 90) 


specifies the chance of the search engine being disabled. Currently it will be a 90% chance. Change the number to (for instance) 50 for a 50% chance.


Toning down the chance of a Server Too Busy error:
This line:

PHP Code:

    if ($glitch < 75) 


specifies the chance of getting a Server Too Busy error. Lower the number for a smaller chance.


Toning down the chance of a blank page:
This line:

PHP Code:

        if ($glitch < 50) 


specifies the chance of getting a blank page. Lower the number for a smaller chance.


Increasing the chance of getting a normal page:
This line:

PHP Code:

    if ($glitch < 80) 


specifies the chance of not getting a normal page. So, if you want to increase the chance of getting a normal page, decrease this number!


Toning down the chance of a refresh to Forum home:
This section:

PHP Code:

    $glitch = rand(0, 100);
       if ($glitch < 80)
       {
           if ($glitch < 50) 


specifies the chance of getting a refresh. If the 20% chance of getting a normal page is not the case, there will be a 50% chance of a white page, and if that doesn't happen, there will be a refresh. If you want to change it, meddle with those two options to find a balance you like.





Hope you guys enjoy this update of the excellent hack by Zzed, with the improvements I've made to it for higher maintainability (and, no file edits ).

[corsacrazy]

why would you want to drive people away ?

[KuraFire]

Banning doesn't always help, people tend to evade the ban by signing up again and what not. Making it difficult for them to be on your site without them realizing that it's your doing will make them want to go because it's annoying for them to stay, whereas banning them over and over again makes it annoying for YOU if THEY stay.

[RixiuS]

Thanks, KF. Maybe I'll find use for this when my forums get more popular, as for now; there's been noone that naughty

[TheAnt]

oh yes, now the fun begins

*install

[MGM]

w00t! thanks man, my site wouldn't have been the same without this

[high]* MGM clicks Install
[/high]

MGM out

[KuraFire]

Glad you guys enjoy

And keep in mind - this is not so much my hack, more is it a port of Zzed's hack. He came up with the idea and the initial code, I've only ported it and made it a little better.
(this to ensure people don't go blaming me for trying to steal someone else's hack)

[dynamite]

You know... I never thought I would use this, but I had 14 people sign up yesterday and posted a bunch of crap on my site. I have wasted my valuable time having to delete all their posts. Should I send them a little email that says "Welcome to hell"? Maybe that will encourage them to come back to the site !!!

[KuraFire]

Just make sure to be careful, you don't want those members to figure out that they are placed in a Miserable Users group!

[Gary King]

Does this count as a hack though, because there are no code changes as it states in the rules..?

EDIT: Sorry about that, my mistake there is a forum for phpinclude hacks actually

[KuraFire]

yeah, I put it in here though because the original hack was a file edit hack and that one was placed in this Category of hacks, so for the sake of people familiar with the vB2 hack, I've placed it here instead of in Mini-mods.

[buro9]

It's good in here... I found it because it was in here... and I've used the original hack... far more effective than banning... as they're able to log off and register a new user and IP banning is a heavy handed tool when you have proxies involved.

The only thing I'd like to see is a small addition... Add a permanent cookie to the client of a banned user so that if they manage to log out they are still in hell. Of course... this would need a lookup to confirm that the user is still 'miserable', but if they cookie contained the userId of the user that was miserable... and then you could check the database to see if they're still miserable and only clear that cookie if the user associated with the cookie has changed status.

The problem I saw is that I know of two users who live together... one of whom might soon earn miserable status... but the other user would not, and thus they would see swiftly that the user had been tampered with... so the above would just render that browser useless until they manually cleared all cookies.

Finally... it would be lovely to see one more minor adjustment... to make the 'tone down' stuff an option... so you'll have the ability to make someone 'slightly miserable' and 'very miserable'

[KuraFire]

I've considered using $vboptions for the percentage/chance checks, so that you could tone it down via options, but decided against it for now, only because that makes the Installation of this hack a LOT more 'complicated'. Mainly because the Hack Tracking Log is not done yet, so once it is I'll release a HTL-installer that comes with $vboptions for the toning down.


As for a cookie and all that stuff - I'll think about it. It seems like a good idea, but I'm not sure how hard to implement it is.. I don't want to make this Hack complicated as it's such a simple thing, and should remain a simple thing. I hate unnecessary file edits. ^_^

[Gary King]

Originally Posted by KuraFire

yeah, I put it in here though because the original hack was a file edit hack and that one was placed in this Category of hacks, so for the sake of people familiar with the vB2 hack, I've placed it here instead of in Mini-mods.

Yep that's true

[SloppyGoat]

OMG!!! This is wonderful!!! I will definitely be installing this one!!! Thank you sooo much!!! LOL