Bet remains PENDING when using Tick offset bet

[cooldad]

Hi,

I use the following trigger to place a bet: BACK-PL20. What it should do, is place a BACK bet using the provided odds and stake, and then when it is matched, place a LAY bet at a lower odd (20% lower) and the stake adjusted so that the profit is greened out.

However, this is not what happens. The bet ref for this bet continues to show PENDING, and no bet is matched (neither the BACK bet, nor the LAY bet). I am using Betting Assistant version 1.1.0.20 Beta.

Can you explain what I am doing wrong?

Thanks!

[GaryRussell]

It's not implemented in version 1.1.0.20. It's in version 1.1.0.62 which is the latest official version.

You might like to try the latest pre-release version 1.1.0.63 which will be the official version shortly. You can download it using the link below. You will need to uninstall the current version first.

http://www.gruss-software.co.uk/Betting ... _Beta1.msi

[cooldad]

Hi,

I´ve tested it with ver 1.1.0.63d, and it seems to be working fine.

However, I do have a question (probably related to my ignorance, I´ve only recently started to use trigger modifiers).

I wanted to place a bet with a tick offset of 1, and a stop loss offset of 3, to have 1 tick profit, or loose a maximum of 3 ticks.

So this is the trigger I fired:
BACK-TL1-SL3, odd 1.01.

Now 2 bets were placed: a Back bet (was matched @ 1.56), and a Lay bet (unmatched @ 1.55).

So far, so good.

Now the price moved upward. When the Lay odd reached 1.6, a stop loss bet was placed (Lay @ 1.6). In the meantime, the actual Lay odd reached a value larger than 1.6, and continued to rise, so this stop loss bet was never matched. which left me with an undesired liability.

Do you know how to resolve this?

Where can I find an explanation of sliding stop loss, level loss stop loss, level loss sliding stop loss?

Thanks in advance!

BTW, great improvements in ver 1.1.0.63d. I specifically like the concept of profiles!

[GaryRussell]

There isn't a solution to this in the current version. We are considering ways to improve this function and one way of doing it may be to allow you to specify a fill or kill time for the stop loss bet so each time the stop loss is killed it can be triggered again. Do you think this could be a good solution? I am open to suggestions.

[orange]

This is an age old problem and to me the only way round this event is to somehow have the choice of the stop loss being placed x ticks away from the point at which you want it to kick in e.g

Back bet placed at 1.60 tick offset of 2 stop loss of 5

price rises to 1.65 and now the stop loss is actually placed into the market at 1.7(if set to +5), hopefully the market is still at 1.65 and you get out, if not it still gives you a 5 tick window to get out if the price is going the wrong way quickly.

I would like to see it being an option of how many ticks away you want it to place the stop loss from the point that it is triggered, or indeed if you just want it to be placed at the original stop loss point.

One problem with this is, it would make a mess of level loss calculations

This would obviously require some options to be added and in your case you need it for triggers but it is something that I would like to see if possible in the main program as I am not an excel user and only use Betting Assistant as it is so to speak.

Hope the points I have made are clear and make sense.


Cheers

[cooldad]

I´ve given this some thought and agree with orange´s suggestion. An extra option with the number of ticks (or percentage) would do it for me.

So the stop loss modifier will have two variables: the number of ticks (or percentage) to use for triggering the stop loss, and the number ticks (or percentage) to add to (for a LAY), or subtract from (for a BACK), the current price.

As far as I can judge, this should be relatively easy to implement in BA, as all the logic to trigger the stop loss is already there. The stake calculation for Level stop loss could remain unchanged, this means that if the bet is matched at a higher (or lower) price than the current price, the profit won´t be greened out. But this would be OK for me, as the stop loss is an exception, a safety net (or it should be anyway!).

Although I am an Excel developer, I would like to focus on the strategy logic, instead of keeping track of unmatched bets. For me, it is ideal if I can trigger a bet and then forget about it.

Until this option is available, I´ve implemented the following workaround. I am trading during pre-play only. Just before the scheduled off, I check all Unmatched bets. Then for each Unmatched bet, I use the UPDATE trigger to update the price to force a match. And although this works, I am loosing more on the stop loss, than I would with the extra tick (or percentage) option.

Gary, let me know what you think of this.

[GaryRussell]

The option to specify ticks will be easy to implement. Please leave it with me. I have some other issues to deal with first so it will be some time before I can get round to it, possibly weeks, but hopefully not.