Bet Angel wrote: ↑Fri Jun 21, 2019 11:51 am
mcgoo wrote: ↑Wed Apr 24, 2019 7:45 am
All I need now are the ability to record my back/lay matched prices (I think this is essential-especially in tennis or football)
Could you clarify what you mean by 'record' the prices? I'm assuming that you want to use the price that you were last matched as a basis for a future bet?
A: Yes- record the lay matched or back matched prices I was matched at when the opening trade was made
We could look into having some more stored value options. Perhaps 'amount matched of most recently placed back/lay bet on a selection' and 'average matched price of most recently placed back/lay bet on a selection' if that would be of use?
A: Yes- what price I was matched at would be of use. This is especially important in things like tennis where I need to calculate % of stake to reduce liability etc when the price has moved against or for me by x ticks but I only want to partially red or green up
Then there the question of whether most recently 'placed' or 'matched' is important... they could be entirely different bets.
A: True but this is true anyway for matched bets and a checkpoint and time since last bet etc settings potentially could sort this out
Edit: And another situation that I've just thought of is partial matching of a bet. How would you cater for only £10 of a £100 bet being matched, later to be followed by the extra £90. All matched amounts get aggregated together under the same bet reference, so there's a risk you could place an opposing bet before the first one has finished filling. Or place £10 followed by the full £100 which would throw it £10 off in the other direction.
A: Partial matched bets are a problem/dealt with anyway. A fill or kill timeout or a cancel unmatched sorts these out.Even if you are recording a SV as you can do now (by recording the last traded,back or lay price when you place the bet) you have this issue
It starts to get very complicated when there are a number of unmatched bets, placed at different prices, not necessarily filling in the order they were placed, so we'd only do this if just dealing with the most recent bet is actually of use to enough people.
A: See above .Also you only get matched at best price anyway-once- depending on how you place the bet .I only want to record the price I am matched at regardless of partial or not
I can't see that we'd ever be adding lists,queues or arrays to Automation as the compexity of implementation compared to the number of people that would actually use them; it doesn't justify the cost/time.
A: I have seen this done in other iterations of software and would appear to be fundamental to me but am open to correction/discussion. BA must record the current matched price somewhere as the ability to offset,use a stop loss or trailing stop loss would only work using ticks or % if this variable was available? It would be great to have this available as a SV so dependent calculations are accurate.I have noticed how especially in tennis when I am recording an SV (of last traded price, for example)as I place the bet, this can vary by 5 ticks or more to the actual price I got matched at...but as per below perhaps I am doing it incorrectly?