limit the number of bets

hi
new variable trigger
name scored
value score1+score2
condition
or trigger/ trigger block scoretime has been executed
or trigger/trigger block scored has not been executed OVERALL
no more than 10.00

new variable trigger
name scoretime
value now_time*24*60*60

conditions
and trigger expression score1+score2 is greater than0
and trigger expression score1+score2 is greater than scored

your green trigger new condition
and trigger expression scoretime is greater than (now_time*24*60*60)*1.5

you will have to play about with the time settings

mcbee

markV got in as i was typing and having my tea
without testing, we are making this up as we go along

Thanks to both of you!

I learned so much the last two days.

Quote from: mcbee on 05 Jul 2012, 19:23

your green trigger new condition
and trigger expression scoretime is greater than (now_time*24*60*60)*1.5

you will have to play about with the time settings

But the 1.5 is seconds then, isn't it?

Quote from: mcbee on 05 Jul 2012, 19:23

condition
or trigger/ trigger block scoretime has been executed
or trigger/trigger block scored has not been executed OVERALL
no more than 10.00

And I can't pick "trigger scoretime has been executed". With "trigger" I only can pick number of runs and number of runs per selection.

Should I change that to:

or trigger scoretime number of runs greater than 0
or trigger scored number of runs is equal to 0 OVERALL

(I can only mark OVERALL here)

OR

or trigger scoretime number of runs per selection greater than 0
or trigger scored number of runs per selection is equal to 0 OVERALL

Thanks for help!

hi
sorry i am mixing v6 and v7 conditions.
it is number of runs is greater than 0

thank you, you're really quick

and the 1.5 is the time I wanna wait? in seconds?

And if I may ask, what do these 10 secs mean exactly:

Quote

no more than 10.00

Hi
You may find this to be of interest
http://community.welldonesoft.com/triggered-betting-10/can-someone-please-explain/

hi
no more than 10.
is the trigger will monitor the market at every 10 seconds.
you need this because of the score altering so many times, if there is a lot of goals.
once per market, means it the trigger will monitor the market until it has been activated/used etc
once per selection, is the trigger will monitor until all selections are bet on/activated
one time only will monitor once per day/until the triggers are reloaded

mcbee

Thank you!

I think I got it and would like to test the trigger a few more hours, but the trigger doesn't bet anymore.
Last night the trigger was betting for 6 games and greened them up, but it doesn't bet for the the new matches this morning and I don't know why

hi
at the start of the day it is better to reset the win/lose history
use a new trigger to reset win/lose history
no conditions
one time only
because if your hist carries over to the next day and you restart the bot, the hist_count will have the other bets

mcbee

mcbee, above you proposed to count number of bets placed and compare to hist_count. What will happen with counter if bet will be cancelled, voided or lapsed?

Regards,
Anton

hi
mfp does not know if a bet is cancelled,void or lapsed.
you would have to alter the variable in the variable screen every time a bet is cancelled,void or lapsed.

mcbee

Very strange - because I know it is available by API.

Also with all these manual "corrections" - MF does not look like automation too much.

limit the number of bets

Hello Guest