Pages:
Author

Topic: Seuntjies DiceBot -Multi-Site, multi-strategy betting bot for dice. With Charts! - page 19. (Read 274841 times)

newbie
Activity: 75
Merit: 0
Hello, bit-exo normalized, betking and wolfbet still have problems.

last week I try on wolfbet with dicebot Version 3.4.4 it working for manual bet but not on autobet, on dicebot Version 3.4.5 beta it same, maybe on dicebot next version will be stable.

this is the same thing i have happen too so also looking forward to the next version to try again


True, I believe that in the next update will be possible to bet on betking and wolfbet with Dicebot, this program is very good, expecting here.

Hello friend, good morning, is there a prediction for the new update and if the issues of Betking and Wolfbet will be solved?
legendary
Activity: 1717
Merit: 1125
yes 3.4.4

does that make sense which site are selected when im trying to run simulation? its YOLO, but after this commend add I will try change another.

bet numbers are nothing, there is no change if I write runsim(0.1, 999) or runsim(0.1, 100000) or something.

between press enter and crush are 1-2seconds.

update, you know, after changing site simulation are not crushin... wtf Cheesy

The simulator uses the RNG for the site that you have selected to make it as accurate as possible.

This probably means there's an issue with the way I implemented yolodices RNG/verifier. Do you have reset seed enabled?
full member
Activity: 319
Merit: 100
hello, what possible problems can be that dicebot are get msg and closed "dicebot has stopped working" checking for solution etc. when try to run simulation?!

Are you using the latest version of the bot (3.4.4)? Which site do you have selected when this happens? How many bets are you simulating? How long does it take between clicking start and the crash?

yes 3.4.4

does that make sense which site are selected when im trying to run simulation? its YOLO, but after this commend add I will try change another.

bet numbers are nothing, there is no change if I write runsim(0.1, 999) or runsim(0.1, 100000) or something.

between press enter and crush are 1-2seconds.

update, you know, after changing site simulation are not crushin... wtf Cheesy
legendary
Activity: 1717
Merit: 1125
hello, what possible problems can be that dicebot are get msg and closed "dicebot has stopped working" checking for solution etc. when try to run simulation?!

Are you using the latest version of the bot (3.4.4)? Which site do you have selected when this happens? How many bets are you simulating? How long does it take between clicking start and the crash?
newbie
Activity: 75
Merit: 0
Hello, bit-exo normalized, betking and wolfbet still have problems.

last week I try on wolfbet with dicebot Version 3.4.4 it working for manual bet but not on autobet, on dicebot Version 3.4.5 beta it same, maybe on dicebot next version will be stable.

this is the same thing i have happen too so also looking forward to the next version to try again


True, I believe that in the next update will be possible to bet on betking and wolfbet with Dicebot, this program is very good, expecting here.
full member
Activity: 319
Merit: 100
hello, what possible problems can be that dicebot are get msg and closed "dicebot has stopped working" checking for solution etc. when try to run simulation?!

And no problem running the bot in the normal (rolling) mode ?  I never really used the simulation because it wasn't that fast. Is that still not that fast or have that improved in last versions?

all was fine with simple betting bot 24/7 without errors Smiley
hero member
Activity: 1372
Merit: 512
hello, what possible problems can be that dicebot are get msg and closed "dicebot has stopped working" checking for solution etc. when try to run simulation?!

And no problem running the bot in the normal (rolling) mode ?  I never really used the simulation because it wasn't that fast. Is that still not that fast or have that improved in last versions?
full member
Activity: 319
Merit: 100
hello, what possible problems can be that dicebot are get msg and closed "dicebot has stopped working" checking for solution etc. when try to run simulation?!
member
Activity: 309
Merit: 12
Hello, bit-exo normalized, betking and wolfbet still have problems.

last week I try on wolfbet with dicebot Version 3.4.4 it working for manual bet but not on autobet, on dicebot Version 3.4.5 beta it same, maybe on dicebot next version will be stable.

this is the same thing i have happen too so also looking forward to the next version to try again
member
Activity: 359
Merit: 61
︻┳デ═—
Hello, bit-exo normalized, betking and wolfbet still have problems.

last week I try on wolfbet with dicebot Version 3.4.4 it working for manual bet but not on autobet, on dicebot Version 3.4.5 beta it same, maybe on dicebot next version will be stable.
newbie
Activity: 75
Merit: 0
Regarding Betking and wolf.bet. Both sites have updated their APIs and the updates have broken DiceBots integration. I will release an update that fixes the issues as soon as I have time.

Do you have any plans to include the sites below in Dicebot?
https://casinoroyale.bet
https://1xbit.com

