Jump to content
Stake Forum

Josh

Developer
  • Content Count

    35
  • Joined

  • Last visited

Player Details

  • Username
    Josh
  • Wagered (BTC)
    6.24038628
  • Wagered (ETH)
    31.46645132
  • Wagered (LTC)
    7.23086129
  • Wagered (BCH)
    0.27163686
  • Wagered (DOGE)
    108,644.80919
  • Ripple (XRP)
    14,672.37153

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. You're going to have to be more specific than that I'm afraid @S1MPL3X, what exactly doesn't work? I have an iPad2 and an iPhone 8, I play Stake on both regularly without issue. We also test on multiple other devices and nearly 1/2 of ours play on tablets/phones so I'm not really sure what you're referring too? Certainly, if I knew what the issue was 😅
  2. The payouts/probabilities for Baccarat (all Baccarat games, not just ours) can be seen here: https://wizardofodds.com/games/baccarat/basics/#toc-Odds Check out the Infinite Decks section. You could say the edge sorta' varies slightly depending on what fields you bet on. But a single bet on "Banker" or "Player" is ≈1%, single bet on "Tie" is actually higher. If you bet on both "Banker" and "Player" you basically just "pay" 1% over time.
  3. Ha, I got here 1st mate...
  4. query Bet($iid: String!) { bet(iid: $iid) { ...BetFragment } } fragment BetFragment on Bet { id iid type bet { ... on CasinoBet { ...CasinoBetFragment } } } fragment CasinoBetFragment on CasinoBet { id active payoutMultiplier amountMultiplier amount payout updatedAt currency game user { id name } } Mines is a stateful game and therefor has various different actions associated to it. Here are the main ones: Mines Active Bet (query for an active miens game) [Authenticated] query minesActiveBet { user { id activeCasinoBet(game: mines) { ...CasinoBetFragment state { ...MinesStateFragment } } } } Mines Bet (start a new mines game) [Authenticated] mutation minesBet( $amount: Float! $currency: CurrencyEnum! $minesCount: Int! $fields: [Int!] ) { minesBet( amount: $amount currency: $currency minesCount: $minesCount fields: $fields ) { ...CasinoBetFragment state { ...MinesStateFragment } } } Mines Next (bet on an active mines game) [Authenticated] mutation minesNext($fields: [Int!]!) { minesNext(fields: $fields) { ...CasinoBetFragment state { ...MinesStateFragment } } } Mines Cashout (cashout active mines game) [Authenticated] mutation minesCashout { minesCashout { ...CasinoBetFragment state { ...MinesStateFragment } } } The following two fragments are used in the above mutations and queries: CasinoBetFragment fragment CasinoBetFragment on CasinoBet { id active payoutMultiplier amountMultiplier amount payout updatedAt currency game user { id name } } MinesStateFragement fragment MinesStateFragment on CasinoGameMines { mines minesCount rounds { field payoutMultiplier } }
  5. This should be fixed now @paito, sutobet settings are now always reset when leaving a game. Thanks for reporting. 👍
  6. 1. Agreed, that'll be live probably sometime today. 2. Bit confused by this one, the alerts that slide in on the left? They do disappear by themselves, or do you mean the the bell on the right? 3. Click on your username (top right), "cashier" and "community" there. 4. We could probably add some filtering to this in future, I'm assuming you're talking about here: https://beta.stake.com/transactions/bets 5. If you have "instant bet" enabled and autobet, that's max speed. If there's one more bet after you click stop, that's because the bet is already "in flight" between you and the server, I can't stop that! 6. How should autopick work then? I don't think we'll change the odds tbh, but not my call, so I'll pass it on. 7. This becomes a bit tricky as the "old" wheel only had like 12 segments max, "new" wheel has 50, that kinda makes it hard to fit the numbers 🤷‍♂️ 8. We tend to to do this as it's a bit more pleasant for users on mobile I think, but I'll happily be proved wrong if enough people tell me they don't like it! Thanks for the feedback and bug report! 👍
  7. Looks like our DNS provider has resolved the issue! Starting to see traffic returning to normal. Sorry for the wait!
  8. Think we're having DNS issues guys, will keep y'all updated. @GodIoft we deffo do care!
  9. Thanks @toohoola, at @Bojana , I'll take a look at this.
  10. Thanks for the feedback guys, will address shortly. ?
  11. We now change the number of options available base on screen dimensions
  12. Hey guys! So on mobile with move this to "settings" in an effort to save space, see attached image. If someone has a suggestion to make this move intuitive, I'd be happy to take suggestions.
  13. Hi guys, this is likely an error with a recent front-end update, we're looking in to the issue now, thank you for reporting and your patience.
×