# Afk Presets {% hint style="info" %} AFK Presets allow you to set the default configurations used when running an AFK Mode task. {% endhint %} *** {% stepper %} {% step %} Tap `💤 AFK Presets` from the Presets menu.

Button	Action
Platforms	Choose the platform to activate the AFK task on. After selection, set up the task, and AFK Mode will be enabled on all chosen platforms.
Max Buy Count	Set the maximum number of coins the bot will purchase according to your current configuration.
Buy	Choose the SOL amount to buy.
Fee	Set the transaction fee for buying.
Slippage	Set the buy slippage percentage.
Buy Protection	Toggle MEV protection (enabled/disabled) to prevent your transaction from being sandwiched. The fastest processor is automatically used.
Buy Tip	Set the target buy tip fee to prioritize the inclusion of your transaction in the next block.
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. 🟢: When enabled, Bloom will ignore the set profit/loss percentage and only trigger a sale when the Dev sells.
Time	Sell after a desired timespan. Enter the expiry time in: • 1H = 1 hour • 30M = 30 minutes • 1D = 1 day • 60 = 60 seconds
Trailing	A Trailing Stop Loss moves automatically as the token price increases. The Trailing Value (%) represents the distance between the current price and where the stop loss is set. As the token price rises, the stop loss moves up with it, always maintaining that distance. If the price drops enough to hit the trailing level, the order triggers and closes the position automatically.
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)
Fixed Mcap	Set the target market cap at which you’d like Bloom to sell.
Mcap Variation	Set the market cap increase or decrease threshold at which you’d like Bloom to sell. Bloom will execute the sale only when the market cap change matches your specified value.
Sell at	This button adapts based on your selected selling method (Profit/Loss %, Fixed MCap, MCap Variation), allowing you to set your preferred value accordingly.
Sell Amount	Set the target amount to sell as a percentage.
Slippage	Set the slippage percentage.
Sell Protection	Toggle MEV protection (enabled/disabled) to prevent your transaction from being sandwiched. The fastest processor is automatically used.
High Impact (Expert only)	Enables trades that require higher price impact than usual. Use this if you’re buying large amounts of SOL in low-liquidity pools. ⚠️ Expert users only: using this when it’s not needed can route the sale through suboptimal pools or cause bad slippage.
Tip	Set the buy tip fee to prioritize the inclusion of your transaction in the next block.
Fee	Set the transaction fee for selling.

{% 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/solana/solana-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.