+1 888 340 6572 GET STARTED
MultiCharts Project Management
Go to the previous open issue
Go to the previous issue (open or closed)
Please log in to bookmark issues
Open Feature request MC-105

Allow complex commission structures to be specified

Go to the next issue (open or closed)
Go to the next open issue

Currently MultiCharts has very limited commission structures that can be specified when performing backtests. Commissions are really important as they can make or break a trading strategy.

As a minimum I think users need the ability to specify commission as a percentage of the equity traded.

But more complex comission structures need to be possible such as those at Interactive Brokers: http://www.interactivebrokers.com/en/p.php?f=commission#stocks1

The most flexible way to provide this would be to allow the user to write commission structures using Easy Language, and allow those scripts to accept custom inputs in the same way that a "study" or "signal" allows custom inputs. 

For example the "per Trade" commission structure would become an Easy Language script with a custom input variable called DollarValue.

Users could select one of these Easy Language scripts from a drop down list which would change the available input variables below. If the script didn't quite meet their needs they could edit it or create a new script.

Steps to reproduce this issue


Comments (0)
Issue basics
  • Type of issue
    Feature request
  • Category
  • Targeted for
    MultiCharts 8.5 (RELEASED)
  • Status
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (3)
People involved
  • Posted by
    No such user
  • Owned by
    Not owned by anyone
  • Assigned to
    Not assigned to anyone
  • Subscribers
    1 subscriber(s)
    Click here to show the list of subscribers
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
  • Severity
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