vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vBulletin 3.0 Full Releases (https://vborg.vbsupport.ru/forumdisplay.php?f=33)
-   -   vBookie - vBulletin Betting Hack (https://vborg.vbsupport.ru/showthread.php?t=65844)

twoseven 09-04-2004 12:17 AM

Quote:

Originally Posted by KevinSHOCK
can someone please answer my problem i posted, the vbookie cant be used correctly until this is fixed

kevin i had that problem as well. there are 2 database entries for different points and ucash is pointed at one and vbookie is pointed at the other. i just copied one to the other and it was fixed

KevinSHOCK 09-04-2004 02:35 AM

Quote:

Originally Posted by twoseven
kevin i had that problem as well. there are 2 database entries for different points and ucash is pointed at one and vbookie is pointed at the other. i just copied one to the other and it was fixed

can you explain which ones if its not a problem? im really rusty at coding and working through the database, well i mean i havent forgotten but like yeah...im kinda lost :( can i fix this problem with running a query?

Taco John 09-07-2004 05:49 AM

I've got a pretty important question that I haven't seen addressed...

Does this software account for bets that go push?

RMS-Chef 09-07-2004 10:11 AM

Quote:

Originally Posted by Taco John
I've got a pretty important question that I haven't seen addressed...

Does this software account for bets that go push?

Event's can be "Abandoned" and all bets are returned to the users if that's what you mean.

Taco John 09-07-2004 02:58 PM

I don't want the whole event abandoned... I just want certain outcomes that "push" abandoned. A "push" is a common outcome on many wagers...

Ugh. This thing is going to explode in my face if I can't refund stakes on outcomes that push.

VodkaFish 09-07-2004 05:31 PM

Quote:

Originally Posted by Taco John
I don't want the whole event abandoned... I just want certain outcomes that "push" abandoned. A "push" is a common outcome on many wagers...

Ugh. This thing is going to explode in my face if I can't refund stakes on outcomes that push.

The only way to do something like that with the current system would be to separate any events that can be pushed into their own event, and then abandon it if they push.

Taco John 09-07-2004 05:55 PM

Ugh. I was afraid you would say that.

I don't mean to be negative, but this hack doesn't make sense without a feature that allows an outcome to be a push. I'm using this for a sports forum, and in sports there are often outcomes that go "push" while there is still action that nets wins and losses. This is very common in sports, especially NFL.

There really should be an option for an outcome to go "push" that doesn't wreck the action on all the other bets.

There's no way I can manage all these games if i'm having to have three seperate threads to bet one game...

To see how I am using this in an NFL format, please view this thread:
http://www.orangemane.com/BB/showthread.php?t=16833

It's all together, and consice. Everybody can see how each game is being bet.

"Push" is a standard in gambling. If this hack is going to be used in football forums, "push" outcomes are important to have without having to mess up the other action... and without having to have a dozen different threads to bet a single game. There's only one bet in standard football betting that doesn't go push...

Unfortunately, my users have got action placed already and the NFL season starts this week.

Taco John 09-07-2004 06:17 PM

Also, for reference, there are 16 games a week in the NFL, with three standard bets...

1. MoneyLine
2. Over/Under
3. Point Spread

To seperate those into three seperate threads per single game is the difference between managing 16 threads a week (opening and closing) and almost 50 threads each week. That's about a hundred threads each week for NFL forum admins to manage when you figure that you've got to close last week's results, and then you've got to open next week's action. That's a huge time investment.

I love the hack, but a "push" outcome is incredibly important.

VodkaFish 09-08-2004 12:01 AM

I'm sure you thought about this already - but for the meantime you can use half values for spreads and over/unders.

Taco John 09-08-2004 01:08 AM

Yeah, I thought about that for next week... But for this week, It's difficult to do that without causing a board riot since bets have already been placed.

Hopefully, for the future, a column next to the "pay out" column can be added for pushes.


All times are GMT. The time now is 11:59 AM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.01473 seconds
  • Memory Usage 1,745KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (4)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (4)pagenav_pagelink
  • (2)pagenav_pagelinkrel
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (10)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • pagenav_page
  • pagenav_complete
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete