DELAY BET - DELAY bet 30sec after set when Markets have settled

Advanced automation available in Guardian - Chat with others and share files here.
Post Reply
rencoetz
Posts: 92
Joined: Thu Aug 22, 2019 5:25 am

Hi All

I am having difficulty with the conditions part of adding a delay in bet once signal changed condition has been done.

I basically want to bet on a selection based on if she won the first set or not

Rule 1 - Signal 1 - Fav won set 1 - DOGDOWN
RUle 2 - signal 2 - Dog won set 1 - DOGUP
Rule 3 - SIGNAL 3 - GAME AT - POTBETFAV
Rule 4 - SIGNAL - GAME AT - POTBETDOG
Delay trigger @ 1-1 - named Delay with value 5 - trigger 6 time every 6 sec
Rule 5 - Back guardian selection if(conditions , 1-1 and signal changed cond, ) + Back selection DOGDOWN or DOGUP

Can anybody assist why the delay trigger is not working ie the bet wont place when the signal changed condition is active.
The bet gets placed when when the signal condition is not in the conditions - so I know it is this rule that is FALSE and the bet doesnt trigger

There is almost no help on the delay bets rule and so frustrating.

I honestly think a lot more more videos / are needed to understand how BA works when a system has become more complex. Very frustrating at times

Maybe the public must start submitting its own videos

Still loving BA though - my Bot almost complete to where I need it to be.

Any help will be appreciated
User avatar
ShaunWhite
Posts: 10472
Joined: Sat Sep 03, 2016 3:42 am

I can't advise on this specific bot but rather than having DOGUP and DOGDOWN signals it would be be simpler to have just DOGUP and set it to 1 for true, zero for unknown (or neither up nor down), and some other value for false Eg - 1 (ie the dog is down).

One variable (aka signal in BA lingo) with several states is preferable to having a separate variables for each state if the states are mutually exclusive. Eg if the dog can't be up AND down.
It helps you to avoid logical inconsistencies such as testing two variables as both being true when only one at a time can be true. It probably won't help this specific issue but will make your bots easier to maintain and more robust as they get more complex.

Sometimes rewriting a bot can help you see things you couldn't see before. If you got rid of DOGUP and DOGDOWN and replaced them with DOGSTATUS (where a DOGSTATUS = 1 if they are up and DOGSTATUS = 2 if they are down etc) then you might have a light bulb moment?
User avatar
ShaunWhite
Posts: 10472
Joined: Sat Sep 03, 2016 3:42 am

Re complexity I don't think it's helped having stored values AND signals. Which you choose seems to just depend on how you want to assign its value. How is a signal containing the value "1" any different to a stored value containing the number "1"? There's probably a reason but I don't see it. Why not just allow stored values to also be incremented/decremented or set to constants, or allow signals to be also assigned from data values.?
rencoetz
Posts: 92
Joined: Thu Aug 22, 2019 5:25 am

Hi Guys thanks for the input.

I require stored values and signals for my bot being at 0-1 or 1-0 and 1-1 I need to know what the the corresponding odds are for the players as I get in at a when a player trades a specific odds I.e in Relation to how they were trading before ie if the DOG 🐕 loses the first set she will trading at X - and I she gets back into the match she will trading at Y in the second set and Z when it is 1-1. So based on 0-1 ; and 1-1 Odds I get in at a certain point in set 2 and 3 on a specific nominated player. Everything in my bot works perfectly but the only problem is that at 1-1 the bot places the bet and stores the value to quickly as the markets are still moving and require about 30sec to settle where liquidity comes through. It’s good it places it early but it’s a couple of ticks off at 1-1 and I have other places I can get in after 1-1, but this value is not a 100% correct. I hope this makes sense ?

So all I basically need is a delay at 1-1 where thee in bet / or store value is delayed at 1-1 and after set the first set
User avatar
Dallas
Posts: 23532
Joined: Sun Aug 09, 2015 10:57 pm

What time have you used for the signal changed condition?
If its the same in each box ie, between 6 secs and 6 secs after signal value changed then it wont trigger, the 2nd box needs a later time

Also double check both signal setting and conditions for any typo's in the signal name
User avatar
ShaunWhite
Posts: 10472
Joined: Sat Sep 03, 2016 3:42 am

Dallas wrote:
Thu Jan 09, 2020 11:40 am
Also double check both signal setting and conditions for any typo's in the signal name
I seem to remember being caught out by a trailing space in a name once, but I could be wrong as I'd assume they're all trimmed.

It seems OTT but I've sometimes resorted to writing the stored value/signal names down on a good old fashioned piece of paper. Then stepping through my bot imagining a given scenario for each pass, writing the new values down each time. It's suprising how many time you realise you're using a condition on something that hasn't been set, or expecting a value that's already been cleared. It'll be there somewhere and when you find it you won't believe you didn't see it before.
User avatar
jimibt
Posts: 4197
Joined: Mon Nov 30, 2015 6:42 pm

ShaunWhite wrote:
Thu Jan 09, 2020 5:45 pm
Dallas wrote:
Thu Jan 09, 2020 11:40 am
Also double check both signal setting and conditions for any typo's in the signal name
I seem to remember being caught out by a trailing space in a name once, but I could be wrong as I'd assume they're all trimmed.

It seems OTT but I've sometimes resorted to writing the stored value/signal names down on a good old fashioned piece of paper. Then stepping through my bot imagining a given scenario for each pass, writing the new values down each time. It's suprising how many time you realise you're using a condition on something that hasn't been set, or expecting a value that's already been cleared. It'll be there somewhere and when you find it you won't believe you didn't see it before.
i've probably mentioned it in passing before. On a new or *sticky* rule I tend to also use a bit of paper with a flow chart of the intention and follow both the logic and expected values. I would then use the BA log to compare the values when plugged into the flow.

don't use it so much now but was very helpful, especially if it had a lot of small moving parts that were more or less self contained.
rencoetz
Posts: 92
Joined: Thu Aug 22, 2019 5:25 am

Dallas wrote:
Thu Jan 09, 2020 11:40 am
What time have you used for the signal changed condition?
If its the same in each box ie, between 6 secs and 6 secs after signal value changed then it wont trigger, the 2nd box needs a later time

Also double check both signal setting and conditions for any typo's in the signal name
Hi Dallas

The second box is between 1 and 29 sec ago - not sure if this is correct ?
You do not have the required permissions to view the files attached to this post.
Last edited by rencoetz on Fri Jan 10, 2020 4:46 am, edited 3 times in total.
rencoetz
Posts: 92
Joined: Thu Aug 22, 2019 5:25 am

How do I place a bet with a 15 sec delay after something has happend ?
the event 1-1

Surely this is not difficult ?
User avatar
Dallas
Posts: 23532
Joined: Sun Aug 09, 2015 10:57 pm

The time in the top image needs to be set as between 15 and 16 secs

I can't see how all your conditions are configured but rather than have a set a signal rule applied on ANY then your back/lay rules applied to Guardian nom 1 (or 2)
I always use seperate rules, ie, set signal applied to nom 1 and another applied to nom 2
then have a back/lay rule applied to nom 1 and 2 also (with signal conditions), that avoids any chance of errors
Post Reply

Return to “Bet Angel - Automation”