📌Pricing can be found here (.pdf file)

⚠️ Starts from 03/13/2025 the only safe use cases for the bot are to run the game in a cloud service such as GeForce NOW or to run the Eye Auras on a second computer (or inside a virtual machine) and transmit the image via Parsec. You can learn more here in DC

ChangeLog.

📌03/12/2025 rev28 - Added a temporary solution that forcibly disables price checking on the purchase page. The main reason for adding it is incorrect readings of values that are difficult to fix. I am already working on a unified ML model that will almost completely remove this problem. For this purpose, a new variable purchaseBypass has been added, the default value of which is False. In case you notice that the bot can't buy the item due to incorrect reading, you can set the value to True and then the check on the purchase page will be skipped.

This is a temporary solution that will be removed in the future.

👁️‍03/10/2025 rev27 - added version with pre-compiled scripts. EA alpha 1.6.8106.0 required.

👁️‍02/15/2025 rev23:

• For convenience, I will refer to the main part of the bot (sniping up to 7 items at a time) as "main logic" and trait sniping as "trait logic".
• Redo all the scripts in main logic sections. Fixed mistakes and a bit of optimization.
• Added new option "trait logic". Now you can set you preferred trait in filter: such as rareness, type of the trait (weapon\armor\accessory) and needed trait (attack speed\heavy attack chance etc.). I will describe how to use this in the section 📍Installation and how to use the bot.

VIDEO EXAMPLE OF WORK REV19

📞Contacts:

- Official Discord of EyeAuras

- Main thread in Discord of EyeAuras

- My Discord and Telegram: iemn02

- elitepvpers forum thread

- ownedcore forum thread

📍Installation and how to use the bot.

⚙️Game settings:

- Scale and layout of you display in Windows should be strictly 100% regardless of your screen resolution.

- 1920x1080 (windowed) (the bot is configured in such a way that theoretically it is possible to use functionality using Parsec or GeForce NOW. If you have a positive experience, write to me on discord)

- TIER 1 UI size in: Settings > UI > HUD UI Size.

- Brightness ~0.58.

- Defensive ability must be set to Q (if it was changed).

- There should be no active overlays that can block the game window. For example, from Nvidia.

- Your T&L window must be active before launching the bot and during operation.

Default buttons:

• Q for your defensive skill.
• F11 - To set the required variables (you need to hold down the key and wait for the message in the console).
• F12 - Starting and stopping the bot. (Your start page for starting should ALWAYS be the favorites tab on an open auction).

1. On this page - at the top right, click on the Download portable pack button.

2. Move the contents of the archive to any location on your pc convenient for you.

3. Launch the game and then launch EyeAuras. After launch, you will see a hierarchy like this (may differ when new features are added).

4. Each time you start the EyeAuras you have to press and hold F11 until you see a notification in the console while the EyeAuras window is inactive. You must wait until the script completes and list of new variables will appear in the root bot folder in the specified folder Variables

5. Next you must specify values ​​for the new variables.

• First you need to choose what logic you want to use: main logic or trait logic. main logic is enabled by default (True) and trait logic is disabled (False). By changing these variables you switch logics. The variables setPrice1Line and setMaxLucToSpend are responsible for price limits in the trail logic section. (A little more detail on the variables below)

• setPrice1-7Line - This is your target price. Anything that is equal to it and below the bot will buy or try to do so.

• setMaxLucToSpend - This is the upper price threshold for one purchase. That is, the bot will not be able to buy anything that exceeds this value. (Also, this value cannot be greater than your current quantity of LUC.)

• Both of this values must always be specified as an integer such as 1, 10, 100, 1000, 10000, etc. The bot is set up in such a way that all fractional parts of prices, for example 3.111 or 3.999 will always be rounded up, i.e. to 4. So take this into account.

For example, you specified setPrice1-7Line as 10. The bot will buy or try to do so when a price appears in the range of 0.0001-10.

For example, you specified setMaxLucToSpend as 100. The bot will buy or try to do so when a price appears in the range of 0.0001-100.

• isLine1-7Enabled - new variable type that defaults to True. This variable is responsible for the performance of the lines. If for some reason you need to exclude a specific line, then simply replace True with False.

• main logic - by default (True). This variable is responsible for the operation of the main logic of the program. (sniping up to 7 items in the favorites tab).

• trait logic - by default (False). This variable is responsible for the operation of the trait logic of the program. (sniping one of the cheapest traits).

6. Press F12 to turn bot ON

7. More about how to set up trait logic part.

Starts from rev23 the bot trait logic works in a simple and limited form.

Since the game can have the same trait for different types of equipment, I made a simple and "cut" version of sniping. The bot refreshes the page with selected traits by clicking the "all" button. Because of this, you can't (for now i hope) select a specific type for weapons, armor, and accessories. But you can either track the cheapest option (minimum 10 lucent). Below is a visual example.

• 1. Select "find trait".
• 2. Select equipment type.
• 3. Select your trait in a list.
• 4. Don't forget to specify the rarity of your trait. Otherwise the bot will buy traits of ANY rarity.

I also wanted to clarify that in the current version (starting from rev17 and above) the main logic part of the bot checks prices from top to bottom (from 1 to 7). And if there is a case when an item under the number 1 and 3 meets your criteria, then depending on the current stage of checking, the bot will first buy the item under number 1 and only then under number 3.

Also, since the bot "reads" information from the screen, I physically could not check all the combinations. Therefore, incorrect readings of numbers are possible (usually this can happen with a single digit, for example 3 or 5). I work as hard as possible to find the "golden mean", but you need to understand that errors will still occur.

💸HAPPY HUNTING!💸