Jump to content

Serlite

Moderator
  • Content Count

    654
  • Joined

  • Last visited

  • Days Won

    5

Serlite last won the day on October 30 2018

Serlite had the most liked content!

About Serlite

  • Rank
    Master

Player Details

  • Username
    Serlite
  • Wagered (BTC)
    10.58449703
  • Wagered (ETH)
    0.65257660
  • Wagered (LTC)
    6.84424949
  • Wagered (DOGE)
    154,769.90000

Recent Profile Visitors

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

  1. Well, that wasn't too horrible! A little more than the expected number of rolls to make, but variance didn't hit me too hard this time. 4.13 Bet: 27,369,828,589 placed by Serlite on 14/01/2019 Wagered 1.70000000 Multiplier 2.00x Profit 1.70000000 97.11 Bet: 27,369,828,790 placed by Serlite on 14/01/2019 Wagered 1.70000000 Multiplier 2.00x Profit 1.70000000 And here's a script for it! Nothing more than a bunch of "if" statements, but it helps save your eyes the trouble of inspecting every bet. Just paste it into dicebot, change the bet/currency, and start()! chance=49.5 nextbet=1.7 bethigh=false currency="Doge" hitFirst = false function dobet() if win then if not hitFirst then if lastBet.Roll <= 5 then hitFirst = true bethigh = true print(tostring(lastBet.Id)) end else if lastBet.Roll >= 95 then print(tostring(lastBet.Id)) stop() else hitFirst = false bethigh = false end end else hitFirst = false bethigh = false end end
  2. Since the feature already exists and was just overlooked, I'll be closing this suggestion.
  3. Serlite

    🏆 [0.1] The Three Wise Men

    Well, this one's done. Though it was...ugh, costly. Over 1k DOGE down the drain, thanks to variance. Not a huge fan of high multiplier challenges... Bet: 27,131,686,815 placed by Serlite on 07/01/2019 Wagered 1.70000000 Multiplier 300.00x Profit 508.30000000 Bet: 27,131,768,401 placed by Serlite on 07/01/2019 Wagered 1.70000000 Multiplier 300.00x Profit 508.30000000 Bet: 27,131,851,324 placed by Serlite on 07/01/2019 Wagered 1.70000000 Multiplier 300.00x Profit 508.30000000 No script this time, because...well, you can probably do this without a script. =P
  4. Whew, messed up my script at first, but my knowledge of SQL was able to save the day. Finished before I rolled too many times extra! Group A - 02.19 Bet: 26,967,947,191 placed by Serlite on 31/12/2018 Wagered 1.60000000 Multiplier 1.01x Profit 0.01632000 Group B - 19.02 Bet: 26,968,491,480 placed by Serlite on 31/12/2018 Wagered 1.60000000 Multiplier 1.01x Profit 0.01632000 Group C - 21.90 Bet: 26,968,701,313 placed by Serlite on 31/12/2018 Wagered 1.60000000 Multiplier 1.01x Profit 0.01632000 Group D - 91.20 Bet: 26,968,768,939 placed by Serlite on 31/12/2018 Wagered 1.60000000 Multiplier 1.01x Profit 0.01632000 20.19 Bet: 26,968,923,089 placed by Serlite on 31/12/2018 Wagered 1.60000000 Multiplier 1.01x Profit 0.01632000 And now for the dicebot script (don't worry, I tested it after I fixed it!): https://pastebin.com/e7uZEPez (Unfortunately, I can't use the forum's code block for this, because copy/pasting seems to carry some invisible characters with it that can mess up dicebot.)
  5. Serlite

    BTC ----> Paypal

    If you're not averse to what amounts to basically a massive exchange fee, there are ways to indirectly convert your BTC to PayPal funds: Buy a Vanilla eGift VISA card (prepaid credit card) from an authorized vendor that accepts BTC, such as Newegg or eGifter Register this credit card with an intermediate PayPal account, then transfer all the credit card funds (be careful to account for PayPal's fee) to your main PayPal account You now have PayPal funds on your main account, though less than what your BTC was worth (because both VISA and PayPal take their own cut)
  6. This was a long hunt, but pretty straightforward. Here we go: 330x bet: Bet: 26,732,062,142 placed by Serlite on 24/12/2018 Wagered 1.60000000 Multiplier 330.00x Profit 526.40000000 Six consecutive alternating 4x bets: Bet: 26,733,617,132 placed by Serlite on 24/12/2018 Wagered 1.60000000 Multiplier 4.00x Profit 4.80000000 Bet: 26,733,617,309 placed by Serlite on 24/12/2018 Wagered 1.60000000 Multiplier 4.00x Profit 4.80000000 Bet: 26,733,617,508 placed by Serlite on 24/12/2018 Wagered 1.60000000 Multiplier 4.00x Profit 4.80000000 Bet: 26,733,617,687 placed by Serlite on 24/12/2018 Wagered 1.60000000 Multiplier 4.00x Profit 4.80000000 Bet: 26,733,617,862 placed by Serlite on 24/12/2018 Wagered 1.60000000 Multiplier 4.00x Profit 4.80000000 Bet: 26,733,618,036 placed by Serlite on 24/12/2018 Wagered 1.60000000 Multiplier 4.00x Profit 4.80000000 Bet with roll number of 25.12: Bet: 26,751,533,493 placed by Serlite on 24/12/2018 Wagered 1.60000000 Multiplier 1.01x Profit 0.01632000 And for the script...well, I think you can handle most of this on your own - it's pretty straightforward. Just use the "win" and "currentStreak" variables for the first two parts. For the last part, some may have noticed that the API is now giving back unrounded numbers, making direct comparison difficult. What we need to do is round the number before comparing it to 25.12, so here's a script that I used for that (change the currency/amount/win chance as needed): chance=98 nextbet=1.6 bethigh=true currency="Doge" function dobet() local formattedRoll = tonumber(string.format("%.2f", lastBet.Roll)) if formattedRoll == 25.12 then stop() end end @williamsh, here's the script if you still needed it!
  7. Serlite

    New Jackpot

    I agree with the sentiment - I've always felt that in its present form, the jackpot doesn't really add anything to the site. The likelihood of rolling 77.77 twice in a row is 1/100,000,000, and this minuscule chance is further exacerbated by the minimum bet requirement (10k) and the manual reporting requirement. At the moment, I don't think anyone would notice if the feature was just completely removed. If the system can't be modified so that winners can be reported at least once in a while (either due to the technical effort involved, or the business costs), then there's little point in keeping it around. Unless people feel there's a non-zero chance that they'll win some kind of prize from the pool, then it won't really influence their decision on whether to play on PD or some other site (and ends up just feeling a bit disingenuous).
  8. I expect we're going to have tons more entries this time around, this one's a cinch! Bet: 26,494,918,987 placed by Serlite on 17/12/2018 Wagered 1.60000000 Multiplier 2.00x Profit 1.60000000 Bet: 26,494,919,177 placed by Serlite on 17/12/2018 Wagered 1.60000000 Multiplier 2.00x Profit 1.60000000 Bet: 26,494,919,387 placed by Serlite on 17/12/2018 Wagered 1.60000000 Multiplier 2.00x Profit 1.60000000 Bet: 26,494,919,568 placed by Serlite on 17/12/2018 Wagered 1.60000000 Multiplier 2.00x Profit 1.60000000 Bet: 26,494,919,751 placed by Serlite on 17/12/2018 Wagered 1.60000000 Multiplier 2.00x Profit 1.60000000 Bet: 26,494,919,954 placed by Serlite on 17/12/2018 Wagered 1.60000000 Multiplier 2.00x Profit 1.60000000 And if anyone really wants the script, to save them...well, at worst probably several minutes, here are the settings I used. Just paste them into the dicebot console: chance=49.5 nextbet=1.6 bethigh=true currency = "Doge" targetStreak = 6 function dobet() if currentstreak >= targetStreak then stop() end bethigh = not bethigh end
  9. Has to be in order unfortunately, Carollzinha. (You wouldn't believe how many times I hit all the numbers I needed early on while hunting, but out of order...) So your third roll number of 44.44 wouldn't be usable; only subsequent rolls of 44.44 would be valid. (If this next part confuses you, just skip it, haha. It's not necessary to finish the challenge, but can improve your odds.) Something worth thinking about though, is that 11.11, 44.44, and 33.33 would also be a valid set of numbers - so don't throw away that unused 44.44 before you finish hunting, because if your next number is a 77.77 instead of a 44.44, you could make your entry 11.11, 44.44, 33.33, 77.77 instead of 11.11, 22.22, 33.33, etc. If you're flexible with what numbers you decide to keep, you can actually improve your odds, because you'll be able to choose more numbers to hunt at once!
  10. Whew, what a tricky one to hunt for! Here we go, I think I may be the first complete entry? Good luck to all the rest of you! Some of you may have noticed that I repeated two numbers, despite what the giveaway said. That's because I hit a dead end after rolling three numbers - there were no other numbers I could make with the ones I rolled! In those situations, it's allowed to repeat earlier numbers - but only once you run out of new numbers to roll. 33.33 Bet: 26,202,406,772 placed by Serlite on 10/12/2018 Wagered 1.70000000 Multiplier 1.01x Profit 0.01734000 66.66 Bet: 26,202,619,469 placed by Serlite on 10/12/2018 Wagered 1.70000000 Multiplier 1.01x Profit 0.01734000 99.99 = 33.33 + 66.66 Bet: 26,202,741,906 placed by Serlite on 10/12/2018 Wagered 1.70000000 Multiplier 1.01x Profit 0.01734000 66.66 = 99.99 - 33.33 (repeat because no other numbers are possible) Bet: 26,202,843,650 placed by Serlite on 10/12/2018 Wagered 1.70000000 Multiplier 1.01x Profit 0.01734000 33.33 = 99.99 - 66.66 (repeat because no other numbers are possible) Bet: 26,202,955,733 placed by Serlite on 10/12/2018 Wagered 1.70000000 Multiplier 1.01x Profit 0.01734000 Now, what about the script? Well, here's what I used: Paste it into Seuntjie's dicebot, and delete the default dobet() function. Don't forget to set the win chance/currency/amount/etc. variables yourself! numbersToHunt = {11.11, 22.22, 33.33, 44.44, 55.55, 66.66, 77.77, 88.88, 99.99} function dobet() if containedInSet(lastBet.Roll, numbersToHunt) then print(lastBet.Roll) print(lastBet.Id) stop() end end function containedInSet(x, set) for key, value in pairs(set) do if x == value then return true end end return false end "But wait a minute," you may say, "this script only hunts for all the numbers, it doesn't do all that math stuff!" And you'd be right - but the thing is, your odds are actually better if instead of settling on the first pair of numbers you roll, you record every valid number you roll for, then work backwards and make the math work. For example, if you rolled 55.55 and 77.77, then you'd aim for 22.22 next to get 3/5 of the numbers. But what if your next numbers were 44.44, 11.11, and 33.33? Well, if you threw away the 77.77, then your numbers would be 55.55, 44.44, 11.11 (55.55 - 44.44), and 33.33 (44.44 - 11.11), then you'd have 4/5 of the numbers instead! So it's safer to keep all the numbers you roll, because you have more options of which numbers you end up wanting to use/hunt. Also, it's harder to code that sort of logic, and I'm tired. =P
  11. Here's an example entry that could work: 22.22, 33.33, 11.11, 44.44, 55.55 11.11 = 33.33 - 22.22 44.44 = 11.11 + 33.33 55.55 = 11.11 + 44.44 Basically, each new number should be based on either adding or subtracting two of your previously-rolled numbers. Another one is 33.33, 77.77, 44.44, 11.11, 55.55 44.44 = 77.77 - 33.33 11.11 = 44.44 - 33.33 55.55 = 44.44 + 11.11
  12. Hey! Who's in charge of these giveaways? They keep getting easier, I was expecting more math and worse odds! XD Bet: 25,735,592,378 placed by Serlite on 26/11/2018 Wagered 2.00000000 Multiplier 5.00x Profit 8.00000000 Bet: 25,735,592,505 placed by Serlite on 26/11/2018 Wagered 2.00000000 Multiplier 5.00x Profit 8.00000000 Bet: 25,735,592,662 placed by Serlite on 26/11/2018 Wagered 2.00000000 Multiplier 5.00x Profit 8.00000000 Bet: 25,735,592,840 placed by Serlite on 26/11/2018 Wagered 2.00000000 Multiplier 5.00x Profit 8.00000000 Bet: 25,735,593,026 placed by Serlite on 26/11/2018 Wagered 2.00000000 Multiplier 5.00x Profit 8.00000000 No script this week, because this one doesn't have a particularly fun or creative script...
  13. That was a lot of numbers to hit! But I finished in basically around the expected number of rolls: 02.20 Bet: 25,482,908,896 placed by Serlite on 19/11/2018 Wagered 2.20000000 Multiplier 1.01x Profit 0.02244000 12.21 Bet: 25,483,168,706 placed by Serlite on 19/11/2018 Wagered 2.20000000 Multiplier 1.01x Profit 0.02244000 26.62 Bet: 25,483,345,493 placed by Serlite on 19/11/2018 Wagered 2.20000000 Multiplier 1.01x Profit 0.02244000 31.13 Bet: 25,483,376,258 placed by Serlite on 19/11/2018 Wagered 2.20000000 Multiplier 1.01x Profit 0.02244000 42.24 Bet: 25,483,745,632 placed by Serlite on 19/11/2018 Wagered 2.20000000 Multiplier 1.01x Profit 0.02244000 52.25 Bet: 25,483,933,185 placed by Serlite on 19/11/2018 Wagered 2.20000000 Multiplier 1.01x Profit 0.02244000 66.66 Bet: 25,484,257,774 placed by Serlite on 19/11/2018 Wagered 2.20000000 Multiplier 1.01x Profit 0.02244000 72.27 Bet: 25,484,375,405 placed by Serlite on 19/11/2018 Wagered 2.20000000 Multiplier 1.01x Profit 0.02244000 82.28 Bet: 25,484,546,357 placed by Serlite on 19/11/2018 Wagered 2.20000000 Multiplier 1.01x Profit 0.02244000 90.09 Bet: 25,484,711,102 placed by Serlite on 20/11/2018 Wagered 2.20000000 Multiplier 1.01x Profit 0.02244000 And now, the script - it'll require some manual intervention, but I felt it'd be safer to record the numbers one at a time, rather than risk losing progress if betting was interrupted (due to something like the connection getting interrupted). Just change the upper and lower limits accordingly, as you work through the numbers! local lowerBound = 0 local upperBound = 9.99 function dobet() -- break down roll number into comparable components local digit4 = round((lastBet.Roll * 100) % 10) local digit3 = round(((lastBet.Roll * 100) % 100 - digit4) / 10) local digit2 = round(((lastBet.Roll * 100) % 1000 - digit3 * 10 - digit4) / 100) local digit1 = round(((lastBet.Roll * 100) - digit2 * 100 - digit3 * 10 - digit4) / 1000) print(tostring(digit1)..tostring(digit2).."."..tostring(digit3)..tostring(digit4)) if lastBet.Roll >= lowerBound and lastBet.Roll <= upperBound then if isValidPattern(digit1, digit2, digit3, digit4) then print(lastBet.Id) stop() end end end function round(x) return math.floor(x + 0.5) end function isValidPattern(digit1, digit2, digit3, digit4) -- identify the palindrome if digit1 == digit4 and digit2 == digit3 then return true end return false end
  14. Serlite

    Do you think pd could be rigged? (No)

    Got good news, actually! The JavaScript code for calculating rolls is publicly available, check out https://primedice.com/verify/how-to-verify. All you need to do is start up a Node.js server (you can either host an instance on your own computer or there are sites online that let you execute whatever code you want on theirs), and plug in the values from a previous seed pair. If you've got some JavaScript knowledge, you could even expand it to verify a whole run of numbers (e.g. All the numbers between two nonce values) and have create your own fully-fledged verification application.
  15. These days, I find the fun to be in writing a dicebot script for the trickier challenges - sometimes you can actually improve your odds with some creative coding!
×