+1 888 340 6572
MultiCharts Project Management
previous_open_issue.png
Go to the previous open issue
previous_issue.png
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
feature_request_small.png
Open Feature request MC-2502

Paper trader triggers stops incorrectly

action_vote_minus_faded.png
5
Votes
action_vote_plus_faded.png
next_issue.png
Go to the next issue (open or closed)
next_open_issue.png
Go to the next open issue
Description

Hi,

In both MC12 and 11 (the only version I've checked), papertrader will trigger a buy stop when the quoted ask = buy trigger price.

If you test it, you'll quickly see so. When trading live.... that event alone ("quoted ask = buy trigger price.") does not trigger a resting stop. Someone has to trade at the price or worse to trigger the stop.

Currently stops can be triggered with price ever trading at the stops trigger price.

Please change this as it seems very unnecessary to introduce such inaccuracy into testing.

Thanks.

Steps to reproduce this issue

Place a resting stop in paper trader. You will see that stop is triggered before the trigger price trades.

Comments (2)
#1
user-offline.png  Will (wilkinsw)
Jan 09, 2019 - 16:31

At the very least, there needs to be a setting within preferences so that the user can define how MC should handle the triggering of stops (in paper trader, and all other MC handled stop triggers).

Futures; stops are triggered by last traded.

FX: I believe some brokers will trigger a stop on bid/ask and/or allow the user to choose.

The latter is very retail though. Would be great if MC made the platform more professional and add the option in preferences.

#2
user-offline.png  Jonathan (Jonathan)
Oct 05, 2020 - 19:04

This issue should be fixed, the stop emulation with futures contracts is not accurate. It allows stops to be triggered when no actual trading has taken place. this affects other parts of strategy and manual trading performance and renders statistics such as shown in Trade Summary to be meaningless.

Thanks for your renewed attention in this matter.

History
Issue basics
  • Type of issue
    Feature request
  • Category
    Not determined
  • Targeted for
    Not determined
  • Status
    Under Review
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (0)
There are no items
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
Attachments (0)
There is nothing attached to this issue
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates