New beta version of Bet Angel v1.63.0 beta1

[Bet Angel]

We are pleased to announce that a new beta version of Bet Angel Professional is available v1.63.0 beta1

Download it from here: - https://www.betangel.com/securedownloads/BAP_1_63_0_b1.exe

Bet Angel VPS only version: - https://www.betangel.com/securedownloads/BAPSE_1_63_0_b1.exe

We have tested this in alpha over the last few weeks and any bugs found have been fixed. We feel it’s ready for beta release to the community ahead of its formal public release.

As with all betas, please gain confidence with the version before using full stakes. If you spot any issues, please post them to this thread.

In this version we add a timed Auto Keypress feature to keyboard shortcuts, Dutching and Bet Modification features to Automation, and many enhancements to Stored Values (including Jump information from TPD and Tennis score information). In addition, this version adds new API operations, the ability to bookmark your favourite Automation Rules files, includes Official Rating and Race Status information from betfair, and implements a number of customer ideas and suggestions. All changes are detailed below.

Features of v1.63.0

Auto Keypress of Keyboard Shortcuts

• Bet Angel can now be configured to automatically trigger a keypress at a defined time and frequency to activate Keyboard Shortcuts.
  • The new 'Auto Keypress' tab page can be found in the Keyboard Shortcuts Editor to define the Auto Keypresses.
  • Conceptually this feature started as a suggestion to allow automatic update of markets loaded into Guardian, but by supporting timed triggers of Keyboard Shortcuts this feature becomes much more open and configurable.
  • Multiple triggers can be defined per keyboard shortcuts profile. They can trigger: just once, once per day, or at a defined frequency in a time range. They can also be limited to only run on specific days of the week if required.
  • Remember that a single keypress can perform multiple Shortcut Actions - just define multiple shortcuts to the same keypress and they will be actioned in order.

• New shortcut to 'Set the Coupon Management settings' in the Guardian category
  • If a keypress is going to be used to apply a Coupon to Guardian (to update the Market List), this action can ensure the Coupon settings are set as required. e.g. Set 'Clearing option' to 'Don't clear' so that the addition of new markets doesn't remove previously assigned Automation Rules.

Additional data values sourced from betfair

• Race Status
  • Provides the status of horse/greyhound race prior to and after the start of the race. Available for UK, Ireland and South African races only.
  • For a list of the status values and descriptions see betfair's documentation here

• Horse's Official Rating

• Note: Both of these data items are available to Automation's Stored Values and can be added as Additional Information at various locations throughout Bet Angel (e.g. Excel, Custom columns in One-click / Guardian / Watch List Coupon, Ladder's additional information area)

Automation – Editor

• A 'Bookmark file' checkbox has been added to the General page of the Automation Editor
  • A bookmarked file will be displayed at the top of any of the Automation Rules Files picklists throughout Bet Angel (e.g. in Guardian or the Servant Manager). By bookmarking your current favourite automation files, you'll be able to find them quickly without having to scroll through every file in the list.

Automation - Dutching

• Four new rule types have been added to support the preparation and placement of a Dutching bet.
  • The concept being that you use 'Dutching - Include a selection' to prepare a dutching bet by including each selection you wish to dutch, setting the price to be used, deciding if the Margin Maker should apply and if a target profit override needs to apply. As with other rule types, you can use conditions to decide whether to include the selection or not. e.g. Fixed Odds condition. Alternatively, you may wish to use the 5 Nominated Selections supported by Guardian for each market to hand-pick in Guardian itself the selections to use with the automation.
  • You can remove previously included selections from the dutching bet being prepared by using either 'Dutching - Exclude a selection' or 'Dutching - Clear all selections'
  • Use 'Dutching - Place bets on included selections' at a time of your choosing (based on any conditions you wish to apply) to place all the necessary bets to dutch the included selections. The rule will compute the correct stake size based on the 'place at' parameters applied to the selections during inclusion.
    • This rule type has parameters to define the staking method, set the margin maker percentage if applicable, and choose whether to actually place the bet and/or log a breakdown of the predicted profit calculations.
    • The new Dutching condition helps trigger the dutching bet at the optimum time. e.g. Use to ensure the total stake is under your defined limits and check that the current dutching book% is providing the desired margin.

Automation - Modify the price of an unmatched bet

• This new rule type allows the price of an unmatched bet to be modified.
  • Includes choices to modify the oldest unmatched bet, the most recent unmatched bet, a bet whose reference is held in a stored value, or a bet that is located at the Servant context price.
  • Additional 'place at' parameters allow the bet to be moved a defined number of ticks (or percentage) above/below its current price.
  • Note: when a bet's price is changed, betfair will issue a new reference for the bet

Automation - Stored Values

• Stored Values can now be set with:
  • Race Completed % (using Race Meter settings).
  • Runner's Official Rating
  • Race Status (as explained above) Note: this is stored as a text SV
  • The Money available to Back above a specified price for a selection
  • The Money available to Back below a specified price for a selection
  • The Money available to Lay above a specified price for a selection
  • The Money available to Lay below a specified price for a selection
  • Volume Traded above a specified price for a selection
  • Volume Traded below a specified price for a selection
  • Unmatched Bet Information of the market/selection
    • The stake / price / reference of the most recent / oldest unmatched bet can be stored
      • Existing filters of price and back/lay type can apply to these new options
  • TPD Jump information (requires subscription to Total Performance Data)
    • The number of jumps ahead/behind of each selection
    • The distance in metres to the next jump / from the last jump, for each selection
    • Note: Currently jump information is available for the ARC Racing courses offered by TPD
  • Tennis Score information
    • The sets, game, points values for a player.
      • Note: As numeric stored values are used to hold the points, an in-game Advantage is scored as 41. e.g. the Score line would be 40-41 or 41-40, rather than 40-Adv or Adv-40
    • If the player is serving (1 = yes, 0 = no)

Automation - Conditions

• The Total Performance Data condition has new options:
  • Race information contains Jump Position information about the course
  • Race information does NOT contain Jump Position information about the course

• The new Dutching condition was added to support the new Dutching rule types

Bet Angel API

• New operations have been added:
  • getBalance - returns your betfair account balance as at the last refresh by Bet Angel.
  • getCoupons - returns a list of all the Coupons that can be used with the applyCoupon() operation.
  • getRulesFileNames - returns a list of all the Automation Rules File names that are available in Guardian.

• Bug fixed:
  • getMarketPrices - previously, in a situation where a selection had less than three back prices on offer, the API would only return one price.

Ladder settings

• Unmatched Bets page - added a new option to choose what happens when an empty cell of the unmatched bets column is clicked (e.g. move the most recent bet to that price).

• General page - added Last Traded Price as an option for the Ladder's header & footer.

• Additional Information page - added Last Traded Price to the Preset Information picklist.

Other changes

• Fill & Kill time field (Global settings on various screens) - Increased number of characters so the maximum value is now 999999 seconds.

• Market Filter Editor - Enhanced to allow a time of day filter to be used when filtering markets by their Start Time.

• Matched Bets pages (main trading screen and Guardian) - new checkbox option to Merge the data so that both back & lay bets are displayed in the same grid and so can be sorted together.

• To help new users, Bet confirmation messages have additional detail when global settings have been applied. They are now also shown when unmatched bets are modified.

[Tuco]

I was looking forward to the next BA version update, but must say I'm initially disappointed with what I read above. I've made lots of suggestions and recommendations that could benefit everyone, but not a single one is included in any shape or form in this beta update.

[jamesedwards]

Some excellent stuff in here. Looking forward to getting stuck into this!

[jamesedwards]

Perhaps I should add this into suggestions, but given more and more useful market-level data is being made available, it would be great to have an area at the top of the one-click screen where market-level stored values can be displayed.

eg for race status, ideally I'd want to display this once as a stored value at the top of the one-click screen. But currently to get this info onto the one-click screen I would have to display the same info against every selection.

[jamesedwards]

Re the TPD jumps info; is there a way to get the raw jump position data for each race? I assume that as the distance to and from the next/previous jump is known, then the positional data of each obstacle is also available? I'm specifically interested in knowing the distance between the final jump and the finish line.

[Bet Angel]

Perhaps I should add this into suggestions, but given more and more useful market-level data is being made available, it would be great to have an area at the top of the one-click screen where market-level stored values can be displayed.

So like the Ladder's Additional Information area, but displayed under the one-click toolbar. That sounds useful - we'll have a think about that.

[Bet Angel]

Re the TPD jumps info; is there a way to get the raw jump position data for each race? I assume that as the distance to and from the next/previous jump is known, then the positional data of each obstacle is also available? I'm specifically interested in knowing the distance between the final jump and the finish line.

We don't have the actual GPS locations of the jumps, but TPD do provide the locations in terms of race distance. Thinking about how it could be added to SVs (in terms of picklists etc), it's probably only the distance to the first jump and the distance from the last jump to the finish line that's important.

[jamesedwards]