I was in contact with casinoroyale.bet a while back, I had some issues with their site that I required they fix before I add them to the bot, they never got back to me.
The vast majority of 1xbits games are not provably fair that I could find, and I do not want to promote sites that are not fair.

You also seem to be under the impression that this is my job and that I attend to queries immediately. It's not. it's a hobby. I work on the bot when I have free time to do so. Please be a bit more patient.

Yes friend, forgive me if I seemed impatient, sincerely not the case, I know how much you have been trying to contribute to the whole community, your work is very special and I am grateful to you!

Bit-exo also has an intermittent problem with Dicebot: 66236 ["Internal Error", null]

Hello, bit-exo normalized, betking and wolfbet still have problems.
newbie
Activity: 75
Merit: 0
Regarding Betking and wolf.bet. Both sites have updated their APIs and the updates have broken DiceBots integration. I will release an update that fixes the issues as soon as I have time.

Do you have any plans to include the sites below in Dicebot?
https://casinoroyale.bet
https://1xbit.com

I was in contact with casinoroyale.bet a while back, I had some issues with their site that I required they fix before I add them to the bot, they never got back to me.
The vast majority of 1xbits games are not provably fair that I could find, and I do not want to promote sites that are not fair.

You also seem to be under the impression that this is my job and that I attend to queries immediately. It's not. it's a hobby. I work on the bot when I have free time to do so. Please be a bit more patient.

Yes friend, forgive me if I seemed impatient, sincerely not the case, I know how much you have been trying to contribute to the whole community, your work is very special and I am grateful to you!

Bit-exo also has an intermittent problem with Dicebot: 66236 ["Internal Error", null]
newbie
Activity: 75
Merit: 0
Regarding Betking and wolf.bet. Both sites have updated their APIs and the updates have broken DiceBots integration. I will release an update that fixes the issues as soon as I have time.

Do you have any plans to include the sites below in Dicebot?
https://casinoroyale.bet
https://1xbit.com

I was in contact with casinoroyale.bet a while back, I had some issues with their site that I required they fix before I add them to the bot, they never got back to me.
The vast majority of 1xbits games are not provably fair that I could find, and I do not want to promote sites that are not fair.

You also seem to be under the impression that this is my job and that I attend to queries immediately. It's not. it's a hobby. I work on the bot when I have free time to do so. Please be a bit more patient.

Yes friend, forgive me if I seemed impatient, sincerely not the case, I know how much you have been trying to contribute to the whole community, your work is very special and I am grateful to you!
legendary
Activity: 1717
Merit: 1125
Regarding Betking and wolf.bet. Both sites have updated their APIs and the updates have broken DiceBots integration. I will release an update that fixes the issues as soon as I have time.

Do you have any plans to include the sites below in Dicebot?
https://casinoroyale.bet
https://1xbit.com

I was in contact with casinoroyale.bet a while back, I had some issues with their site that I required they fix before I add them to the bot, they never got back to me.
The vast majority of 1xbits games are not provably fair that I could find, and I do not want to promote sites that are not fair.

You also seem to be under the impression that this is my job and that I attend to queries immediately. It's not. it's a hobby. I work on the bot when I have free time to do so. Please be a bit more patient.
legendary
Activity: 1717
Merit: 1125
PSA: Submitting a support ticket to a website using my contact email address to get them added to the site IS NOT OKAY. If you want a site added to the bot, contact me directly or contact the site directly (as yourself) and ask them to contact me. IMPERSONATION IS NOT OKAY.
member
Activity: 309
Merit: 12
hi, wondering if you got a chance to look into this yet. thanks Smiley

Wolf.bet Doesn't allow you to use DiceBot if you haven't made a deposit yet or are only playing with faucet/bonus coins. If you haven't yet, please make a deposit in the currency you're trying to play with and then try again.

If the problem persists, please download the 3.4.5 beta (https://bot.seuntjie.com/botpage.aspx?id=79) and try again. Send me the dicebotlog.txt file from then new version again if betting still doesn't work.

with that one i am getting this

Code:

    console.log(
    '%c--------------------------------------',
    'font-size: 16px'
    );
System.Runtime.Serialization.SerializationException: There was an error deserializing the object of type DiceBot.WolfBetClasses.WolfBetResult. Encountered unexpected character '<'. ---> System.Xml.XmlException: Encountered unexpected character '<'.
   at System.Xml.XmlExceptionHelper.ThrowXmlException(XmlDictionaryReader reader, XmlException exception)
   at System.Runtime.Serialization.Json.XmlJsonReader.ReadAttributes()
   at System.Runtime.Serialization.Json.XmlJsonReader.ReadNonExistentElementName(StringHandleConstStringType elementName)
   at System.Runtime.Serialization.Json.XmlJsonReader.Read()
   at System.Xml.XmlBaseReader.IsStartElement()
   at System.Xml.XmlBaseReader.IsStartElement(XmlDictionaryString localName, XmlDictionaryString namespaceUri)
   at System.Runtime.Serialization.XmlReaderDelegator.IsStartElement(XmlDictionaryString localname, XmlDictionaryString ns)
   at System.Runtime.Serialization.XmlObjectSerializer.IsRootElement(XmlReaderDelegator reader, DataContract contract, XmlDictionaryString name, XmlDictionaryString ns)
   at System.Runtime.Serialization.Json.DataContractJsonSerializer.InternalIsStartObject(XmlReaderDelegator reader)
   at System.Runtime.Serialization.Json.DataContractJsonSerializer.InternalReadObject(XmlReaderDelegator xmlReader, Boolean verifyObjectName)
   at System.Runtime.Serialization.XmlObjectSerializer.InternalReadObject(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
   at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
   --- End of inner exception stack trace ---
   at DiceBot.json.JsonDeserialize[T](String jsonString)
   at DiceBot.WolfBet.placebetthread(Object obj)


i have also deposited coins in my account and have no problems with the bot on the site itself
newbie
Activity: 75
Merit: 0
hi, wondering if you got a chance to look into this yet. thanks Smiley

Wolf.bet Doesn't allow you to use DiceBot if you haven't made a deposit yet or are only playing with faucet/bonus coins. If you haven't yet, please make a deposit in the currency you're trying to play with and then try again.

If the problem persists, please download the 3.4.5 beta (https://bot.seuntjie.com/botpage.aspx?id=79) and try again. Send me the dicebotlog.txt file from then new version again if betting still doesn't work.

Neither betking nor wolfbet is working on Dicebot.

As soon as you can get a post here please, thank you!
legendary
Activity: 1717
Merit: 1125
hi, wondering if you got a chance to look into this yet. thanks Smiley

Wolf.bet Doesn't allow you to use DiceBot if you haven't made a deposit yet or are only playing with faucet/bonus coins. If you haven't yet, please make a deposit in the currency you're trying to play with and then try again.

If the problem persists, please download the 3.4.5 beta (https://bot.seuntjie.com/botpage.aspx?id=79) and try again. Send me the dicebotlog.txt file from then new version again if betting still doesn't work.
member
Activity: 309
Merit: 12
Hi, I saw other posts about not being able to log in to wolf.bet and I had the same problem, just had to keep trying until it worked, but I can’t get automatic bets to work, only manual. If I set it at martingale 2x or anything else the manual bets always work but no matter how I set the bot up the automatic bets just show the message at the bottom like “betting 1 at 49%” and nothing ever happens

Can you email me your dicebotlog.txt file please?

hi, it always gives the same error in there so i am just pasting it here, probably easier and faster. this gets added every time i try to make a bet there


System.Runtime.Serialization.SerializationException: There was an error deserializing the object of type DiceBot.WolfBetClasses.WolfBetResult. Encountered unexpected character '<'. ---> System.Xml.XmlException: Encountered unexpected character '<'.
   at System.Xml.XmlExceptionHelper.ThrowXmlException(XmlDictionaryReader reader, XmlException exception)
   at System.Runtime.Serialization.Json.XmlJsonReader.ReadAttributes()
   at System.Runtime.Serialization.Json.XmlJsonReader.ReadNonExistentElementName(StringHandleConstStringType elementName)
   at System.Runtime.Serialization.Json.XmlJsonReader.Read()
   at System.Xml.XmlBaseReader.IsStartElement()
   at System.Xml.XmlBaseReader.IsStartElement(XmlDictionaryString localName, XmlDictionaryString namespaceUri)
   at System.Runtime.Serialization.XmlReaderDelegator.IsStartElement(XmlDictionaryString localname, XmlDictionaryString ns)
   at System.Runtime.Serialization.XmlObjectSerializer.IsRootElement(XmlReaderDelegator reader, DataContract contract, XmlDictionaryString name, XmlDictionaryString ns)
   at System.Runtime.Serialization.Json.DataContractJsonSerializer.InternalIsStartObj ect(XmlReaderDelegator reader)
   at System.Runtime.Serialization.Json.DataContractJsonSerializer.InternalReadObject(XmlReaderDelegator xmlReader, Boolean verifyObjectName)
   at System.Runtime.Serialization.XmlObjectSerializer.InternalReadObject(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
   at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
   --- End of inner exception stack trace ---
   at DiceBot.json.JsonDeserialize[T](String jsonString)
   at DiceBot.WolfBet.placebetthread(Object obj)


hi, wondering if you got a chance to look into this yet. thanks Smiley
Pages:
Jump to: