• Sell Bot
• MeltGems
• MeltItems
• SwapCape
• Revive Bot
• AutoPotion
• AutoClicker
• Fully Configurable: All positions, delays, timings, and offsets can be customized.
• Config Save/Load: Your setups are saved for convenience.

1. Set First Cell

   • Click the "Set First Cell" button in the menu.
   • Select the top-left square of your inventory.
   • This defines the starting point for the grid.

2. Inventory Grid

   • Click the "Inventory Grid" button.
   • Drag over your entire inventory area, starting from the top-left cell to the bottom-left cell.
   • This defines the boundaries of your inventory slots.

3. Set Bag

   • Click the "Set Bag" button.
   • Select the first bag in your inventory.

1. Set Close Button
   • Click the "Set Close Button" option.
   • Select the Close button located in the top-right corner of your inventory.

1. Set Melt Button(s)
   • Select the buttons responsible for melting gems/items.
   • Adjust any timing or delays in the configuration if needed.

✅ automatically melt gems and items.

1. Save Pos
   • Click the "Save Pos" button.
   • Create a group and select the first player on the right side of your screen.

• AutoPotion: Automatically consumes potions when health drops below configured thresholds.
• AutoClicker: Automates repeated clicks for fast actions in-game.

• Make sure all selections (cells, buttons, etc.) are made precisely to avoid misalignment.
• Always test the setup once before using the bots in live conditions.
• Adjust window scaling or UI size if detection is off.
• All delays, timings, offsets, and positions can be configured via the settings panel.

This project is for personal or educational use. Redistribution or commercial use without permission is not allowed.

If you encounter a problem or bug while using any of the bots, please follow these instructions when creating a GitHub Issue:

1. Open a new issue in this repository.
2. Include the applog.txt file generated by the application.
   • This file contains detailed logs that help us understand what went wrong.
3. Describe the bug clearly, including steps to reproduce it.
4. Provide screenshots if possible.

Important: Issues without the applog.txt may be harder to troubleshoot and could be closed.