Trailing Take Profit Trailing Stop Loss — 由jason5480 提供的策略

simplemovingaverage trailing trailingstoploss trailingtakeprofit

This script demonstrated a dual trailing take profit and stop loss strategy. Where you take 50% (configurable) of the profit when a price level is reached and then you get the rest when a trailing stop loss is hit.

發布通知:

Logic for short positions added
Logic to exit when "trend" (based on the two sma) changes. This prevents overlapping positions and results in more clear demonstration.
Add option to enable/disable stop loss trailing
Add min max for inputs
Add plots for short take profit and stop loss

發布通知:

Fix bug that caused Stop Loss to not set correctly when Take Profit was triggered in the very first candle
Give more descriptive names to strategy orders

發布通知:

Fix quantity taken on "Short Take Profit" order to match the given quantity percentage given by the user

發布通知:

Add the option to start Stop Loss trailing from the beginning of the entry order as @Soincoin proposed
Trailing Stop Loss is enabled when TP order is filled not when TP target is reached
Simplified Take Profit and Stop Loss Price code to be more readable
Simplified strategy orders
Add offset to the plots to have a more intuitive representation
Fixed a bug where TP and SL orders were not filled if they triggered in the very first candle
Don't draw the TP price if the TP order is filled

發布通知:

Fixed a rare bug that caused some transactions to not exit 100% of the position size when Stop Loss and take Profit was hit at the same candle.
Fixed a bug that made the percentage quantity handled by the Stop loss order incorrect.
Changed the name of "Take Profit" odrers to "Take Profit / Stop Loss" to better reflect the fact that the order will exit if stop loss price is reached first.
Simplified strategy order code and added closeLongDeal and closeShortDeal variable to make code more readable.

發布通知:

Add check to calculate TP and SL prices when it is within backtest period to avoid unnecessary calculations and painting outside the area of interest
Add check to the Take Profit Executed condition that compare the high/low price with the take profit price

發布通知:

Replace deprecated transp argument with color.new to prevent warnings during compilation of the script

發布通知:

Fix a rare bug that were causing the stop loss to be calculated wrong when there was a back to back entry with the previous one
Use strategy.percent_of_equitity
Draw lines with width 1
Add highlighter for positive and negative price moves

發布通知:

Update to pinescript V5
Take profit steps to 0..05 and deviation steps to 0.01

發布通知:

Minor transparency issue

發布通知:

Transparency deprecation

發布通知:

New Break Even feature added!

If Break Even check box is checked, then when the take profit price is hit, the stop loss will be moved to the entry price or "better" depending on the stop loss % and the trailing settings. The more strict value will be applied.

發布通知:

Let's face it a Green-Red color model is more intuitive!

發布通知:

minor optimization

發布通知:

Thanks to the user @HBGJA for pointing out and solving a bug that caused longs after a short close alerts not to be executed.

發布通知:

Happy New Year!
Most of the questions I had last year was about setting strategy alerts and connecting them with webhooks to your bots.
So I added the ALERT MESSAGES section to show you how you can send different execution messages to your bots and execute your orders!
If you are using the 3Commas bots all you have to do is to put your bot IDs and email token in the strategy settings. Add an alert, check the webhook, set the URL and write the [] in the message text box.
If you are using any other bot system that can be used with webhooks, you can always modify the messages according to your Bots API
Many code refactorings and optimizations to better use this script as a template and plug your own strategy at ease

發布通知:

Add bot tags

發布通知:

Fix quotes around string message fields of 3Commas messages (message_type, email_tocken, action)

發布通知:

Let the user put the whole alert message as an argument. Strategy will forward it to the {{strategy.order.alert_message}} place holder as it is

發布通知:

Bug fix: (rare/minor) Remove 'strategy.position_size == 0' condition in stop loss calculation that made the very first stop loss price target to be calculated based on previous 'strategy.position_avg_price' instead of 'close' if the previous position closed exactly one bar before!

發布通知:

NEW FEATURE! After many requests for an ATR based trailing approach I added:

A new take profit method that is ATR based. Now you can set the length and the multiplier for long/short in the settings menu.
A new deviation method that is also ATR based. Deviation is used for take profit trailing!
A new stop loss method that is ATR based. Now you can set the length and the multiplier for long/short in the settings menu.

發布通知:

NEW FEATURE RELEASE (TOO RISKY :P)

Risk/Reward Ratio Take Profit type added! Now you can set price target based on RR and your stop loss
Risk management for entry quantity calculation is added! You can set what percentage you are willing to risk for every trade and the amount for the entry is calculated accordingly
Leverage variable is added that multiplies the initial amount of every trade
Set minimum trade price that your exchange support
Set max drawdown percentage to stop strategy

發布通知:

Re-write the risk quantity formula to clamp the amount between minimum trade and the equity (multiplied by the leverage)
Add the option for different leverage factors for long and short trades

發布通知:

This script development has gone far beyond my expectations and from a combination of trailing take profit and stop loss, had became a template for new strategies to develop. New interesting feature requests was implemented. However, I decided to create a separate script that will work as a template for new strategies and that can be found () with even more features! The features that are irrelevant from the initial purpose of this script were removed to minimize the clutter. At this point I want to thank all those people in the community that helped this to become a robust implementation by reporting several bugs to me after an extensive testing and thoroughly checking edge cases in different market conditions!

發布通知: