Config by Rugger

The configuration page of a rugger is the nerve center of the bot. This is where you control everything related to a specific address.

Access the config

From 🎯 Ruggers, tap any rugger in the list to open its config.

What you see

At the top of the page, a compact summary displays the key settings:

• Buy — The configured buy amount
• Mode — The active tracking mode
• TP — The first Take Profit level
• SL — The first Stop Loss level

Available actions

Auto-Buy and Auto-Sell

These two toggles are independent per rugger. You can have a rugger with Auto-Buy enabled and Auto-Sell disabled — in that case, the bot will buy automatically but will not sell.

💡 Tip : Disable Auto-Sell if you prefer to manage your sales manually or if you want to observe a rugger’s behavior before trusting it.

🛑 Auto-Buy Protection

This feature protects your wallet against consecutive losses while you’re away (at night, for example).

How it works: The bot counts losing sales. When the counter reaches the threshold you set, the bot pauses auto-buy. The bot displays PAUSED, new buys are blocked, but your open positions are not affected — you then reactivate it manually.

The counter tracks the whole chain, not each address separately. When Rugger Protection adds child addresses, losses are counted on the root rugger (the parent), not child by child. If the total reaches the max, auto-buy pauses for the entire chain until reactivation. A single win on any child resets the root counter to zero.

Configuration:

• Default threshold: 10
• Configurable from 1 to 20

Example: You are asleep. Your rugger “DevSniper” has several tracked child addresses. Together, they rack up 10 losing sales in a row. The bot pauses auto-buy across the entire “DevSniper” chain. The next morning, you see PAUSED, check what happened, and decide whether to reactivate it or not.

💡 Tip : Set a low threshold (3-5) if you’re sniping a new rugger you don’t know yet. Raise it to 10-15 for a trusted rugger that may occasionally have streaks of bad tokens.

🔗 Settings Inheritance

This toggle controls what happens when the Rugger Protection detects a transfer and adds a new address (child address) to monitoring.

• Inheritance ON (default) — The child address inherits the parent’s settings (the rugger that made the transfer)
• Inheritance OFF — The child address receives your own custom settings instead of inheriting from the parent

Why disable inheritance? If your parent rugger has Keep Address ON in Rugger Protection, every transfer adds a new address WITHOUT removing the old one. If inheritance is enabled, every child address will also have Keep Address ON, which creates a chain reaction that can fill your 30 slots in a few minutes.

By disabling inheritance, child addresses receive “clean” settings — you stay in control.

⚙️ Child Address Defaults — your settings for children

When inheritance is OFF, child addresses receive the values defined in Child Address Defaults (accessible from the Protection menu). There you control:

• Keep Address and Fresh Wallet — child Protection rules
• Protection ON/OFF and its Mode
• Auto-Buy and Auto-Sell
• 🧹 Remove if no launch — the probation period specific to child addresses
• Transfer Ranges

Since Remove if no launch is also set here, a parent address and its children can have probation periods different — for example, 24h on the parent you know, 2h on the children being tested.

💡 Anti-cascade tip : set Keep Address OFF and Protection OFF in Child Address Defaults — child addresses are sniped once, then removed. Combined with a short Remove if no launch, your list always stays clean.

⚠️ Important : If you use Keep Address ON, remember to disable inheritance to avoid filling all your slots automatically.