New Release — 1.7 (RU/EN)

A lot of work went into making Behavior Trees and the entire scripting system more flexible. We can now finally build bots using only Macros and Behavior Trees, without needing to rely on Auras.

Combining two complex systems (Auras and BT) made the logic harder to follow, so the new nodes should make things much clearer. And this is not the end of it — more changes are coming soon, especially around preview-related functionality.

Screen Capture — BREAKING CHANGE

For many years, all Capture triggers (Image/Color/Text/ML) required the Target Window parameter — EyeAuras worked only with windows.

Starting with this version, we are trying a different approach:

• If Target Window is not specified, EA will capture the primary screen.

What does this mean in practice?

• Previously, clearing the Target Window field would effectively stop those triggers from working. Now it simply switches them to primary screen capture mode. I strongly recommend using Enabling Conditions to control capture. This is important! Check your old triggers to make sure there are no "test" or "forgotten" ones — they will start consuming CPU.
• One less setup step if you are configuring something for personal use: in many games running in Borderless Windowed mode, or similar fullscreen-like modes, specifying Target Window is no longer required.
• Once the window dependency is removed, working with mouse coordinates becomes simpler — every coordinate becomes absolute.
• Anything related to clicking objects on the screen should continue to work as before. If you notice any issues, please report them.

IMPORTANT! Multi-monitor setups are not supported yet. Only the primary screen is captured. Support will be expanded in the future.

Behavior Trees & Macros Improvements

• Major Macros changes: macro flexibility has been significantly expanded.
• New CV-based nodes: computer vision nodes that act as trigger equivalents. For simple bots, triggers are no longer required!
  • MLSearch together with MLFindClass — works with ML models and lets you filter ML search results. Combined with MouseMove improvements, you can build a point-and-click bot in minutes.
  • PixelSearch — finds a pixel of the specified color.
  • ImageSearch — finds an image.
  • ColorCheck — checks whether the color of a pixel/area matches the expected value.
• New logic nodes: let you control execution flow.
  • Interrupter — conditionally interrupts nodes that are already running.
  • Timeout — sets the maximum time a child node may remain in the Running state.
  • CheckKeyState — checks the current state of the specified key.
  • IfThenElse — if..then..else as a BT node, useful for users who are just getting familiar with BTs.
• Undo/redo in BT: you can now undo/redo node additions and deletions with Ctrl+Z / Ctrl+Y.
• Hotkey activation: BTs and Macros can now be started directly with hotkeys.
• Login Widget: a simple widget that can be used in mini-apps for EyeAuras-based authentication.
• PopOut View: a read-only popup window for BT/Macro testing and debugging.
• BT variable support: nodes like MouseMove can now use CvLastFoundRegion from CV searches.

C# Scripting System

• Precompilation and script persistence: scripts are compiled ahead of time, reducing runtime delays. Compiled binaries can be stored to avoid recompilation after restart.
• API File Provider: scripts can inject and load additional files (.css, .js, .md, .dll) via IScriptFileProvider.
• NuGet package support: packs automatically fetch and package required NuGet dependencies for a better offline and startup experience.
• Keybind attributes: scripts can bind methods to hotkeys via [Keybind].
• Dependency Injection improvements: cleaner script structure thanks to [Dependency] or init properties for services such as SendInput.

Trigger Improvements

• Lifecycle Events Trigger: added triggers such as AppStarted, making it possible to automate processes without showing the EA UI.
• ML Search: some basic models can now be downloaded directly from the UI. In the future, the same system will be used to distribute "standard" models such as HP bar detection.

Packaging and Distribution

• Script protection (ShadowForge): closed alpha version of obfuscation and IP protection for distributed scripts.
• Pack compilation modes: scripts only, scripts + binary, or binary only (with obfuscation).
• Pack distribution policy: packaged-only distribution can now be enforced to simplify onboarding.
• Feature exclusion for packs: ability to disable CV or Input for lightweight builds.
• Start Minimized & Minimize to Tray: new packaging options for standalone applications.

Computer Vision API (Experimental)

A programmable interface for Image Search, Pixel Search, ML Detection, and Text OCR with OSD overlay support. More details here.

Authentication and Licensing

• Semi-offline mode: the first steps toward fully offline use of the application.
• KeyLogin: sign in with license keys — no account required.
• Sublicensing: tiered access to paid packs and features.

Performance and Optimizations

• Cold start optimization: startup time reduced by up to 15%.
• Modular feature loading: RAM and CPU usage optimized by excluding CV/Input where they are not needed.

Fixes / Improvements

• [Crash] Fixed a BT crash introduced by recent changes (Already cancelled).
• [Crash] Fixed an import crash that occurred if the clipboard contained a link to an unsupported file.
• [BT] Added a new button that lets you run a BT/node "until you stop it."
• [BT] Fixed a bug where it was possible to delete a node by connecting its output to its own input...
• [BT] Fixed a bug that caused many error messages when deleting nodes in bulk.
• [BT] Fixed an issue where the Debounce node did not save its properties.
• [BT] Improved the UX of node deletion.
• [BTs] Macros now stop correctly when the main application window is activated.
• [Capture] Fixed the FPS selector — it behaved incorrectly and showed a Range selector even without a Min value.
• [Capture] Fixed region selection in the Preview window when Resize/Rescale effects were applied.
• [ColorSearch] Minor optimization — lower memory usage and about 2–3% faster.
• [Macros] Improved drag-and-drop responsiveness in the tree.
• [Macros] The Comment node no longer throws an exception during execution — which completely defeated its purpose.
• [OSD] Fixed incorrect OSD rectangle color layout — the R and G channels were swapped.
• [Scripting] IBlazorWindow now has a new TitleBarViewType property, allowing complete replacement of the window title bar.
• [Scripting] Added a Clear() method to MiniProfiler.
• [Scripting] Added the WorldToWindow matrix to WindowImageProcessedEventArgs, making window coordinate calculations after Refresh() easier.
• [Scripting] Added implicit conversion from string to WindowMatchExpression.
• [Scripting] Added a Percentage struct for percentage values (for example, 0.1 = 10 %).
• [Scripting] All OSD objects now have Opacity.
• [Scripting] Error line numbers are now highlighted/displayed correctly for compilation errors.
• [Scripting] (Apparently) fixed an issue where LoginWidget could behave incorrectly.
• [Scripting] Slightly improved first-run script performance (3–5%).
• [Scripting] Fixed an issue in auras that could prevent a script from executing if the aura was disabled too quickly.
• [Scripting] Slightly optimized memory usage (AuraScript utilization).
• [Scripting] The SendInput API has been moved from SendInputUnstableScriptingApi to SendInputScriptingApi — it has not changed in a year and is stable enough now.
• [SendInput] Fixed an issue where interleaving Delays/SendInputs could block each other (a bug from the latest version).
• [SendSequence] Fixed an issue where key press sequences could stop too early, so only part of the sequence was sent. Thanks to @Rowenor for catching it!
• [SendText] Fixed incorrect size of the text input field.
• [TextSearch] Fixed a bug where the IncludeTextSegments parameter was not saved in config.
• [UI] Added a Move To Parent option in the aura tree.
• [UI] Fixed a crash when setting an invalid aura name.
• [UI] Fixed a serious authentication issue — in some cases even pack authors could not publish an update (Non-authorized users are not allowed to update shares).
• [UI] Fixed an application manifest issue that required a restart to obtain administrator rights (still needs testing on different OS versions).
• [UI] Fixed selection offset in the fullscreen region selector.
• [UI] Fixed login sensitivity to the accuracy of the user's system clock.
• [UI] Fixed a package issue where closing the license agreement window caused the application to exit (first launch only).
• [UI] Fixed Overlays in precompiled packs.
• [UI] Fixed duplicated script messages in the Event Log.
• [UI] Fixed the Start Minimized option under certain conditions.
• [UI] Fixed CodeEditor alignment in the maximized window.
• [UI] Fixed a bug where import links from AuraLibrary might not work in some cases.
• [UI] Refactored the license agreement window — it should open faster now.
• [UI] Minor fixes for the PopOut functionality added in the previous release.
• [UI] Further improved semi-offline mode support — the token refresh algorithm has been refined.
• [UI] Using a dot (.) in aura names has historically caused many problems, because EA saves auras to disk using those names, and a dot usually separates a file name from its extension. EA will now show an error if you try to set a name containing a dot, just like it does for other invalid characters.
• [Web] Fixed links on the Aura Library page — the hostname was missing.

Behavior Trees - added Invert option to some of the nodes

The new option is available only in those nodes which work with image capture right now - pixel color checks, ML, image search, etc. It is very simple and semantically equivalent to Inverter node, but built in. The reason is BTs tend to grow very-very quickly and reducing overall amount of nodes should help keeping them structured.

p.s. I know these have been quiet few weeks, internally I am working on a new large feature, which will be available to public later this year. I'll keep you posted.

Bugfixes/Improvements

• [BT] Fixed a bug which lead to showing a bunch of errors whenever you've removed multiple nodes in a bulk

Performance improvements - please report any issues you may notice

Huge amount of work has been done on internals of the program, too many to list. All-in-all, such things tend to lead to a string of bugs, please, pay attention to any irregularities and report them, I will be closely monitoring the inbox.

Behavior Trees - implemented Undo(CTRL+Z)/Redo(CTRL+Y) support

Writing a script in ExecuteScript node and accidentally removing it is a pain. Been there, done that. This feature will allow you to easily rollback such changes on the spot. For now, Undo/Redo supports only nodes addition/removal, other nodes modifications will be added as soon as the mechanism will become stable enough.

Bugfixes/Improvements

• [BT] Fixed a bug in BTs where you could remove the node by linking its output to its input...
• [UI] Semi-Offline mode support improvements - improved token update algorithm, should make things smoother
• [Scripting] IBlazorWindow now has a new property TitleBarViewType` which allows to fully replace window title bar with whatever you want

Bugfixes/Improvements

• [BT] Fixed a problem with Debounce node not saving properties
• [Crash] Fixed Import-related crash which happenede when clipboard containted link to unsupported file
• [UI] Fixed a problem with full-screen region selector - selection was off a bit

Behavior Trees / Macros - Activation Conditions - Hotkeys

Previously, there was a single way to make Trees and Macros "tick" and "run" (correspondigly). If you wanted to make the tree run when/while some hotkey was pressed, you had to use a separate Aura with HotkeyIsActive trigger in it. In the new version you can just add that same hotkey in the Tree/Macro straight away, reducing number of operations and complexity of configuration drastically.

Interception conditions

In original HotkeyIsActive triggers, there is a functionality, which allows to restrict hotkeys to a specific window/application/etc.

This mechanism is directly responsible for enabling/disabling hotkeys handling at any given moment. By adding one or multiple auras you can specify exact set of conditions, which must be met before Trigger will start doing anything.

For example, by linking Aura which has WindowIsActive in it, you will make Trigger react only to keys which were pressed while game window is active.
In more complex cases, you can link the trigger to some in-game condition, for example, you when you click RMB(part of HotkeyIsActive configuration) AND some powerful skill is off-cooldown(linked condition), instead of casting whatever is usually on RMB, you'll simulate key press of a button which casts that skill. A good example would be automating cast of Vaal Skills on Path of Exile - you have the usual version of a skill bound to some button which you spam and whenever Vaal version got enough souls, it will be automatically release without you having to remember about it.

In BTs, the equivalent will be adding Enabling Condition on the tree itself - just like you did it before. The hotkey will be intercepted only if Enabling Condition is met. We'll see how that approach goes - please send your feedback.

New Node - Interrupter - MAJOR

Very important new node in BTs ecosystem - it allows to conditionally interrupt already running nodes. Usually, when some node is Running (like Wait or Until Success), there is no chance to other nodes in the tree to do anything - EyeAuras just waits for the node to complete its work. In contrast, Interrupter node, when executed, ALWAYS runs Condition(left) node, even if the Action(right) node is Running. Moreover, if Condition succeeds, instead of giving control to already Running Action, it will interrupt it from further activity. This could be used to break long-running actions (e.g. Wait) or make some loop(like Until Success) stop on demand - the node is emmensely powerful given right conditions.

New Node - Check Key State

Very simple node, which checks the current state of the specific key. If it is pressed, the node returns Success.

New Node - Timeout

Another node which is expected to be paired with long-running nodes such as Until Success - it allows you to put a maximum time which you "allow" the child node to Run. The first combination of nodes which comes to mind is something like this:

By combining Timeout -> Until Success -> Image Search you basically tell the tree Keep trying to find the image until you Succeed, but no longer than for 2 seconds.

Bugfixes/Improvements

• none this time

Performance - startup time improvements

Started to work on startup time improvements and, more specifically, "cold" (first) start.

Here are startup times for the latest pack for GTA5 by @linx - https://eyeauras.net/share/S202503032233289fPxqP4AA0N0 v8215 - 33.41s v8224 - 28.89s

So the new version is approximately 15% faster on the first launch.

Subsequent launches: v8215 - 29.38s v8224 - 27.10s ~8% faster.

I will keep working on improving those stats.

Bugfixes/Improvements

• none this time

Packs - added ability to disable modules from loading

Sometimes, you do not need ALL the functionality which is built into EyeAuras in your Packs. For example, if your pack does not use computer vision at all, it does not make much sense to load CV-related modules into the memory - this is waste of both CPU and RAM. With the new functionality around working with applications directly - such as reading memory - it is expected that there will be more and more cases where you just want to use EyeAuras as a platform for development and distribution own of your app.

This feature is intended to be used exactly for that purposes - you now can disable some parts of the application from loading. Those modules, which are blacklisted:

• will not ever be loaded into memory
• will not load any dependencies
• will not even be decrypted, meaning they could not even be scanned/flagged as they never leave encrypted blob of data they are distributed by default

For now, we have two types of modules which could be excluded:

• Computer Vision - All types of capture-related functionality (Image/Color/ML Searchers, etc)
• Input Simulation - Send Sequence/KeyPress/MouseMove and all other input-manipulation actions. p.s. Note that HotkeyIsActive is still available

How much does it save?

• Computer Vision - heavy-hitter, could save around 300MB of RAM and 3-5 seconds of startup time.
• Input Simulation - light-weight in comparison, but, more importantly, by not loading input-related libraries, you make the app appear more legit to all external observers. This could be very important if you decide to distribute your pack not as an automation tool, but as computer-vision-based helper.

How to set this up?

Blacklist is a part of Pack configuration. By default, everything is shipped, but you can disable two types of modules/

Bugfixes/Improvements

• none this time

KeyLogin

KeyLogin is a way to sign in using a one-time license key — no account creation required. This system is intended to be used along with Sublicenses to allow your users to access your cool Packs as quickly as humanly possible.

That is how the process looks right now

For end-user(the person who will be using the pack):

• purchase a key to your pack from a 3rd party website
• go to pack page, click on Download pack
• login via the key and start using the pack

That is it. I think this is as simple as it could get and we'll stay in that state for some time and see how it goes.

For you(author, who is creating the pack):

• you create something cool
• you export it and get URL (like this or this or other packs in Aura Library)
• add description, images, etc to the page
• add an aura which checks for the license - code is available for copy-paste
• enable Script Protection - this makes it much-much harder to counteract licensing mechanism
• contact me(Xab3r) in Discord and I generate keys for you
• you(user) distribute keys via FunPay or any other websites that allow to sell keys

Yeah... for authors the process is not as straightforward. I will streamline it this year.

RU version of the article here

Bugfixes/Improvements

• [UI] Fixed a problem with login being too sensitive for user clock precision

New Node - Color Check - Early prototype

Allows to check that the color of a specific pixel(or region) matches selected one. Probably one of the most useful nodes out there - fast, very easy to use and very flexible.

New Node - Image Search - Early prototype

Allows to find image somewhere on the screen/in a selected region.

New Node - IfThenElse

Added new node, which is intended to be used by those who are more comfortable with "classic" logic building.

Bugfixes/Improvements

• [BT] Improved nodes removal UX

New Node - MLSearch - prototype

New node in BTs and Macros, which allows you to run ML search over a region of a screen/window. It is still missing a lot of options currently present in MLSearchTrigger such as Configende/IoU thresholds, inference method, number of threads etc - those will be added in the nearest future.

Note, that by itself this node does not do anything - you have to pair it with other nodes such as MLFindClass or MouseMove to get anything from it. By default, it will pick the very first object and make it available for click via MouseMove - for some very simple scenarios that will be enough, for more complex one - use MLFindClass

The node will return Success only if there is at least one found prediction.

New Node - MLFindClass - prototype

This node must be used in pair with MLSearch and allows to pick some class(~object) from the output generated by MLSearch - you can set some filtering parameters such as class name(s), minimum confidence threshold, size restrictions, etc. Those predictions which do not match any of those, will be filtered out.

Out of those predictions which will be left after filtering, you can make the node pick exactly one of them - it could be the very first in the list or the one with the highest confidence or even the one that is currently closest to the cursor.

The node will return Success only if there is at least one found prediction that matches all the criteria.

Of course, both MLSearch and MLFindClass could be used in combination with all other nodes. Here is, for example, priority-based target selection

Bugfixes/Improvements

• [BT] Fixed a problem with zero-timeout BTs - they ticked only once