Добавлено лицензионное соглашение

Чтобы учесть юридические аспекты, я включил обязательное лицензионное соглашение. В этом соглашении указано, что пользователь несет единоличную ответственность за соблюдение лицензионных соглашений любых приложений, которые они автоматизируют.

Как многие из вас знают, игры часто явно указывают, что автоматизация действий любым способом запрещена и может привести к бану. Пожалуйста, имейте это в виду.

Улучшения техники активации окна

Для эффективной работы EyeAuras окно, получающее ввод, обычно должно быть активным. Если это не так, у EyeAuras есть некоторые методы, чтобы автоматически вывести его на передний план.

На первый взгляд, это кажется простым вызовом API в одну строку. Однако из-за различных особенностей Windows это не так просто. В результате я реализовал несколько механизмов для увеличения вероятности успеха.

В этом релизе я ввел дополнительный код для улучшения производительности, особенно в крайних случаях и для приложений, устойчивых к автоматической активации.

Вкратце, если у вас возникают проблемы с активацией окна (например, окно не активируется, когда вы отправляете ввод), пожалуйста, свяжитесь со мной, так как в этой версии были сделаны корректировки.

YooKassa (бывшая YandexKassa) вернулась

Это может быть интересно для пользователей из РУ/СНГ - YooKassa теперь снова доступна и вы снова можете оплачивать картами.

ИСПРАВЛЕНИЕ ОШИБОК

• Исправлена проблема с тем, что якоря Conent/Position не сохранялись

Actions can now be enabled or disabled

You can now temporarily disable any action in an Aura by clicking the checkbox next to its name. This is useful for debugging, and it is also available through the scripting system, so you can switch which actions will run based on options the user selected in your Custom UI, config file, and so on.

Another batch of anchor system changes

In 5397, I already made some changes to how anchors work across different EyeAuras screens, but that was not enough to cover some cases, such as clicking the center of an image found with Image Search.

So now we have two different anchor types: Position and Content. This should make the system more flexible, although it may also introduce a bit of confusion.

Here is the main rule:

• If you want to calculate the coordinates of a point, meaning X and Y, in most cases you should use the Content anchor. Clicking the center of an image found with Image Search via SendInput is the best example here.
• If you want to position one rectangle relative to another rectangle, meaning X, Y, Width, and Height, you should look at the Position anchor. This is useful when you want to create a kind of "panel" — for example, placing several overlays that show cooldown timers next to each other. By using anchors, you can avoid specifying the coordinates of each overlay manually and use Bindings to move the whole panel as a single overlay.

More details and examples are available at https://wiki.eyeauras.net/en/coordinate-system

Bugfixes / Improvements

• Fixed an issue where Public Auras became Unpublished after a package update in the Aura Library
• The Aura Variables panel should now be visible again; it was accidentally hidden on the main screen
• Fixed an issue with Bindings in SendInput — they had been temporarily disabled some time ago, and now they are back. This means the key combination can once again be configured through config/script.
• Fixed an issue with invalid coordinates defined in Send Input when an Aura was Bound
• Improved C# Script compilation speed

Main focus

In June, the main focus was on improving scripting. Most of the results of this work will become available in August — behavior trees, pathfinding, and visualization.

I’m also actively working on a Diablo 4-related project that will bring together most of the current EyeAuras functionality to demonstrate what it is already capable of. Because of that, most of the systems I implement for that bot will also be released to all users as soon as their API is stable.

I’ll publish a detailed post once those features are ready for public use. If you’d like to try some of them earlier, feel free to contact me directly.

Wiki updates

A lot has changed in the Wiki: https://wiki.eyeauras.net/en/home

• Added documentation for almost all action, trigger, and overlay types available in the app
• Added documentation for the Coordinate System, which is used in some actions and triggers to define capture areas, clone areas, or click coordinates: https://wiki.eyeauras.net/en/coordinate-system
• Added documentation for Text Match Expressions, which are used to evaluate recognized text or incoming network/Telegram messages: https://wiki.eyeauras.net/en/text-match-expressions
• Added documentation for Window Matching Expressions, which are used to specify which window should be selected as the target window: https://wiki.eyeauras.net/en/window-matching-expressions
• Take a look at the Dependencies Viewer, which is often overlooked but makes debugging complex aura setups much easier: https://wiki.eyeauras.net/en/overlays/dependencies-viewer
• Added some technical information about Custom UI: https://wiki.eyeauras.net/en/overlays/custom-ui
• Bindings: an extremely powerful mechanism that lets you connect trigger and action properties together — Bindings | EyeAuras Wiki
  • for example, you can find an inventory using Image Search and bind the detected area as the source region for another Image Search, which will then search only inside the inventory area
  • you can also bind overlay coordinates to Image/Text/Color Search and link the overlay lock state to HotkeyIsActive, allowing the user to quickly change the capture area by pressing a hotkey and dragging the overlay somewhere on the screen
• Sync: a mechanism that makes it easier to share an aura set that you are actively working on

Anchor system improvements IMPORTANT CHANGE

Anchors are the coordinate system used anywhere you need to select an area — screen regions, image regions, and so on.

