Thank you. I'm happy to hear that.
Quote:
1) When the ad came up I wasn't sure if I was being folded out of a dealt hand or not. Might want to throw up a message to let the user know the game is pausing for the add or something. Right now, when the ad starts, you hear a time-out beeping sound which I assume is for posting the blind but it gives the impression that I'm timing out on a decision.
You are *not* wrong in your assessment here. However, the placement of the ad and how it fits into the game is a very contentious topic within our company. There are several issues at play here. If we place the ad somewhere innocuous that doesn't get in the way, no one will see it. And the ad companies are pretty smart about detecting that. If we hold up the game and wait for players to watch ads, then, well, we hold up the game and that gets kind of annoying for the players.
Here're a few positives to consider. The current placement of ads (will eventually) yield a very high ad rate due to its placement and user attention. This means more revenue for players since we give half of it back to players. While ads can be pretty tough to sneak in playing heads up, they're a breeze to manage on a 4-handed or higher table. Fold preflop... watch ad. After playing a short time, it's very manageable. I already know how to sneak in ads on a heads up table so that it doesn't get in my way or cause noticeable delay for my opponent (hint:
don't do it between hands; start your ad immediately after clicking a pre-action, especially if you think your opponent is going to ponder a few more seconds). We are considering making ads optional on heads up tables. Also, ads become optional starting at level 10. I've played on level 10 for a few hours and I must say it's really slick being able to skip the ads. If I were 4 handed or more, I'd definitely watch them anyway.
While we know it's not 100% perfect, we're open to all forms of suggestions on how to make ads more manageable.
Quote:
2) You currently have the blinds being posted and then the dealer button moving. Clearly you want to move the button first before posting the blinds. I can imagine it would throw people off a lot especially if multi tabling.
When this was originally programmed, it threw me off a bit myself. But there's a programmatic reason for this. In a live game, [human] dealers tend to handle unexpected events quite well. Buttons move in concert with the shuffle, posting of the blinds, etc. Occasionally something will throw off this concert such as when the [presumed] big or small blind bids adieu to the table and the blinds adapt along with the button without much fuss.
However in the world of software, things aren't as forgiving. Since players at the same table are occasionally on the opposite side of the planet, we need to verify that they are taking the blinds before we know where the button goes. Technically speaking, the button isn't the leading indicator for the blinds. It's the big blind that moves around the table and the small blind and button follow in accordance with whoever ends up taking the big blind. While we auto post blinds, occasionally network delays make the button movement lag. Also, new players or players who have missed their blind will be offered an option to post, which also introduces substantial delay. Only once we figure out where the blinds are going can we know where the button will end up. That's why we do it this way. If it's any consolation, I happen to know at least one
extremely large site that does [or did] it the same way.
It does. Thank you.