Quote from: paradoxal420 on December 10, 2014, 08:30:41 AM

Enough with these stupid temporary fixes. Please have the devs do their job and just shut down the site until its actually working properly. This is fucking ridiculous and it has nothing to do with too much traffic or DDoSing. Fix the backend please!

Ive enjoyed playing on PrimeDice, but would have to agree a bit with this sentiment. For the amount of money I can assume the site makes on the constant churn of wagers, I think there needs to be a bit more focus on:

1.) Uptime in general: Not limited to site uptime, but also autobetting (using built in autobet) hanging in the middle of perhaps a martingale series.

2.) Faucet: While this isn't a big deal breaker for me, I know there are a lot of players who rely on the faucet in order to play at all. While I've played a bit on it, simply for the challenge (ran 5600 to 1.8M) there seems to be a lack of consistancy in terms of claiming a faucet reward.

   - Some of the captchas- specifically the TiVo Captchas are actually incorrect. The displayed captcha on one is Tivo yet TiVo is required for payout.

   - It seems the time to claim is roughly 3 minutes from the point of zero account balance, nit last claim. Yet if you request a payout even a few seconds early, it penalizes you by adding additional time.

That said, perhaps some simple copy on "this is how it works" would be helpful to users.

3.) Roll Speed: This is a big frustrator for me personally. From what I understand the cause of the lag users are experiencing, which at times can slow auto-betting down to as low as 4 bets per minute, is directly related to the number of users and bots on the site. At least this is what I've read and seen said by mods in the chat room.

   - If this is the cause of the lag, perhaps disable the API, until a patch that solves the problem can be put into place.

   - It appears that during high lag times, the overall bet count for the site is much slower, so to me it seems the user count isnt the cause of the lag. If x bets per minute can be processed per second server side, shouldnt that remain constant? It appears there is some other bottleneck or throttling going on here, but thats just my perspective based off playing on the site.

   - Regardless, I think in all fairness and transparency to the players, a more consistent and expected roll speed should be a high priority fix. Its frustrating and also dangerous and in some ways wreckless - to allow say a new player to log on, set up an autobet and "think" he will be autobetting at 7 bets per minute... To then base his bets around that variable (which should really be a constant) and then walk away. When the user comes back he then realizes the site has ramped up to 70 bets per minute. These swings in roll speed are not fair to the players or community as a whole.

4.) Referall Bonuses: I know a lot of users have had issues that referral bonuses have not been paid as they should (simply quoting people from chat); however I personally used the referally link of my brother, who runs a twitter feed and has been promoting PrimeDice for weeks.

   - I had never registered as a user or played PrimeDice at all prior to using his link and setting up my account. However we work in the same office, on a dedicated IP, although I would think the site would differentiate us as users as I used my own computer and again had never used the site before.

   - After betting personally over 1100 BTC (Im top for the week on Leaderboard) - he has never seen a referall commission for me.

   - He also mentioned his referal count on his affiliate link page lists 20+ referalls, yet only 7 or 8 actually "list" below in terms of names. And out of all these only 500 Satoshis have been paid. I can inderstand his frustration considering he A.) Turned me onto the site, where I have wagered 1100 BTC, B.) His other referrals dont seem to add up or even tally corrctley, C.) He has done a decent amount of promotion on his twitter feed with 3000 plus followers - all crypto related - and seen zero returns.

For Reference: His Twitter Feed is @BlTC0lN Thats @BLTC(ZERO)LN and his PD Account is InviteBonus1

Now this all stated, I know Stunna has had a lot of things pop up, such as the 32 Bit limitation/number of bets, as well as migrating the server or signing up with cloudflare (not sure on the specifics), but I hope he takes the time to read this post and give it some thought, and is able to make steps towards remedying what I have listed above, and believe to be the top issues complained about in the chatbox.

Again, not coming down with an iron fist here. I know Stunna has had his work cut out for him. But for those of us who play the site and contribute to the community, hopefully he can respond to these issues and provide a realistic timeframe for fixes to be implemented.

My only thoughts in closing are if PD needs to be able to handle X bets per min based on the current user base, whatever patches and fixes that are applied should be geared towards X times (4) bets based on current user base... Which will allow the site to grow and not immediateley be bogged down as growth continues.

Thanks for your time,

CD