Quote from: ajaxmoor on February 16, 2017, 01:24:53 AM

Quote from: SwC_Poker on February 15, 2017, 09:21:09 PM

Quote from: darkmule on February 15, 2017, 08:20:24 AM

I second the general concept and HTML5 in particular seems the best option.

We have heard the community loud and clear on this matter. It has been added to the development path.

And still you have it 4th on the list ? Don't you guys realize you can knock the rest off the list if you were to give it a higher priority ?

There is much work to do, and it was difficult to decide the exact order. The precise ordering of client development was based on available resources and partial client code. We feel that most players prefer to play on a client so they can arrange multiple tables on the desktop, however we understand the desire for browser based play.

Quote from: scottyno on February 16, 2017, 05:14:52 AM

I can't believe people are willing to pony up $200+ for a tournament where you never know when your cards will just vanish or the site will super lag and you'll never even get a chance to act. It was fun enough in a 5 chip mix game tourney where you're pretty short stacked to see AAKK in plo, and then the site lags and you watch your hand get folded before your buttons even ever showed up to act, I can't imagine how much more brutal it would be in a 250.

I love the lowball and mix game tourneys even at low stakes, and am a fan of the new schedule bc I'd play those games for basically any stakes however small, but for the love of god please fix the brutal connection issue that has been going on forever and ever now. The site never has more than a few hundred people and never more than 50-60 in any single tourney so I don't understand how this is still an issue after so long. Really this should be issue 1 2 and 3, why should anyone ever risk significant amounts of money when the connection can drop with no warning at any time.

Thank you for your feedback. While most users play without frequent major issues, a handful of players have reported similar problems. This issue is tricky because it seems to only occur in certain combinations of Windows version & hardware. This bug is known to us and we have deployed resources to fix it.