D'Alembert problem
Pages:
1
Actions
Choose an action
Print
#1 by sanyboy3400 on 21 Jan 2016
Hi. I'm trying to use this staking plan but something ain't right. Default_backa is 10. When I win, everything OK, but when I lose, next step is not 20, but 90! And next one also. Can you take a look please?
Thanx
sanyboy3400
#2 by MarkV on 22 Jan 2016
Hi
Is your Win/Lose history at zero when you start? The trigger uses win/lose history variable last_lost to update the staking.
Try in test mode after restarting the program without any other bets.
If that works ok, add a trigger at the start of the file to execute one time only, action: reset win/lose history.
MarkV
#3 by sanyboy3400 on 22 Jan 2016
I have done all that. But every time I lose, next bet is x 9, no matter what default_backa is.The same happens with D'Alembert lay trigger. Can't figure this out. I belive it's a solid staking plan for bets over 2.00.
sanyboy3400
#4 by mcbee on 22 Jan 2016
hi
you have set all your triggers to all matching selections, so the counter etc will be x times the selections, resulting in your extra bet amounts.
download the original trigger and learn where you have gone wrong.
mcbee
mcbee
#5 by MarkV on 22 Jan 2016
Hi
I would hazard a guess your soccer market has 9 selections.
The original example trigger shows "favourite" in the selections field.
Your trigger shows "all matching selections" with no conditions except in the backing trigger.
If you look at the "reset the counter" trigger, for each loss the
counter
value will increment by 1, for each selection in the market, because it is set to "all matching selections"
And of course the back price formula is starting_back*
counter
You might need to define your selections in a better way.
MarkV
#6 by MarkV on 22 Jan 2016
snap mcbee
MarkV
#7 by mcbee on 22 Jan 2016
hi mark
happy new year.
beat you by one minute
mcbee
mcbee
Pages:
1
Actions
Choose an action
Print
Desktop View
Hello Guest
Home
Recent Posts
Register
Login
Mobile View