# Configuration

<figure><img src="/files/rfRlQJ1w4G9MXpS7Ux9i" alt="" width="563"><figcaption></figcaption></figure>

1. Wallet selection
2. Amount you wish to allocate to each buy
3. Amount available in the wallet
4. Enable/disable Auto Take Profit. If this function is enabled, after buying a token, Shotgun will automatically create a sell order with the profit you have specified.
5. Score selection. The score you choose is directly related to the risk you wish to take when activating shotgun. The lower the score, the more the token meets the requirements of a safe token; conversely, the higher the score, the higher the probability of it being a scam. In short, the most perfect score is 0, the worst score is 115.
6. The percentage of profit you're targeting. The lower the percentage, the more likely you are to succeed.
7. The percentage of token you wish to sell when executing the Take Profit order
8. Buy Slippage. On SOLANA, the slippage required for proper order execution is quite high. According to our tests, a slippage of 30 is ideal, especially when tokens have a high transaction volume. (Slippage is not a tax and has no impact on the quantity of tokens you get.)
9. Protection against MEV bots. If you activate this function, you'll be protected from MEVs, but your transaction will be slowed down. It's also unlikely that you'll be a sandwich victim, as buying takes place very soon after the token is launched.
10. The duration of Shotgun's running time
11. START HUNTING button


---

# 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://unodex.gitbook.io/docs/shotgun/configuration.md?ask=<question>
```

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.