More Betting Exchange Questions

[SneakyDave]

I created an open bet for something, a member accepted accepted the open bet, and he said that he got this error message:
http://i.imgur.com/PwW4djn.png

He thought maybe it was permission based?

Also, the same bet that he accepted, I don't know how to "settle" it, now that he's "won" it. Do I just transfer the wager to him, or is there a sportsbookER mechanism to actually settle it.

The bet itself:
GTB Restore | BASH.zone

 

[SneakyDave]

And one other thing to throw into the lawsuit.

It seems comments added to the betting exchange bets don't have their own permission. Although members can view the bet and the comments, it looks like guests can only view the bet.

 

[Bob]

I created an open bet for something, a member accepted accepted the open bet, and he said that he got this error message:
http://i.imgur.com/PwW4djn.png

He thought maybe it was permission based?

There isn't anything in the Accept action that would produce a redirect to another action in another controller (it just does a DataWriter action and redirects to the Bet. That looks like someone manually tried to create a bet with the wrong URL params (using the wrong URL, you can do that with ANY controller for core XF, or any addon). I'd really need to see the Server Logs to see the exact URL that was submitted to the system. If you can provide that (send an inbox) that would be perfect

I don't know how to "settle" it, now that he's "won" it

There are 2 ways that a bet can be settled.

Way 1. Self Settlement. This involves both the Bet Owner and Bet Challenger. When the Bet is in an "Awaiting" state and the Bet Owner & Challenger have the permission to "Settle Bet by self", they will see a "Settle" button. This allows them to submit their settlement choice. They pick either the Owner to win, the challenger to win or Push (in case of a tie). They have a text input box to explain their reasoning for their choice. Once both the Owner and Challenger have Self Settled, the system will check them both and if they are the SAME, then the system settles it based on that decision. If there is a MISMATCH, then it is up to a BOOKIE (with the permission to settle any bets). The BOOKIE can not be involved in the bet (can't be either the owner or challenger). They will see a settle button and will see the same input form with the choices and text box. When they submit it, its FINAL. A Bookie can perform a FINAL settlement at any point in the process.

Way 2. Bookie Settlement. A Bookie with permissions to settle ANY bet as long as they are not PART of the bet (Owner or Challenger). Even if the owner or challenger started the self settlement process, a Bookie and come in and just FINALIZE the bet settlement.

It seems comments added to the betting exchange bets don't have their own permission.

Yes, this is done on purpose. A comment is content agnostic (it can belong to an Event or a Bet). Viewing a Comment requires 2 permissions. view Comments and view Betting Exchange or view Comments and view Sportsbook.

Here is a bet with comments: Penguins vs. Lightning as a guest, I can view all comments and comment reply's.

 

[SneakyDave]

Well I'm confused. I have a bet in accepted status. How do I get it to awaiting status to settle it? There isn't a close date or status change possible when editing it.

I then tried to see something in the bookie cp, but I only see the traditional sportsbook options and events there, the bookie cp doesn't list any betting exchange bets or info.

I've made sure my account has the bookie and moderator permissions set to 'allow'

 

[SneakyDave]

Ok. I guess my problem is that the bet has a close date that I didn't notice before, and it's still in the future. I can't edit the close date on it, so I have to wait until that date passes to settle it.

And then I assume that I can't settle it as a bookie because I'm 'part of' the bet

 

[Bob]

Well I'm confused. I have a bet in accepted status. How do I get it to awaiting status to settle it? There isn't a close date or status change possible when editing it.

Accepted Status turns into AWAITING on the CLOSE DATE of the bet. You have a bet that has a close date of 2017. Its probably best to just DELETE that one and start a new one by using the CLOSE DATE as it is supposed to be used (set it to the start date/time of the specific event that will determine the outcome). You can't CHANGE the close date right now(you need to be careful when creating).

I then tried to see something in the bookie cp, but I only see the traditional sportsbook options and events there, the bookie cp doesn't list any betting exchange bets or info.

The Bookie CP is part of Sportsbook, not the Betting Exchange.

The Next Release will have the ability to change the CLOSE DATE.

 

[Bob]

then I assume that I can't settle it as a bookie because I'm 'part of' the bet

Ya, only a bookie that isn't involved in the bet can settle as a bookie. Just create a fake account, give it betting exchange bookie permissions. That's what I do.

 

[SneakyDave]

So, now that I can edit an event's close date, that's great. But the only problem is that when the close date is selected, it still has to be in "the future".

On some bets I create as bookie, I have the close date set to a far enough date in the future, and then want to close the bet when the outcome is "obvious" to both parties, and then settle it with both parties. Currently, I can set the update the close date, but it still has to be in the future, so I have to set it to about a minute or so in the future, then come back to the bet in order to settle it.

 

[Bob]

But the only problem is that when the close date is selected, it still has to be in "the future".

Yes, by ONE MINUTE (which the TIME picker allows the settings by minute increments).

This has already changed in the next maintenance release (I even mentioned in our convo what was coming) lol

 

[SneakyDave]

I must have missed that, thanks for the quick reply bobster.

 

[Bob]

I'll try and push out a release this week. Busy week at the hospital for me tho, so no guarantees.