Hello Guest

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Seuntjie

Pages: [1] 2 3 ... 33
I have several very good reasons to not do this.

Here's one, a quote from the FAQ page I posted earlier:
This error WILL cause unpredictable betting, it WILL make incorrect decisions, it WILL bet the wrong amount at the wrong chance at the wrong side at the wrong time. You WILL lose because of this error if it resumes betting automatically.
What's more important to you? Not being a little inconvenienced by having to click the start button or not losing all of your money?

In my opinion, this should be a good enough reason for everyone, but obviously my expertise with regards to the bot I wrote isn't good enough for you. You clearly think you know better or just don't give a shit about your money.

Other reasons for not doing this right now:
1. I'd need to completely rewrite parts of the bot to allow it.
2. Since I've already done that for KryGamesBot and made it a setting there, I'm not going to do it again for DiceBot.
3. I'm literally only doing bug fixes on the bot and this is not a bug. There's maybe 1 or 2 versions of DiceBot that has new features in the last 2 years. This is because I'm trying to concentrate my efforts on Doormat and KryGamesBot instead.
4. I can be extremely petty and the more entitled someone gets over a request, the more inclined I am to ignore it.

You are talking to air because my responses never reach anything but deaf ears so I've stopped listening myself. And everything's terrible from my side until you're in my seat and have to decline the same arrogant and entitled requests over and over again from the same people that won't listen to reason.

ps: Point no.4 is a joke.
pps: Saying "thanks for your hard work" doesn't make your message any less rude or entitled.

Bugs and Suggestions / Re: login issue with bitsler
« on: September 12, 2020, 05:01:15 pm »
Are you still having this issue?

Bugs and Suggestions / Re: The DuckDice doesn't work
« on: September 12, 2020, 04:57:05 pm »
They've had an API change, they've notified me of the changes and I'm working on a fix.

Bugs and Suggestions / Re: Improve E-mail Notification
« on: September 12, 2020, 04:56:34 pm »
I'll not be implementing this in v3, but KryGamesBot will probably have some settings for this kind of behavior. We'll see when we get there.

1. The bot defaults to -1 and prints out to the console that you need to set a value for nextbet before starting the script if you try to start it without giving nextval an actual value. -1 shouldn't be a valid bet at any site, but some sites (like I assume the one you're using) uses the absolute value of whatever is sent to them as the bet. It's not supposed to get to that point where it sends the bet to the site though, and this will be fixed in the next version. That being said, it is 100% your responsibility to ensure that your script does what you intend and to ensure reasonable precautions against stuff like this from happening before starting the bot. I take steps to protect users against themselves (to their great dissatisfaction usually), but I can't do everything.
Edit: nextbet and previousbet are linked. nextbet will by default have the value of previousbet until you change it (assuming previousbet has a value). This means that if you place a bet manually, from the advanced mode or from a previous script and do not override on script initialization, it will assume that value as a starting bet. Point is, make sure you script sets nextbet on initialization.

2. I agree with you, but with the current architecture of the bot it would be quite a lot of work to implement that properly. The easiest solution for me would be to automatically reset your stats before and after you run the simulation, which I don't see as a good solution to the problem, and since this is already addressed in KryGamesBot, I'm not going to spend time on it for v3. As a workaround for yourself, before and after running your simulations, reset your stats using the reset stats button.

3. Balance is not reliable when referenced at script initialization and could quite often be null (especially when running simulations). I would suggest using this approach when you need to snap your balance at when running the script:
Code: [Select]
--script contents
StartingBalance = nil
LowestBalance   = nil
function dobet()
    if (StartingBalance == nil) then
        StartingBalance = balance-currentprofit
    if (LowestBalance == nil) then
        LowestBalance = balance-currentprofit
    --script contents

4. Again, most of this is already addressed in KryGamesBot, if it's not, please create an issue on https://github.com/Seuntjie900/KryGamesBot/issues. If you're not comfortable using KryGamesBot while it's in alpha (which honestly makes 100% sense), I guess wait untill it's out of alpha and see what you need then.

Can you send me your dicebotlog.txt file please?

DiceBot General Discussion / Re: Luckygames setup
« on: August 22, 2020, 02:18:44 pm »
Does reverse target switch from 30% (<30) low to 30% (>69.99) high or from 30% (<30) to 70% (<70)?

If it's the first, on the "advanced bet settings" tab, the "switch" settings are what you're looking for. If it's the latter, you will need to use the programmer mode.

Bugs and Suggestions / Re: FlashBet Feature
« on: August 04, 2020, 08:04:13 am »
No, it can't.

Programmer Mode / Re: Round a variables value
« on: August 01, 2020, 01:34:11 pm »
For one thing, the syntax is math.floor, not mathfloor. The dot is important.

Secondly, floor rounds DOWN to the closest INTEGER. in other words math.floor(0.999999) will return 0. math.floor(100.99999999) will return 100. So it is doing exactly what it should, just not what you need.

Doing a web search for simply 'lua round' provided this result that seems like a pretty resource: http://lua-users.org/wiki/SimpleRound

Pages: [1] 2 3 ... 33