Thanks for the reply.
Following on from your comments I've looked at the set of triggers again and I can see that the user variable current_bet gets set from the value in another user variable current_loss and it's that variable that gets set to a floating point number with the trailing zeros.
I've changed the name of current_loss to my_current_loss to avoid any possible clashes with frequently used names and rerun the triggers. Unfortunately, the same problem happens.
The variable my_current_loss is defined as a constant and set to an initial value of 0.00.
I've attached some screenshots of before an after the first bet is settled.
This first bet gets placed ok. I then settle the market and make the bet lose. This causes the trigger that deals with a loss to fire and set the appropriate variables.
11:43:29 | Checking market "Horse Racing / GB / Wolverhampton 30th Aug / 13:00 Wolverhampton 30th Aug - To Be Placed". |
11:43:29 | Checking condition and Market's Settled P/L is less than 0. |
11:43:29 | Condition is: TRUE. valid for 1 selections: Youllovemewheniwin. |
11:43:29 | Selection: Youllovemewheniwin, initial expr.: current_step + 1, intermediate: 1+1, final: 2. |
11:43:29 | Setting variable current_step to 2. |
11:43:29 | Selection: Youllovemewheniwin, initial expr.: my_current_loss - last_pl, intermediate: 0--2.36, final: 2.36000000. |
11:43:29 | Setting variable my_current_loss to 2.36000000. |
11:43:29 | Selection: Youllovemewheniwin, initial expr.: IF(current_step > 1, my_current_loss, current_bet)), intermediate: IF(2>1,2.36000000,2.00)), final: 2.36000000). |
11:43:29 | Setting variable current_bet to 2.36000000).
|
The user variables are now as shown in the second attachment.
As you can see, my_current_loss is set to 2.36000000 which in turn sets current_bet to 2.36000000. This causes the next bet to fail when using current_bet as the amount to bet.
Any idea why this happens?