[Ganchrow]

I'm sure I'm not the only who finds the whole auto-logout thing at Bookmaker, CRIS, et. al. rather annoying. This is especially true with Bookmaker/CRIS because the software's login process is so time-consuming.

For a while I was just using an auto-refresh, but that was kind of annoying as it would flash the page, often refresh at an inopportune time, and I'd always need to remember to reset it when I changed pages.

Well I played around with it all for a bit and I think I came up with a pretty good solution for FireFox users.

To install, you'll need the the FireFox add-in GreaseMonkey. If you already have GreaseMonkey you can install the Stay Logged-In Script by clicking here (For new beta version that should work with nearly all books click here.)

If you don't already have GreaseMonkey visit the FireFox GreaseMonkey page, install the add-in by clicking the "Install Now" button, then restart Firefox and install from the above link.

(If you want to uninstall, go to Tools/Manage User Scripts, select "Stay Logged-In", and click Uninstall.)

If you care how it works:

The script is really quite simple.

It works by sending making xmlhttpRequest every 5 minutes (to change the refresh time just modify the lRefreshInterval variable, specified in milliseconds) to the main wagering page (wagering2.aspx). This is done behind the scenes with the response summary sent to the Firefox error console ("under Messages") with the response itself is discarded. CRIS & co. treat this request as activity on the player's part and thereby keeping the session alive.

It's still a bit syntactically messy but it does do the trick. I haven't played around with with it but in order to conserve bandwidth perhaps a page smaller than wagerisng2.aspx might be better suited to the task.

By design it won't send the request if you're on the main portal page (meaning you're not logged in), if you're viewing the wagering iframe in its own window (which unless you're hacking around you almost certainly are not), or if you're in the process of logging in or out.

It's currently set up to work with the following sportsbook domains:

betcris.com
bookmaker.com
2betdsi.com
betdsi.com
betmaker.com
yabet.com
optionsports.com
betonfighting.com
4galaxysports.com
sport-bet.net

Modifying the script to work with other domains attached to sportsbooks using CRIS software is trivial (it would just be a matter of going to Tools/Manage User Scripts and adding the desired domain).

Modifying it to work with a different sportsbook (or any other size which automatically logs you out after a period of inactivity) should in most cases probably be fairly easy as well.

If anyone has any suggestions on how to improve this, please post them here.

[RickySteve]

Very useful. This tool should make Mudcat deliriously happy.

Is this something CRIS might frown upon?

[Bill Dozer]

I'm not sure how it looks to them but if player usage time goes up they may look to see why. I wouldn't be surprised if CRIS asks you not to use it the way Pinnacle asks people not to scrape their lines.

It sounds harmless otherwise... but using stuff like this always seemed like a good way to get profiled.

[RickySteve]

I'm already profiled. I just wouldn't want to get profiled out the door.

[Ganchrow]

To CRIS it just looks identical to a normal Firefox refresh.

It's only once happening every 5 minutes and it's not like it's requesting any lines or anything. It's basucally just keeping the connection alive by making a simple request.

[2Pac]

This could be a reason for them to not pay your winnings!

[RickySteve]

Originally Posted by 2Pac

This could be a reason for them to not pay your winnings!

Let's not get hysterical.

[Ganchrow]

Originally Posted by 2Pac

This could be a reason for them to not pay your winnings!

From CRIS's perspective this is no different from manually refreshing every few minutes.

[Scorpion]

I tried it. didnt work
why are you excluding wagering.aspx?

[Ganchrow]

Originally Posted by Scorpion

I tried it. didnt work
why are you excluding wagering.aspx?

It's not. It's excluding wagering2.aspx.

wagering2.aspx is the page loaded by AJAX. Under normal usage it would only appear in an IFRAME. If I didn't exclude it would just wind up creating an additional AJAX request.

What address are you using? Is it one of the one listed above?

If you go to Tools=>Error Console in FireFox and click the "Messages" button you'll see some script output. Try clearing that and refreshing CRIS/Bookmaker and seeing what it says.

If it's still logging you out it's possible that for whatever reason your auto-logout period is shorter than 5 minutes. Try changing it to 3 to 4 minutes.

[Scorpion]

it works
thanks

i think after adding a book, i probably didnt refresh

how about books like abc islands that use a different software?

[jjgold]

Using these auto refresh utilities at sportsbook slows up the betting pages for other players trying to make plays.

[bigboydan]

Originally Posted by Scorpion

how about books like abc islands that use a different software?

Good question Scorpion. I would like to know the answer to that one myself.

[Ganchrow]

Originally Posted by jjgold

Using these auto refresh utilities at sportsbook slows up the betting pages for other players trying to make plays.

This places considerably less load on a server than a full-page auto-refresh. This script is only requesting the text of a very small page (so no images, for example, are loaded).

EDIT: I just made a change to the script so that instead of it requesting the entire page it's only requesting the page header, which contains less than 300 bytes of data.