Yes, there are predefined exit-only strategies available in MC. You have to be careful though, because if exit strat places an order that you don't like, and you move it, strategy will place it back. Some people end up fighting with their own strategies.
You can also use the automated exits available in the Trade Panel.
MultiCharts - Raising the Trading Standard.
Please send me a private message if you have any further questions about MultiCharts
Please note that you can't place the multiple target exits simultaneously in MC through power language. If the first target gets filled - it would cancel the other target orders and then resubmits again at the same price ( you would lose the position in the queue).
The following user says Thank You to ejtrader for this post:
I thought that "named orders" was possible now, and you can exit a specific "named" entry point and control exact what position you are exiting, not some sort of FIFO.
Due to time constraints, please do not PM me if your question can be resolved or answered on the forum.
Need help? 1) Stop changing things. No new indicators, charts, or methods. Be consistent with what is in front of you first. 2) Start a journal and post to it daily with the trades you made to show your strengths and weaknesses. 3) Set goals for yourself to reach daily. Make them about how you trade, not how much money you make. 4) Accept responsibility for your actions. Stop looking elsewhere to explain away poor performance. 5) Where to start as a trader? Watch this webinar and read this thread for hundreds of questions and answers. 6) Help using the forum? Watch this video to learn general tips on using the site.
If you want to support our community, become an Elite Member.
The following user says Thank You to Big Mike for this post:
Mike - it is still not possible to have simultaneous exit orders with MC.
Basically when the first target order is filled - it would first cancel the other orders and then submit a new order at the same price and would be placed at the end of the queue and there is "absolutely" no work around for this issue at present with any combination of power language code.
For further details - please see the PM request here.