Improve documentation
This commit is contained in:
parent
9d5961e224
commit
676dd0d664
@ -78,6 +78,7 @@ At this stage the bot contains the following stoploss support modes:
|
|||||||
2. Trailing stop loss.
|
2. Trailing stop loss.
|
||||||
3. Trailing stop loss, custom positive loss.
|
3. Trailing stop loss, custom positive loss.
|
||||||
4. Trailing stop loss only once the trade has reached a certain offset.
|
4. Trailing stop loss only once the trade has reached a certain offset.
|
||||||
|
5. [Custom stoploss function](strategy-advanced.md#custom-stoploss)
|
||||||
|
|
||||||
### Static Stop Loss
|
### Static Stop Loss
|
||||||
|
|
||||||
|
@ -29,6 +29,8 @@ E.g. `current_profit = 0.05` (5% profit) - stoploss returns `0.02` - then you "l
|
|||||||
return 0.04
|
return 0.04
|
||||||
```
|
```
|
||||||
|
|
||||||
|
Stoploss on exchange works similar to trailing_stop, and the stoploss on exchange is updated as configured in `stoploss_on_exchange_interval` ([More details about stoploss on exchange](stoploss.md#stop-loss-on-exchange-freqtrade)).
|
||||||
|
|
||||||
!!! Note "Use of dates"
|
!!! Note "Use of dates"
|
||||||
All time-based calculations should be done based on `current_time` - using `datetime.now()` or `datetime.utcnow()` is discouraged, as this will break backtesting support.
|
All time-based calculations should be done based on `current_time` - using `datetime.now()` or `datetime.utcnow()` is discouraged, as this will break backtesting support.
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user