Tickstory

Example, to avoid the signal when the position opens on 2024.03.08 1.02350 and there is a loss, a dishonest EA coder uses the hard coded settings (03.08 + 1.02300 -1.02400). If only data shift 28 year is applied, then the loss will be at 1996.03.08 1.02350, then loss avoidance will work (03.08 + 1.0...

The only tick data shift that is realistically possible is to the past by 28 years. The main reason for that is the fact that shifting by this value will result in a 100% match between the dates and the days of the week.

The ability to shift the price cannot be viewed separately from shift the timestamp. They must be both together. In the current window, where you have days and hours, you should add a one more option - price shift. "If the date is between <startdate> and <enddate> the price is between x and y t...

Simply a adding another checkbox to alter the price by y points. To calculate the points you will probably need additional steps, so it would be even better not to use points but a double number (as Srormex777 was suggested - "...add 0.2 to each quote ...").

Cheers.

Such short shift times (shifted from May 15th to say June 15th) cannot be correctly applied based on many nuances. For example, we would have tick data on weekends while it would be missing during some days of the week, swap would be charged on the wrong day, we also need to remember about long year...

As Srormex777 mentioned, the ability to shift the price is also important. For example, an EA can use a specific date and price range to hide losses. Considered as an example, EA should not be traded if the date is 05.15 (month/day) and the price is between 1.02300 and 1.02400. This means that the E...