Results 1 to 6 of 6

Thread: Zynga poker: Dealer rotation policy?

  1. #1
    Join Date
    Apr 2004
    Posts
    65

    Zynga poker: Dealer rotation policy?

    I assumed that after every hand the player to the left of the dealer would deal the next hand. That’s doesn't seem to happen all the time. If one of the player's who put up the small or big blind go all in and lose, then the dealer doesn't rotate. Has anyone else noticed this? Or is it just me in this case. Because if anyone would have noticed the same issue earlier then I would have found many cases discussed on the same. So please help me in this case and let me know the proper scenario in this case.

  2. #2
    Join Date
    Mar 2010
    Posts
    303

    Re: Zynga poker: Dealer rotation policy?

    It is a poorly coded dealer routine IMO the dealer button moves one place to the left and pushes the SB and BB around too, if players leave the table or go bust then it is possible to be BB or SB numerous times in a row. My record is 2 BB then 4 SB then dealer then SB again. It should be the BB that moves one place to the left and drags the SB and dealer with it, and you should never be the SB or the BB more than once in an orbit.

  3. #3
    Join Date
    Mar 2010
    Posts
    338

    Re: Zynga poker: Dealer rotation policy?

    I asked myself that too. Numerous times I sit at the table and then players stand up and I have to pay like 3 big and small blinds! That’s not fair. And by the way I was always asking myself why the hell do we need to pay bb when we sit at the table. The blind that you pay when you first sit is called a Post Blind. This is to avoid people standing up when the BB is near. Zynga should eliminate Post blind when you have already paid once.

  4. #4
    Join Date
    Nov 2009
    Posts
    3,331

    Re: Zynga poker: Dealer rotation policy?

    There was a huge problem with blind dodging last year. Zynga introduced the 'BB to sit down' fee to discourage it and it does the job well. It is only 1 percent of your stack when you join a table. If you say so, but there are many other problems they could look at. Post blind is just ridiculous because I pay that and the BB is all over on me again because people stand up all the time. Just think it’s not fair.

  5. #5
    Join Date
    Feb 2011
    Posts
    142

    Re: Zynga poker: Dealer rotation policy?

    The way the button moves around is based on the big blind. The big blind always advances to the next player clockwise. Then the small blind is the player to the right of the big blind and the button is the player to the right of the small blind. I'm not exactly sure what this is called, but it is definitely not the dead button rule. The problem with the Facebook Poker button rule is that if the player who is the big blind keeps getting knocked out in consecutive hands, the small blind player gets hit with the small blind in multiple hands.

  6. #6
    Join Date
    Mar 2010
    Posts
    1,998

    Re: Zynga poker: Dealer rotation policy?

    The Facebook poker button rule is actually unfair to the small blind as he may have to post multiple small blinds in consecutive hands. With the dead button rule, if the BB is eliminated, the player to the left of that player should be the BB, and there should be no SB. This way, no player gets hit with multiple big blinds or small blinds. This is generally how we play in our home games. I would have like FB poker to use the dead button rule.

Similar Threads

  1. Replies: 2
    Last Post: 28-08-2011, 11:12 PM
  2. Replies: 5
    Last Post: 31-05-2011, 10:10 PM
  3. Zynga Poker : All poker buddies are missing
    By Elettra in forum Video Games
    Replies: 3
    Last Post: 29-05-2011, 05:43 PM
  4. Texas Hold-em Poker Shoutouts in Zynga poker
    By Dwayne Johnson in forum Video Games
    Replies: 3
    Last Post: 05-03-2011, 05:30 AM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,714,274,420.60609 seconds with 17 queries