1. How to place a bet on the winner of the previous market?

The parameters of the selection that won in previous market can be accessed using the pw_ prefix (which stands for “previous winner”). Specifically, if you want to address the winner of the closest settled event, you write pw_1_, the winner of the settled event that was before that -- pw_2_ and so on.

Therefore, if you mean you want to bet on a selection with the same index as the previous winner, use this condition to find this selection:

Selection’s Index is equal to pw_1_sel_index.

If you are looking to bet on a selection with the same rank as the previous winner, use this condition:

Selection’s Index is equal to pw_1_last_order.

2. Which condition to use to only bet if the odds of the first and second favourites are at least 10 ticks apart?

And Selection’s Trigger Expression g_ticks(r_1_back_price, r_2_back_price) is equal or greater than 10

Here the function g_ticks returns the difference (in ticks) between the two prices in the parentheses.

3. How to place delayed bets in MarketFeeder Pro?

A delayed bet is usually understood as a bet with a price that is currently worse than the best offer in the market. For example, if the current back price is 2.0, you want to place a delayed bet at 1.5 so that when the price shortens, your bet will be matched, but no sooner.

However, no matter how these bets are called elsewhere, they are in fact ordinary triggers that act as soon as the prices hit the predefined value.

A delayed back bet could look like this:

Delayed back bet

A delayed lay bet could look like this:

Delayed lay bet

A green-up bet that will stay in the market until it gets matched:

Attempt to green up

4. I sometimes get this error message when editing conditions:

Same-level conditions error

What do I do wrong?

The rules of logic algebra require that you do not mix up AND and OR conditions. When conditions are connected with an AND, all of those conditions must be true for the trigger to fire. When they are connected with an OR, any of those conditions can be true to execute the trigger. This fundamental difference makes it impossible for the two logical operators to be used on the same level. But luckily you can add nested conditions by using condition blocks.

A condition block may contain conditions connected with an operator that is different from the one that connects the block itself to other upper-level conditions.

Blocks act like parentheses in math expressions, e.g.:

5 – (4 + 2) is not the same as 5 – 4 + 2, right?

In the screenshot above, you can see that the second and third conditions have different logical operators. To separate them from the rest of conditions, you need to include them in a block like this:

Conditions in blocks

This effectively means: “The selection’s rank must be within the given range AND (Either the current loss is zero OR the price of the selection is below the specified value)”. This is a legitimate logical sentence.

You can add as many logical blocks (nested condition blocks) as you see fit. Use “Add Block” inside the appropriate block menu:

Add blocks of conditions

If you have not heard of BetFair yet or do not have an account, register today and get £20 free. Use the link below:
New customers only, bet up to €/£20 on the Exchange and if your first bet loses, we’ll refund you €/£20 in Cash. Bet must be placed in first 7 days of account opening. T&Cs apply.
Gamble responsibly! Always be aware that betting is NOT risk-free. You must be 18+ years old before you try gambling, but even as an adult, withhold from spending money in an ill-judged manner. Our company does not encourage you to prefer gambling over other meaningful activities. If gambling is affecting your life or the lives of people close to you, please contact GamCare
© 2005-2023 WellDone Creative Software. All rights reserved. Terms and conditions.
BetFair® and the BetFair Logo are registered trade marks of Flutter Entertainment plc. Gamble responsibly.