Screengrab says it all. I expect its because they're ITM but it should then close the reg period.
Unfortunately the "well known" bugs are still alive I have reported they though.
-Unloadable opponents/player cards when tourney starts (need closure and reopen table to solve it)
-fix limit holdem option in progress (you can't go allin)
-the ability to raise and have less than 1 chip (the best gift for bounty hunters)
-A client message starts with "message"(FE if you type a wrong password)
It seems until the next version of the client we shall deal with the current bugs.
I believe it's already in the backlog but have asked for it to be checked.
Hi @psrquack, we'll bring small improvements or small bug fixes on each release. It's not easy to prioritise them because we have more important issues but at the same time, as they're fairly quick to fix, we always pick some of them in order to find the right balance.
Regarding what you're mentioning:
@Chris-Unibet, I think he was referring to the bug where you couldn't raise all in pre-flop if you didn't have many chips and the bug where you would call all-in and be left with .xx of a chip.
They're both fixed in 2.0.7
I think that 2 things what you don't understand are already fixed. It was with a connection of the enabled play in chips mode where in some cases the allin button didn't work and when you had less then a BB you could check only. I think the 2.07 version is much better than the previous one. Btw if there is a resource it would be great if the number of the registered players could increase dinamically. (Means the lobby don't update the number of the registered players.)
Thanks and my bad, I didn't realise that your post was from a week ago.
it's not only wen players are ITM or on the bubble.
This happend to me again with the Saturday Stack €1 pre-qualifier.
Just for you information, we have two different issues there:
1. When registration closes earlier than expected (see 2. for the reasons), the client should stop implying that registration is open (Currently it says “Registration ends: hh:mm:ss”)
2. There are two reasons why late registration closes before the expected time. One is because players are already in the money and this reason is valid. One other is because the first player to be eliminated will cap the tournament.If e.g. 11 players join a tournament and 1 player busts, the tournament will be capped to 72 players because in tournaments of over 73 players, 11th place would be paid. That's a weird one but also a complicated one to change for some reasons. I won't elaborate into the different options we have we'll look into it at some point.
Issue 1 would be the bigger of the two for me IMO. If a reg closes for any reason that's fine enough but it should show in the client correctly that it has.
I can understand the capping thing, it's just something that's going to happen from time to time. Would it not be possible to manually set caps for MTTs that are consistent in registrants?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.