Problem backing over 1.5 at a specific time frame

User to User support only. For technical support visit www.betangel.com/support/
Post Reply
zerobetting
Posts: 1
Joined: Fri May 17, 2024 8:25 pm

Αντέγραψε και στείλε στον ιδιοκτήτη του Bet Angel το παρακάτω κείμενο:

---

## Bet Angel automation settings – Early Goal Over 1.5

I am using **Bet Angel Professional v1.63.0** in **Practice Mode**.

### Intended strategy

Monitor football **Over/Under 1.5 Goals** markets from **00:00:01 until 00:37:00 in-play**.

If exactly one goal is scored during this period, wait until the **Betfair Back price of Over 1.5 is 1.28 or higher**, then place one Back bet.

If a second goal is detected before the bet is placed, do not place the bet.

### Rules file

**EARLY GOAL OU1.5 1.28**

The file is applied to all selected **Over/Under 1.5 Goals** markets in Guardian.

---

## Rule 1: Goal for overs

**Rule type:** Set/Modify a Signal Only
**Applies to selection:** Row 2 in Betfair order — Over 1.5 Goals
**Timing:** From `00:00:01` until `00:37:00` after the event goes in-play
**Triggers:** Up to 5 times
**Rearm delay:** 90 seconds

### Conditions

1. **Time Since Unsuspended condition**
- Time since market was unsuspended is greater than **60 seconds**

2. **Historic Relative Odds condition**
- Current selection: Row 2
- Current Last Traded Price
- Is less than the Last Traded Price **65 seconds ago**
- Adjustment: **Minus 15 ticks**

3. **Market Type condition**
- Market type is `OVER_UNDER_15`

### Signal action

- Signal location: **For the market**
- Action: **Increment Signal Value**
- Signal name: `goal`
- “Note signal changes in the market’s log” is enabled.

---

## Rule 2: BACK OVER 1.5 AT 1.28

**Rule type:** Place Back Bet
**Applies to selection:** Row 2 in Betfair order — Over 1.5 Goals
**Timing:** From `00:00:01` until `00:37:00` after the event goes in-play
**Triggers:** Once
**Rearm delay:** 5 seconds

### Parameters

- Place at: **Fixed price**
- Odds: **1.28**
- Intended stake: **£5**
- The currently saved `.baf` appears to contain **£10**, which needs correcting.
- Fill or Kill: Enabled
- Fill or Kill delay: **0 seconds**
- Global settings action: None

### Conditions

1. Market type is `OVER_UNDER_15`
2. Market status is **Open**
3. Market is **In-play**
4. Market signal named `goal` is equal to `1`
5. Current Row 2 **Back price is greater than 1.27**

Therefore, odds of exactly **1.28 or higher** should satisfy the price condition.

---

## Guardian settings

- Guardian refresh interval: **20 milliseconds**
- Restrict refresh: Enabled
- From **1,200 seconds before start time**
- Until **7,200 seconds after start time**
- Rules applied to the Over/Under 1.5 markets in the `Automation Rules 1` column
- Export reports on market closure: Enabled

---

## Problem encountered

The automation has failed to place a Practice Mode bet in at least these examples:

### Ferro Carril Oeste v Ciudad de Bolívar

- Score: 1–0
- Goal scored: 18th minute
- Alert generated: 36th minute
- External Bet365 Over 1.5 price: 1.28
- Both automation rules showed `0/1` in Guardian in an earlier version.

### Sabadell v Real Oviedo

- Score: 1–0
- Goal scored: 23rd minute
- Alert generated: 33rd minute
- External Bet365 Over 1.5 price: 1.28
- No Practice Mode bet was placed.

I understand that the external Bet365 price does not confirm that the Betfair Back price was also 1.28.

### Questions

1. Will the Historic Relative Odds condition correctly compare the price from before the suspension when it is evaluated more than 60 seconds after the market is unsuspended?
2. Is the combination of:
- Time since unsuspended >60 seconds
- Current LTP < LTP 65 seconds ago minus 15 ticks
correct for detecting a goal?
3. Could the 15-tick threshold fail to detect goals in the Over 1.5 market?
4. Is there a better way to ensure that the `goal` signal increments exactly once after each genuine goal?
5. How can I identify in the Guardian log which individual condition prevented the rule from triggering?
6. Is a 90-second rearm delay appropriate for detecting separate goals?
7. Is there any issue with using a market-level signal called `goal` and requiring its value to equal exactly `1` in the Back rule?
8. Can this method handle a goal that is subsequently cancelled by VAR?

Thank you
Post Reply

Return to “Support”