vBookie - vBulletin Betting Hack

vBookie

Introduction

vBookie is a 'bookmakers' or betting extension to vBulletin. It enables authorised members to post Events and Outcomes that forum members can bet on. Each Outcome has its own set of odds, and odds can be modified through the life of an Event (bets that are placed are stored with the prevailing odds, so even if the odds change, your users are paid at the correct rate).

Once the results are known, Events can be settled and forums members awarded their winnings.

vBookie uses its own vCash by default, but this has no more use than as 'bragging rights'. However, vBookie also comes with a built-in switch to allow it to use either uCash or Petz money instead. That means that all bets are paid for and settled using uCash or Petz money, making betting even more attractive than just for fun on forums with uShop/Petz installed. Although vBookie does not have any built-in facility to integrate with any other store hacks, it's a very simple job to hack vBookie itself to integrate it with any store/points system you care to use.

Features

• master switch to turn vBookie off
• option to use uCash
• option to use Petz money
• settings to restrict the creation of Events to specific user groups
• settings to restrict which user groups can bet on Events
• settings to restrict which user groups can edit or settle other people's Events
• per-Event, specify whether punters may bet on more than one outcome
• optional 'charity mode' so that the poorest members of the forum always have something to play with
• supplied with a module for vBadvanced

Please click if you install this hack, thanks. Please also let me know - send me an email or a PM. If you'd let me know the forum URL too that'd be cool!

vBookie is free, and will remain free.

Updates

1.0.0 -> 1.0.1

- adds the ability to delete Events. See this post for upgrade instructions if you already have 1.0.0

1.0.1 -> 1.0.2

Corrected a minor bug with the charity mode when using uCash. See this post for manual upgrade instructions from 1.0.1.

1.0.2 -> 1.0.3

Corrected a minor bug with the richest people display when using uCash. Just overwrite includes/functions_vbookie.php with the one from the new Zip file.

1.0.3 -> 1.0.4

Corrected some date display problems when using "Detailed" dates. For manual update instructions, see this post.

Corrected Petz bug whereby all winnings were paid to the bet's owner rather than individual winners. To upgrade from 1.03 or earlier, see this post or overwrite includes/functions.vbookie.php with the 1.0.4 version.

Problems?

-> Petz - If you are using Petz there is a bug in all versions up to and inclusing 1.0.3. Your players won't get paid their winning, and all payouts will end up in the account of the person that posted the Event. To correct this, please see this post. This fix will be incororated into 1.0.4 onwards.

-> If you can't post Events, or can't bet on them make sure you have set your user permissions

-> If you have an SQL error Invalid SQL: UPDATE SET =25 WHERE <25 make sure you are using version 1.0.3 or later.

-> If you have any other general problems, please check the installation/hack instructions and make sure you have carried out all the steps and also check that you made the changes correctly

Anything else, ask in this thread.

Other Stuff

-> If you are using Detailed Date & Time display and have a problem with Event dates appearing as '1 Minute Ago', see this post.

-> If you want to use poster 'Reputation' as the currency for vBookie, see this post.

About Odds

Odds of "5/1" are "amount won per amount placed". This means that I would win 5 for every 1 placed. Of course, if I win, I get my stake back as well. Odds of "1/5" means that I win 1 for every 5 placed. I'd have to place 25 to win just 5.

Decimal Odds

Decimal odds are just another way of displaying the same information. 2.0 is the same as 2/1. 0.2 is the same as 1/5. vBookie only lets you specify odds in terms of x/y, but if you think in terms of decimal you can still work out what odds to provide. Simply think of your decimal odds as "2.0 / 1.0" or "0.5 / 1.0" and then multiply each side through by 10 or 100 until there are only zeros to the right of the decimal point, then just take the whole number part.

2.0 / 1.0 has no decimals, so this is the same as 2/1

0.5 / 1.0 has a 0.5, so multiply both parts by 10 to get 5.0 / 10.0. Then you can specify your odds as 5 / 10. You might also realise that this is the same as 1/2. The technique is a simple way to work out any odds you may need to specify.

Odds of 0.65 -> 0.65 / 1.0 -> 65.0 / 100.0 or 65/100. Then you can divide through by 5 to get to 13 / 20, although this step isn't necessary.


_______________________________________

[Andreas]

Use
[sql]
CREATE TABLE vbookie_groups (
group_id SMALLINT UNSIGNED AUTO_INCREMENT NOT NULL PRIMARY KEY,
group_title VARCHAR(255) NOT NULL)
[/sql]

[Steelersfan]

Thanks! Now I will go try the rest of the install.

[sharonkitty67]

I need someone to install this for me!! Gahhhhhhhhhhhhh! Im not that great at this sorta thing - I'll pay!

[MRGTB]

Does this work with vBulletin 3.0.8. I have installed it and took my time with all the file edits. The vBookie page is there and I'm getting no errors. Everything seems to have been installed just fine.

But when I go to post a new thread. The link is not there to post a vBookie bet with the thread.

I have checked usergroup permissions and enabled admin to post bets as well as members. And I have also enabled the betting system using it own betting type. But still no option is there in a new thread to attach a bet.

Can somebody advice and help me please with this.

PS: I also notice that somebody above said he got a MySQL error duting the installtion on 3.0.8. Well the install file went OK for me and I did'nt get any MySQL errors at all. :ermm:

[MRGTB]

My mistake, I didn't know after the vBadvanced bit there were also a couple of template edits also to be done also. It's working fine but I have question.

There is a section in the file edits were you are asked to open the file called init.php

and search for this:

'stylecache' 
        ), $specialtemplates);

and place with this:

'stylecache', 
            // +++ vBookie 
            'vbookiesettings' 
            // --- vBookie 
        ), $specialtemplates);

The problem is in vBulletin 3.0.8 the line you search for called.

'stylecache'

already had a comma after it like this:

'stylecache',

So what do I do with the placement code. Do I add a comma after the last line in the mod instead.

Should it look like this:

'stylecache', 
'vbookiesettings' 
        ), $specialtemplates);

or this: Seeing as the stylrcache line in vbulletin 3.0.8 already has a comma after it unlike the mod that asks you to search for it mwithout a comma which must have been a 3.0.0 thing that wasnt there in that version.

'stylecache', 
'vbookiesettings', 
        ), $specialtemplates);

[MustangLisa]

Looks good; I'm going to install. Thanks for all your work!!!

[atomic fireball]

Is there any easy tweak to this to have the user's cash amount show up when you click on their user info in member.php?

It would be nice to see how much they have under "Join Date: XX-XX-XXXX" to just say something like in the Postbit.

Any help for getting this tweak? Seems easy for your PHP experts which I am obviously not.

[djwins]

Originally Posted by Ock

I've discovered a huge flaw in the way vBookie events work that allow someone to vote on any events at odds of his own choosing.

The way to do this, which i discovered by chance, is trivial: make a copy of the form - and edit it to change the odds, which are written in the webpage and not checked after submission.

I thought you should know, because someone wanting to exploit it could do so incredibly easily.

Is there any thoughts as to how to fix this??? Much thanks.

Originally Posted by cashpath

Yes this flaw has already been pointed out the fix for it has already been pointed out also

Where is the fix?

[Andreas]

It's not fixed in the vBulletin 3.0 Version and the original author most likely won't update it anymore.
As this isn't a real security issue you might be out of luck if nobody else does a fix.

[Flow Fusion]

Help...