Skele

don't be a moron i just told you i don't know why your banned, i said did you check with support because that would be the logical first step anyone should take. Second i listed common reason i have heard of them shutting peoples accounts down for. third i don't work for bc so why would you think i would be able to tell you why your account was banned with literally not information from your aside from the fact you seem to have a hard time reading everything that is written. Support is the proper place to take up this grievance though, not with a random player who is answering another players question on the forum. Are you perhaps under 18 because i can see that being a reason just judging from your responses to this situation. Also if you had laid low you probably could have started another account, you have only according the number under your name wagered 11k, so you could be back up to the same level in a day with depositing 50$. Again what causual player is going to go on the forum and attack players because they got themselves banned without first talking to support?

well lets go down the list of possibilities. Do you have multiple accounts? Do you have 2FA on (so you don't get someone else in your account). Did you use any autograbber scripts? Did you bother to ask support their reason for locking you out of your account. Or did you just not secure it and somebody else got into it. I don't know the history here but i do not i have not heard of a single case of them locking someone out of their account without a legitimate reason. (and you are talking locked out as in seized assets and all right? Because if your just muted that isn't the same thing at all).

of course there is, you said you messed with the code to change the increases (i don't know why these weren't exposed as inputs to begin with) so you know know where it is being set. So all you need to do is check there to see if the percentage is within your exceptable range, then figure out how you want to deal with that. if(chance > 1.2) { // you could then reset it to the max of your choosing chance = 1.2; // another option is to reset it back to the original starting value. change = config.startingChance.value; // or just stop the script and wait for someone to look to see why it stopped game.stop(); }

https://bc.game/sd/?sd=10KVO3PX1IDJPV

you would need my user scripts that i wrote that just injects the extra tab into the UI and builds it out. its just javascript and html and i reuse their styles for most things.

i don't think this is necessary but in case it is

yeah i can change all of the settings while my script is running. I am just automating the UI functions. I believe i answered the specifics of the high and low swap in another post but i call hdg.changeToggleWin(); Which isn't accessable from the sandboxed scripting environment.

i have given you all of the code Add the two methods anywhere in there out side of the other methods replace the ">3" with "> maxLossesBeforeBet" then add this line maxLossesBeforeMinBet = GetLossesBeforeMinBet(); Everywhere you set your lossStreak back to 0; add the above line right afterwards.

you should make this 3 a parameter, and even better if you make that parameter able to take a range and then you randomly pick from that range. like below, this way maxLossesBeforeMinBet = GetLossesBeforeMinBet(2-3); if(loseStreak >= maxLossesBeforeMinBet) .... function GetLossesBeforeMinBet() { if(config.lossesBeforeMinBet.value.toString().indexOf('-') >= 0) { var numbers = config.lossesBeforeMinBet.value.split('-'); return GetRandomInt(Number.parseInt(numbers[0]), Number.parseInt(numbers[1])); } else { return Number.parseInt(config.lossesBeforeMinBet.value); } } // Returns a random integer between the min and max. function GetRandomInt(min, max) { var retValue = Math.floor(Math.random() * (max - min)) + min; log.info('Number of losses before pause is set to ' + retValue + ''); return retValue; }

i don't know that hashdice gives you history the same way crash does so it may not be possible through using their scripting sandbox stuff. but really it shouldn't matter, on crash it had to be done this way because you didn't bet so didn't have the results from the bet. In hashdice you always have to bet so you should just be checking the result of that bet to see if you won or lost.

i have but you can't do it with their sanboxed scripts.

https://bc.game/sd/?sd=10IU312ZLGHSLV

20x - https://bc.game/sd/?sd=10IQVUB081AE4Z 30x - https://bc.game/sd/?sd=10IQW9TMT9IOLV 45x - https://bc.game/sd/?sd=10IQWESSWCPZ4J * (12$ big hit) 55x - https://bc.game/sd/?sd=10IQWGW3RJRTOZ * (12$ big hit) 60x - https://bc.game/sd/?sd=10IQX2644E5C0J 65x - https://bc.game/sd/?sd=10IQX55IWBP2XF 70x - https://bc.game/sd/?sd=10IQX7ERN2632R 90x - https://bc.game/sd/?sd=10IQX9KZH2NEAB 120x - https://bc.game/sd/?sd=10IQXD122OEVBN 200x - https://bc.game/sd/?sd=10IQXH0W5MFDAR 250x - https://bc.game/sd/?sd=10IQXJBHIBEVIR 300x - https://bc.game/sd/?sd=10IS3ALKBPWRV7 400x 450x 550x 700x 825x 900x 1000x 1200x 1500x 2000x 2500x 3000x 4000x 5000x 20x - https://bc.game/sd/?sd=10IQVUB081AE4Z 30x - https://bc.game/sd/?sd=10IQW9TMT9IOLV 45x - https://bc.game/sd/?sd=10IQWESSWCPZ4J 55x - https://bc.game/sd/?sd=10IQWGW3RJRTOZ 60x - https://bc.game/sd/?sd=10IQX2644E5C0J 65x - https://bc.game/sd/?sd=10IQX55IWBP2XF 70x - https://bc.game/sd/?sd=10IQX7ERN2632R 90x - https://bc.game/sd/?sd=10IQX9KZH2NEAB 120x - https://bc.game/sd/?sd=10IQXD122OEVBN 200x - https://bc.game/sd/?sd=10IQXH0W5MFDAR 250x - https://bc.game/sd/?sd=10IQXJBHIBEVIR https://bc.game/sd/?sd=10IS3ALKBPWRV7

I have seen like high teens before. Thats why i started putting in the take a break clauses in my scripts so it will stop betting after so many losses and then wait for a win before trying again. It has helped me weather some pretty long red streaks without actually losing all my bankroll, because it ads up fast if you are doubling or tripling your bet.

it sure hasn't and it most likely won't be every. I decided not to spread a lot of the client type stuff around. If i stop being lazy and actually finish packaging it as a browser extension which i can automatically update without having to force the user to update it then maybe i will release that to a limited set of people. Currently i have way too many different version in different locations, and i don't want to fix minor bugs in 6 different versions just beause i didn't wait and finish the browser extension. I have some other ideas for stuff to do with the extension and one of them is essentially extend the current sandbox style scripting to be available in a client script. I would essentially give two text areas a pregame/bet section, and a postgame/hand result section. Then i could pass in more information for people to use and documentation on what does what or contains which information for peopleto use while writing them. This is not goingto happen anytime soon though i have other projects ahead of it as well as my normal job..

https://bc.game/sd/?sd=10HWYT607UUUXF https://bc.game/sd/?sd=10HX0X26J9FXUB

1. I would love tips to default to private, or at least have a way for players to change their own default settings for this one. I almost never want to send tips publicly and when i forget to change it i always end up with a ton of messages and friend invites from the beggers that plague this site, 2. I would love to see game specific chat rooms. For games like blackjack it would be nice if there was a blackjack specific as well as one just for your table, I think this would also help build the relationships between the players, i am much more likely to interact with someone i playing with and let them know well played or congradulate them on a hand etc... than i am to engage in most of the chat that goes on in like the english or global channel. 3. I would love to see more thought and some actual documentation for the scripting. Because there is no documentation it leads to a lot of people having to poke around on their own, granted this can be fun and does lead to things like switching from high to low, which i know a be done because i do it, just not in the sandboxed script. 4. I would love to see some organization and promotion of voice chatrooms like on telegram or discord (i know they are already there on discord. But currently BCs discord is like for silent people and beggers. It needs to be cleaned up so that people actually start using it without being herassed by the few persistent beggers on there. I try not to go there often but i can name at least 1 off the top of my head who begs from evertyone and has for months which i never see them get anything but damn its annoying., 5. I was reading other posts and was reminded of another thing i would like. I would like the ability to exchange valuable crypto for JB. Something reasonably fair like 100k per 1 bcd or something, But currently the only way to get JB is to win it. And for things like boosting rake back percentage or paying withdraw feels i like to use it but i run out often, and would definitely be willing to pay for it. If that isn't a possibility i would be happen if tyou made it tip able at least. That way i could at least make my own deals with other players who don't use theirs..

wouldn't you just change the 99 to 990 or whatever you want the equation is 1/n *99 , so since it is starting at 1/1 that is what you would have for your starting bet, then it would go 1/2 1./3 1/4 etc... i am assuming. So following the same logical step with your equation ((1/chance)*200); with starting chance of 0.02 you get 50 x200 = 10000- and then i you added one it would step down but at some weird rate. either way just the 99 to what you want and leave chance at 1

https://bc.game/sd/?sd=10G6HX701VVQC3

You could also just edit the text box labeled "Base bet" that shows up before you start the script. That is what they are for. Modifying the value in the config declaration is only going to change the default value. This would actually be something good to play around with, because since he isn't assigning the value inside of the main method i am unsure if modifying the input field will be picked up ever by the script or if the values that are there by default on load will stay since those are being assigned to the variables but only at the initial start. I will have to play around and report back on that timing.

couple of pointers here. First are you meaning to increment your lose count by multiples? so below is the else statement in your result handler which handles the losses. If you lose count is < 19 all is well and it increments one. Are you aware that once it hits 19 it will go up by 2, every game and then once it hits 26 it goes up by 3 per game? I am not sure if that is what you intended or not but seems like maybe not which is why i point that out. { if (losecount >= 19) { losecount += (1); varix = 1.5; } if (losecount >= 26) { losecount += (1); varix = 1.66; } losecount += (1); currentBet = (previousBet * varix); chance += (1); } The second little tip has to do with when you write out your logs. I am assuming you want to write it like every 100 bets. But the way the condition is currently written it will write the first log at bet 100 and then you reset the bet number which is actually pretty useful to have. In almost all programming languages there is an operator called modulus. This operator returns to you the remainder of the function so in your case in stead of this: if (betcount >= 100) { logSummary(); betcount = 0; } you can achieve the same thing while keeping betcount accurrate by doing this instead: if (betcount % 100 == 0) { logSummary(); } its saying every time betcount/100 has a remainder of 0 then log, then you can display the actual bet count or use it for other things as well. Other than that looks pretty good.

i did test it out and the answer is, its not available from the scripting sandbox they give you. But if you do all the automation just through simulating clicks and what not on the page said of things there is a handy method for toggling high and low

If it was something other than crash i might agree with you, but since all we ever get to see is the hashed server seed, well i tend to believe what i have witnessed and the probably of some of the trends and the frequencies of occurrences someone make one wonder. But since every is server said and if you were given all to prove that it was hashing then you would be able to predict the results everytime. There are many statements though that while technically aren't lies they certainly aren't necessarily truths. Its funny though how person after person has encountered the exact same experience.

Just so you know if you want the longer history of the game results, if you inject javascript into the main page you can get that no problem, it will only give you the last 2000 games though. You can also get what everyone else is betting that way if you want to write a script that owuld place bets following a particular user. In this same way it would not be hard to rewrite the scripts to play all from the front end like that as they do expose a way to place bests from here as well. Useing the scripting framework i imagine had two different goals in mind. First to make it easier for people who don't know how to auomate web tech in general. And second to be able to control how long and what kind of scripts are ran. I stopped sharing mine widely after realizing that they first will change the beahvior of the games after about 24-48 hours to start matching and defeating your specific strategy, etc... I saw people asking for this script to skip games or do safety rolls. The most successful scripts i have found is the first one i grab configurable random numbers in a range for (number of losses before i skip games because of a loosing streak (generally 2 or 3 games though). how many winning game to see before i bet again (i had to make this more than 1 like i originally had it because i would see after about 24 hours all of a sudden there were very long streaks of LLWLLWLLW just enough losses to get me to sit out on a game that was a win which would trigger me to start betting again. the other script that has actually done nicely for me is just betting a single game with a large bit and low payout like 25% of my bank roll at 1.1x, and doing so an random intervals, like 1 game then skip 0-10 games depending on the random roll. This last approach was the closest i would really get to ensure there was no real pattern for the system to grab and start using against me. if you want crash history you can use this command in the dev console window you can use crash.history. History in this case is a 2000 element array. If you want information on other players and their betting you can get that here crash.playersDict which is a dictionary keyed on playerid with their betting status for the upcoming game. The game or engine object that you have access to in the normal scripts, is just a subset of what is in the crash object in this case, or lbg for limbo, or hdg for hashdice.

Ok finally i have the answer to the burning question on high to set the high and low from the script for hashdice. The answer happens to be we are all complete morons apparently. game.priceLevel is the high or log so game.priceLevel = 'high'; game.priceLevel='low'; or to toggle it game.priceLevel=(game.priceLevel != null && game.priceLevel == 'high') ? 'low' : 'high'; and i haven't tested this but since the game and engine object both appear to be the same as the hdg object i am betting this will also work to toggle it. game.changeToggleWin(); I have not tested the last one though everything else has been tested and confirmed.