over/under scalp method help wanted

Hi mcbee & Mark,

Thanks mcbee for the heads up and wondered if Mark also agrees with the modification
so I can test further.
I will also study it today to try and understand how it works.
Many thanks
R

I noticed two instances of suspension last week in high profile games where the market had been suspended for a very short period. My audio alarm sounded and my market turned red to indicate the suspension but reverted to the original market almost instantaneously. I could discern no differences in prices on offer. It was as though the "man on the suspend button" had pressed it and changed his mind immediately.

I mention this to complement Mark's reply. High liquidity games can settle very quickly but the period is variable. Suspensions of the type mentioned above really screw things up for bots. Sometimes I wonder if Betfair are playing games with us for their own amusement.

Hi Nigel,
suffice to say, ensure that triggers are not fired soon after a "suspended" message.
It seems it is a major boat rocker.
I like Mark's trigger condition that will only fire when a goal is scored and shown in the scoreline.
R

Hi Nigel,
suffice to say, ensure that triggers are not fired soon after a "suspended" message.
It seems it is a major boat rocker.
I like Mark's trigger condition that will only fire when a goal is scored and shown in the scoreline.
R

Mark has made a sensible suggestion. Unfortunately, Betfair cannot be relied on to update scores and there is a chance that a goal will be scored and your trigger will  still not fire. Forgive me for appearing to be overly pessimistic, past experience of Betfair has made me the way I am

As I write, the API has failed on a day which is probably one of the quietest trading days of the week.  Anything can, and probably will, happen

Hi
sorry - been out xmas shopping.

mcbee thanks for the corrections and the addition for the market refresh.
racepro - thanks for your PM regarding the score.
I forgot if no market score is showing, the value per score is -1
as soon as 0-0 displays, the value changes from -1 to 0 and the trigger was firing
I have made some changes to the conditions for the score and am testing it now
will post an updated file later.

Hi
I’m not going to be on here for a few days so I am posting up what I have.

mcbee, thanks for your help, a couple of things:
The repeating set refresh rate trigger stops the main block from closing, so I put it in a separate block.
The gap ticks and stoploss ticks are both required in dist loss. I have changed it slightly from what you did.

I have changed the market_score conditions to
Markets score has changed
Also changed minutes since last suspension to
(now_time-last_inplay)/mf_minute is greater than sus_minutes
this works better than suspension which can be missed if it’s a quick suspension

Tonight I only tested “wait for a goal to scalp” Constant GS=1
Market’s score has changed works OK,  – but only once. The manual says run it again to check the score has changed again. I thought repeating the block would do it, but it does not. Please could you have a look. Thanks.

Seasons greetings chaps.

hi
i have tested the market score has changed and has not changed in a sperate set of test triggers and it does not work.
so i have replaced it with a variable to record the score at the time of the bet placement.
then if the score1 and score2 is greater than the recorded variable and the other conditions are met the loss stop will fire.

please use test mode

mcbee

download the trigger below

Hi mcbee,

Thanks for the latest updated trigger.
I am currently testing and will report back
tomorrow.
Cheers
R

Hi,
I've tested the trigger on a few matches and it is working okay.
It doesn't show a profit with its current settings and overall losses
are incurred when distribute loss trigger fires.
A common problem with scalping.
I'll try tweaking it and see if we can turn a profit.
Anybody else have any ideas ?
R

As I stated earlier, I have been studying this market for many years, before the proprietary software was introduced.  I could write a thesis on the Over 2.5 Market but I would bore everybody to tears.

The simple solution to your present problem is - do not distribute the loss. This may seem to be, on the face of it, an unhelpful answer but it isn't meant to be so. The market prices will continue to move and there is no compulsion for you to take an immediate loss.

I make some money on the market but only as a result of employing different methods. I sometimes drip feed my money into the market. The complexity of my own operations does not lend itself to automation, and I trade manually.

I tend to agree with you. Most times I introduce hedging loss triggers it
always works against me.
Manual scalping has a lot going for it, and I may have to consider it.
Reading a match live is better than trying to employ a robot to think.
Couple that with a few tech issues from time to time.
The downsides are one can only monitor one match at a time and can be very tiresome
focusing long and hard day after day.
For the time being I will persevere with the trigger idea.
R

hi,
the back after goal trigger fired 11 mins after goal was scored which is too
long. I am modifying the sus_min condition to
between sus_min ......and ....1.50
is this correct?
Thanks
R

hi
NO, the sus_min was set to 1 second, so that is not the problem.
the problem will be the gap_ticks.
so you need to allow more ticks to place the bet earlier.

mcbee

Hi mcbee,

I have just noticed that in one of the matches today it
took 20 mins after the goal was scored for the trigger to fire.
I wanted to place the bet between say one minute after the suspended  sign
and say 3 mins after the suspended sign.
Not by tick measurement.
What I was proposing is the following condition:

'And Selection's trigger expression (now_time-last_inplay)/mf_minute is between sus_mins and 3.00'

I am trying to understand this one condition at a time. I can tackle the gap condition next if that is okay
Thanks
R

hi
but it was set to 1 second, so any time after 1 second, the bet will be placed IF the other conditions are correct.
it took 20 miniutes for the back price difference between the lay price to get within  the gap setting, it is not the timing of the bet, that stopped it from placing the bet.


mcbee