# Afk Presets
{% hint style="info" %}
AFK Presets allow you to set the default configurations used when running an AFK Mode task.
***
The guide below refers to BSC. The same logic applies to all supported blockchains, although buttons and available features may vary.
{% endhint %}
***
{% stepper %}
{% step %}
Select the desired blockchain
{% endstep %}
{% step %}
Tap π§ Presets
{% endstep %}
{% step %}
Tap π€ AFK Presets
| Button | Action |
| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Max Buy Count | Set the maximum number of coins the bot will purchase according to your current configuration. |
| Buy | Choose the BNB amount to buy. |
| Gas | Set the transaction gas (Max Priority Fee) for buying.
Max Fee is automatically calculated using the formula: Base Fee + (Priority Fee Γ 2).
|
| Slippage | Set the buy slippage percentage. |
| Buy Tip | Set the tip to increase transaction priority and help your trade execute faster.
Ethereum: We suggest to set a minimum of 0.001 ETH.
|
| Mev Protect | When MEV Protect is enabled, your transactions will be processed through BloXroute to prevent getting MEVed. If disabled, transactions will be routed through the custom node. |
| Limit Orders | Refer to the dedicated guide. |
| Blacklist | Blacklist setup:
- Words: set specific words contained in the token name to make the AFK task skip those tokens. You can also perform a mass import to add multiple words at once.
- Deployers: add deployer addresses you want the AFK task to ignore when creating buy tasks. A mass import option is available here as well.
|
| {% endstep %} | |
| {% endstepper %} | |
***
### Auto Orders
{% hint style="info" %}
Auto orders are limit orders automatically created after you buy a coin. They trigger based on your settings and donβt require you to start them manually once created.
After creation, the task will automatically start post-buy. Make sure to delete it if you don't want it to run.
{% endhint %}
{% stepper %}
{% step %}
Click π Limit Orders
{% endstep %}
{% step %}
Click π Create Limit Order
| Button | Action |
| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Dev Sell | Choose whether to automatically sell the specified amount if the Dev sells any of their tokens. If enabled, the bot will ignore the set profit/loss percentage and only trigger a sale when the Dev sells. |
| Time | Choose whether to buy after a specified timeframe. Bloom will execute the transaction after the timeframe you specify. |
| Sell Amount | Set the % you would like to sell. |
| Profit/Loss | Set take profit or stop loss.
β’ π Take Profit: Use positive values (e.g., +100% for 2x)
β’ π Stop Loss: Use negative values (e.g., -50% for half)
|
| Gas | Set the transaction gas (Max Priority Fee) for selling.
Max Fee is automatically calculated using the formula: Base Fee + (Priority Fee Γ 2).
|
| Slippage | Set the buy slippage percentage. |
| Create Order | Tap to create the order. |
| Delete Order | Deletes the target order.
|
| {% endstep %} | |
| {% endstepper %} | |
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.bloombot.app/evm/evm-bot/settings/presets/afk-presets.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