Perhaps I should add this into suggestions, but given more and more useful market-level data is being made available, it would be great to have an area at the top of the one-click screen where market-level stored values can be displayed.

So like the Ladder's Additional Information area, but displayed under the one-click toolbar. That sounds useful - we'll have a think about that.

Yes, exactly.

I use the one-click screen for in-race trading and I display lots of market-level stored values such as; leader metres to finish, race pace RAG, TPD data integrity RAG, race complete marker, betfair betting delay, and will be adding the new race status. Currently I have to display all these on every selection where it would be much more space efficient and less complex to have them displayed singarly somewhere at the top of the screen, like what you did with the graphical race progress meter.

[jamesedwards]

Re the TPD jumps info; is there a way to get the raw jump position data for each race? I assume that as the distance to and from the next/previous jump is known, then the positional data of each obstacle is also available? I'm specifically interested in knowing the distance between the final jump and the finish line.

We don't have the actual GPS locations of the jumps, but TPD do provide the locations in terms of race distance. Thinking about how it could be added to SVs (in terms of picklists etc), it's probably only the distance to the first jump and the distance from the last jump to the finish line that's important.

Is it possible in this beta to get the distance between the final fence and finish line as a stored value?

[Dabbla]

Perhaps I should add this into suggestions, but given more and more useful market-level data is being made available, it would be great to have an area at the top of the one-click screen where market-level stored values can be displayed.

So like the Ladder's Additional Information area, but displayed under the one-click toolbar. That sounds useful - we'll have a think about that.

Yes, exactly.

I use the one-click screen for in-race trading and I display lots of market-level stored values such as; leader metres to finish, race pace RAG, TPD data integrity RAG, race complete marker, betfair betting delay, and will be adding the new race status. Currently I have to display all these on every selection where it would be much more space efficient and less complex to have them displayed singarly somewhere at the top of the screen, like what you did with the graphical race progress meter.

This is something I have considered in the past. It would be useful, if we could have custom columns but a single (market row).
Like James, I have a lot servants and data that do not really need to be against every selection.

[Bet Angel]

Is it possible in this beta to get the distance between the final fence and finish line as a stored value?

We'll see what we can do - it sounds like a simple addition as there are no user interface changes other than the contents of the existing picklists.
Something for a bug fix build or the general release build.

[jamesedwards]

Is it possible in this beta to get the distance between the final fence and finish line as a stored value?

We'll see what we can do - it sounds like a simple addition as there are no user interface changes other than the contents of the existing picklists.
Something for a bug fix build or the general release build.

That would be great!

[Bet Angel]

This is something I have considered in the past. It would be useful, if we could have custom columns but a single (market row).
Like James, I have a lot servants and data that do not really need to be against every selection.

I think that's a subtly different request, as if you wish to start Servants, you need a button to press so it seems you are asking for horizontal custom columns rather than Ladder Additional Info style display.
The nature of the one-click grid is that all the columns have to line up and contain the same information type (e.g. you define a column and it applies to all rows from top to bottom). Therefore, we cannot simply add a new row of custom buttons as a fixed first row of the existing grid, with different content to the rest of the rows.

So we would have to create it as a hybrid of the Additional Info area, but also support buttons that start servants. That's fine, as that seems a useful feature.

James, perhaps you could raise this as a separate suggestion, so the discussion can continue there.
It's something we'd need to design and implement carefully, so it won't be a v1.63 feature anyway.

I like the ideas though.

[jamesedwards]

This is something I have considered in the past. It would be useful, if we could have custom columns but a single (market row).
Like James, I have a lot servants and data that do not really need to be against every selection.

I think that's a subtly different request, as if you wish to start Servants, you need a button to press so it seems you are asking for horizontal custom columns rather than Ladder Additional Info style display.
The nature of the one-click grid is that all the columns have to line up and contain the same information type (e.g. you define a column and it applies to all rows from top to bottom). Therefore, we cannot simply add a new row of custom buttons as a fixed first row of the existing grid, with different content to the rest of the rows.

So we would have to create it as a hybrid of the Additional Info area, but also support buttons that start servants. That's fine, as that seems a useful feature.

James, perhaps you could raise this as a separate suggestion, so the discussion can continue there.
It's something we'd need to design and implement carefully, so it won't be a v1.63 feature anyway.

I like the ideas though.

Added as a suggestion.

viewtopic.php?t=31340

[Dabbla]

Not sure if it’s a bug or just removed
In the Keyboard short editor, you can’t sort the columns when clicking on the header. E.g shortcut, Category.