Now the plugin tries to workaround this weirdness by disregarding duplicate tickSize LAST_SIZE situations (Together with the exact sizing) and correcting missing ticks usign CUMULATIVE volume sent with tickSize Quantity celebration. Correction is required simply because without the need of it we'd wind up owning incorrect whole volume (from https://forexdataforamibrokerdown63174.blogsvila.com/29300139/new-step-by-step-map-for-forex-data-for-amibroker