Annoying warning

[Frogmella]

How do i get rid of the warning that I created my ruleset on a different football match to the one I want to run it on? And, How can I create a ruleset in future without creating a link to a particular event? I can't see an option to create a ruleset without a selected market.

And why would anyone make a ruleset that only works on one particular event?

Thanks in advance

[Derek27]

How do i get rid of the warning that I created my ruleset on a different football match to the one I want to run it on? And, How can I create a ruleset in future without creating a link to a particular event? I can't see an option to create a ruleset without a selected market.

And why would anyone make a ruleset that only works on one particular event?

Thanks in advance

Does your rule file select a named football team?

If so, selecting Betfair order 1=home, 2=away, 3=draw should work in the same way but skip the warning.

[jamesedwards]

How do i get rid of the warning that I created my ruleset on a different football match to the one I want to run it on? And, How can I create a ruleset in future without creating a link to a particular event? I can't see an option to create a ruleset without a selected market.

And why would anyone make a ruleset that only works on one particular event?

Thanks in advance

You're applying an instruction to a selection by name. Therefore when you change markets this named selection will not be found within that market.

Capture26.JPG

You need to use something else such as row index or favouritism.

[Euler]

It sounds like you have defaulted to the selection name, so when you move to a different market, that would have changed.

To avoid this, make your selection by betfair row or something similar.

People use a default selection name as that may want to do something on the draw for example.

[Frogmella]

I have used the selection name. BUT in a football match they are always consistent. So the warning doesn't apply. Perhaps the programmers could look at this next time they are having a tinker.

I did that because when you are creating a ruleset you cannot go anywhere else in BetAngel to look anything up. That too can be an annoyance especially when testing a new rulesets in practice mode.

[firlandsfarm]

... when you are creating a ruleset you cannot go anywhere else in BetAngel to look anything up. That too can be an annoyance ...

Agreed, it can be very frustrating especially when memory is failing because of age!!

[Frogmella]

I have an automation ruleset that was created on a soccer Current-Score market. All it does is to create event-level Stored values to keep track of the match score. NONE of the rules are tied to any named selection, but as it is a requirement of all rules to assign a selection it applies to, they were originally assigned to "Row Index 1" but I still get the annoying message. I tried assigning them to "Any" selection...but I still get the annoying message.

The problem is that this message halts my shortcut key routine to set up my day's trading with one keystroke. When I press OK to proceed it then misses out some of the markets when assigning automation rules.

I realise I must have done something wrong. Can anybody help me to get rid of this annoyance?

Thanks in advance for any help.

[jamesedwards]

I have an automation ruleset that was created on a soccer Current-Score market. All it does is to create event-level Stored values to keep track of the match score. NONE of the rules are tied to any named selection, but as it is a requirement of all rules to assign a selection it applies to, they were originally assigned to "Row Index 1" but I still get the annoying message. I tried assigning them to "Any" selection...but I still get the annoying message.

The problem is that this message halts my shortcut key routine to set up my day's trading with one keystroke. When I press OK to proceed it then misses out some of the markets when assigning automation rules.

I realise I must have done something wrong. Can anybody help me to get rid of this annoyance?

Thanks in advance for any help.

Exactly what does the message say?

Perhaps post your rulesfile and someone will probably be able to find the issue.

[Frogmella]

Its the standard annoying message. I can't copy it because the damn thing locks BetAngel until you answer it.

It basically says the ruleset is linked to a selection from the market in which it was created and may not work as expected on another market. But NONE of the rules are linked to any named selection.

[jamesedwards]

Its the standard annoying message. I can't copy it because the damn thing locks BetAngel until you answer it.

It basically says the ruleset is linked to a selection from the market in which it was created and may not work as expected on another market. But NONE of the rules are linked to any named selection.

Try posting your rulesfile

[Dabbla]

But NONE of the rules are linked to any named selection.

What about conditions ?

[jamesedwards]

But NONE of the rules are linked to any named selection.

What about conditions ?

and stored values?

[Frogmella]

Thanks for the replies. I think I see the problem.

I am interrogating each selection in turn to find out which ones have a back price of 1000 to determine what the current score is. But these selections are not specific to the match, they are the same with every Correct Score market. It seems that this irritating warning message is intended to apply to markets where the competitors are named. Like Horse Racing or Tennis or Match Odds in Football.

I'm only using the goal markets where the selections are static for every event regardless of who is playing. I don't need this warning, it drives me nuts and it is obstructing my automation.

I think this needs fixing.

[jamesedwards]

Thanks for the replies. I think I see the problem.

I am interrogating each selection in turn to find out which ones have a back price of 1000 to determine what the current score is. But these selections are not specific to the match, they are the same with every Correct Score market. It seems that this irritating warning message is intended to apply to markets where the competitors are named. Like Horse Racing or Tennis or Match Odds in Football.

I'm only using the goal markets where the selections are static for every event regardless of who is playing. I don't need this warning, it drives me nuts and it is obstructing my automation.

I think this needs fixing.

Attach your .baf rulesfile here and most likely someone will very quickly be able to tell you what needs fixing.

You can export your .baf file by clicking "export rulesfile" in the 'automation' tab of guardian.

[Dabbla]

OK, so you’re doing something like this ?

ames.PNG

If so you’re doing it the hard way.
Just set up a rule for (every) selection
With the condition price of the selection is = 1000 (see screen shot) but tick (current)
That will only trigger on the selections that =1000 Not all of them.
Then you can set a SV against the selection that is 1000. EG, SV= DEAD SCORE and then store a value of 1.
The other option would be to use the specific row index, Row 1 = 0-0 row 2 = 0-1 row 3 0-2 and so on, as Derek has said.
In all honesty it will probably be a combination of both.

Admittedly ,it is a bit misleading when it comes to score lines

You may also want to look at Sibur (Current score) baf on the forum.
viewtopic.php?t=27973&hilit=Sibur+Current+score
It may already do what your trying to do, also you can learn a lot from it.