Assuming it hasn’t changed too much since last time I looked into it, the ticks received and counted in any method similar to the one proposed above are not a strict match to tick by tick, therefore when in (x)ticks charts the array in a personal code won’t receive x of them per candle, because it wraps up ticks being in same timestamp as being “one” instead of multiple, whereas the platform built-in ticks counter is able to differenciate them and count all of them (that means not just 2 separate transactions that could theoretically be so close from each other they are in same timestamp, but also more frequently the case of a market order meeting more than one limit order the opposite way: probuilder code with arrays would count these as one, built-in tick-by-tick would be able to count these as being as many as amount of filled limit orders by the solo market order). So you’ll always have some “missing”, and can’t assess how many remain in your [x] ticks candles.
As far as I can assess, next batch of new coding instructions might help to get a closer count with some extra maths, but it would still be inaccurate anyway.
As per forum use guidance in yellow box at bottom of this page just before the “submit” message button, please don’t double-post, I have to delete your same request in the other 2 posts yesterday and today to keep only current topic as active. Thanks.
.