The idea is simple: by choosing different reference points, you can easily align capture or output areas relative to one another.

More details and examples are available here: https://wiki.eyeauras.net/en/coordinate-system

Input redirection improvements

This is a fairly niche feature available in the settings that lets you redirect all user input through a specific simulator.

• You can now quickly enable or disable redirection from the main window, as long as a redirection simulator is configured in settings

ML Search improvements

• In the Effects window, you can now configure automatic screenshot capture/recording, which is very helpful when collecting a training dataset

• Performance improvements, especially noticeable in CPU mode
• Fixed a crash related to loading an incompatible or broken model
• Fixed a memory leak that occurred in Segmentation mode
• Improvements to Segmentation and masks — a new "Group masks by class" mode has been added, allowing all masks of the same class to be merged into one, which makes them much easier to process
  • for example, if the neural network detects 6 different regions labeled as "Road", enabling "group by class" will merge all binary masks into a single "Road", along with their bounding boxes
  • Segmentation is the process of capturing not only object bounding boxes, but also their precise shape

Bug fixes and improvements

• Improved mouse capture — lower latency
• Added status display
• The 'New Clone' button has been removed. To create a clone now, go to: New Aura -> Overlays -> Clone and specify the area to capture/replicate
• Startup speed optimizations
• Drag'n'Drop should now feel more responsive
• Fixed an AuraTree issue that caused sudden jumps while scrolling or selecting items

Main Feature: Enhanced Scripting with Visual Studio/Rider Compatibility

Two months ago, I introduced a major new feature: the CustomUI overlay. It gave developers the freedom to build custom interfaces using the dynamic duo of C# and Razor, greatly expanding the possibilities for bot/aura customization. It also made navigating the EyeAuras interface more user-friendly.

That said, I realized there was still room for improvement. Developers are used to the power of integrated development environments (IDEs) such as Visual Studio and Rider, but until now those tools could not be fully utilized in the EyeAuras workflow. To change that, I improved the CustomUI overlay so your code can now be exported and saved as a C# project.

The exported project, including EyeAuras.SDK, can be opened in any IDE and gives you access to full autocomplete, unit testing capabilities, and much more. Keep in mind, however, that you still need EyeAuras to actually run the code. I am also working on support for connecting external NuGet packages, which will be the main focus in July.

Another highlight is the new Live Development mode, which lets you push changes into EyeAuras in real time. Whether you are tweaking styles or adding new bot logic, your changes can be reflected within seconds. The potential here is huge, especially with access to triggers, captured images, input simulators, and more.

Please note that actions and triggers currently still run on the old scripting engine, but I am working on migrating them to the new scripting engine while preserving backward compatibility.

Color Search Trigger: Mathematical Similarity Calculation Method

In addition to the previous improvements, I added a new similarity calculation method based on Euclidean distance to the color search trigger. You can read more about it on the EyeAuras Wiki.

Bug Fixes and Improvements

• [Overlays] Performance has been improved by using separate CPU cores, which makes the UI more responsive.
• [Bug Fix] Fixed an issue that caused a crash when switching between auras while the editor was still in the loading phase.
• [Bug Fix] Resolved intermittent crashes in Window Selector, the component used to choose the target window.
• [Bug Fix] Fixed an inconsistency in Window Selector where the matching window was not always selected automatically.
• [Bug Fix] All dialog windows were optimized to open faster and no longer display visual artifacts.
• [Image/Color/Text Search] [Bug Fix] Fixed an issue where capturing unresponsive windows could cause the application to freeze.
• [Image/Color/Text Search] [Bug Fix] Removed a UI limitation that prevented selecting 0 FPS. This fix is especially useful for script-driven scenarios.

• [Denoise Effect] Should be more effective now in, well, removing noise
• [Effects Editor] UI changes - added Copy/Paste/Clear, made some performance optimizations
• [Bugfix] Fixed region selection when there were scaling image effects applied (Resize, Rescale)
• [Bugfix] [ImageSearchTrigger] “Save image to file” was not working correctly - it was saving Preview rather than the current image
• [Bugfix] *[Search] Window borders were not always correctly calculated causing image cropping
• [Bugfix] [SendSequence] Fixed crash that occurred when “Show notification” was enabled
• [Bugfix] [SendSequence] “Show notification” should not correctly show current sequence execution progress

• [Bugfix] Removed “Add to blacklist” button in Window Selector which is just a leftover of a functionality that was removed ages ago
• [Rescale Image Effect] Image can now be scaled by both axes - X and Y which will be useful for gathering a data set for machine-learning purposes

• [Color Replacement Effect] Changed how Matching/NonMatching colors are saved into config - now their values are preserved even if actual replacement is disabled

• Bugfix - shortcut to EyeAuras.exe was not created on fresh install / application was not restarting correctly after update
• Bugfix - login operation was working correctly under some conditions

• [Image/Color/Text/ML Search] Added new preview mode - "without Effects" which temporarily disables all effects applied to an image and allows to more precisely select region
• [Color Replacement Effect] Bugfix - selected colors were not correctly saved to a config

• [Image/Color/Text/ML search] Fixed a bug in region selector - selected area was not scaled correctly