SendSequence changes

Added two new flags, which target the scenario when you want to play some long-long sequence of actions, but at the same time you want to make it possible that it could be interrupted at any given moment.

E.g. you have a sequence of skills, which are cast inside WhileActive block. Now you want to be able to interrupt it at any given moment (e.g. by toggling hotkey to "Off" state). Previously it was not possible to do so without using Behavior Trees or Macros. But now, with these two new options, it is just a couple of clicks

Can Be Interrupted

As stated in the name, it changes behavior of the action - if, for any reason, Aura gets deactivated, the action will be stopped, even if the sequence has not been completed yet.

But abruptly stopping sequences of inputs is not really a great idea most of the time - if, for example, action has pressed some button and NOT released it yet, if it will be interrupted, the button will stay pressed, probably breaking something.

That is where the second flag comes in handy:

Restore Keyboard State

This flag remembers keys, pressed by the sequence and will release them automatically at the end of the action. So even if the action was interrupted in the very middle, there will be no "stuck" keys.

Macros - Return/Break nodes

Adding two new nodes which should help to create better and smarter Macros!

Return

Return node allows you to exit the macro whenever you want to, even right in the middle of some sequence of operations. E.g. if character has died it does not make much sense to continue running the main loop. Equivalent of return operation in C#

Break

Break is more niche - it allows you to exit the current scope (not the macro!), e.g. if you're inside some Repeat loop, you can jump out of it if needed. Equivalent of break operation in C#

C# Scripting - DLL injection

For the last couple of months I've been working on internal improvements of EyeAuras.Memory namespace. The goal is to extend capabilities and to support DLL injection and hooking of external processes. For now, I am releasing only one bit of the entire set of improvements - LocalProcess now has InjectDll method which uses naive CreateRemoteThread based injection. This will not help with kernel anti-cheat protected projects. We're already testing kernel-driver based solution which allows to counteract that inconvenience - I'll keep you posted.

DLL injection brings a lot of interesting and powerful things to the table - the topic is very niche and technical, but in the next 6-12 months I'll be trying to make it accessible to anyone with some C# skills, without deep understanding of internals.

Wiki

C# Scripting - Blazor Windows

Added a series of articles in Russian/English about programming using EyeAuras Blazor Windows API

• Intro
• WebView
• Hello, World
• Creating a Toggle
• Making UI Interactive
• Adding multiple different controls
• Applying styles
• Inline CSS
• External CSS

Behavior Tree / Macro

Added a whole bunch of articles about Behavior Tree / Macro nodes. Note that most of these articles are available in both Russian and English.

• IsActive - checks whether parent Tree/Macro is currently Active
• Interrupter - (advanced) node, that allows to break execution of Behavior Tree if some condition is met
• Return - allows to stop the macro
• Break - allows to Break from the loop or code block
• MouseMove Abs - moves cursor somewhere on the screen (or to something)
• MouseMove Rel - moves cursor relatively to its current position
• CheckKeyState - checks whether some key is currently being held
• KeyPress - simulate keypresses
• Send Text - inputs text either via copy-pasting it or inputting each character individually

Bugfixes/Improvements

• [Crash] Fixed ColorSearch template-related crash (disposal race) #EA-1146 by @ganya
• [Crash] Fixed BT Node Position NaN crash
• [Crash] Fixed crash which happened when Export window was closed too quickly
• [Core] Fixed Trigger activation mode - "At least one" as not working properly
• [Core] Fixed bug which made it so Auras were loaded with invalid initial state, e.g. Triggers are Inactive, yet Aura is Active. Please report if you'll notice that problem again.
• [UI] Improved error display in C# Scripts
• [UI] Fixed text editor soft-crash which happened in some cases
• [UI] Fixed jobs scheduler crash #EA-1121
• [UI] Fixed a problem with UI elements sometimes not showing scroll
• [UI] Disabled Cogs animation
• [UI] Fixed a problem with color picker in ColorCheck/PixelSearch
• [WaitFor] WaitFor action now behaves exactly as Delay if it does not have any links in it
• [TextSearch] Fixed Tesseract (numbers) not initializing properly
• [SendSequence] Added Random Offset (like in MouseMove nodes)
• [SendSequence] Fixed a problem with Restore Mouse position not working as expected in some cases
• [SendSequence] Added chill time 1ms to TetherScript - this should fix a problem with TetherScript driver not being able to read requests fast enough
• [BehaviorTree] Fixed a major visual bug which sometimes removed multiple nodes from the tree instead of a selected one
• [CheckIsActive] Fixed node not being properly redrawn
• [Scripting] Made it possible to implement EA-based authentication mechanism right in your code, meaning you can code your own login procedure which will be relying on EyeAuras Sublicenses
• [Scripting] Fixed an issue with LocalProcess memory-reader breaking after multiple sequential reloads
• [Scripting] Improvements in scripting system - added AdditionalPath resolution for Managed assemblies in NuGet packages
• [Scripting] Improved script obfuscation quality
• [Scripting] Added GetCurrentColor in ColorCheckNode
• [Scripting] Added EngineId to TextSearch in CV API - now you can specify which OCR engine to use, e.g. Tesseract (eng) or Windows (rus)
• [Scripting] Breaking change: ISharedResourceRentController: IObservable<AnnotatedBoolean> IsRented => IObservable<AnnotatedBoolean> WhenRented + bool IsRented
• [EyePad] Greatly improved loading performance for larger .sln files
• [EyePad] Added Recent files

C# Scripting - DLL injection

For the last couple of months I've been working on internal improvements of EyeAuras.Memory namespace. The goal is to extend capabilities and to support DLL injection and hooking of external processes. For now, I am releasing only one bit of the entire set of improvements - LocalProcess now has InjectDll method which uses naive CreateRemoteThread based injection. This will not help with kernel anti-cheat protected projects. We're already testing kernel-driver based solution which allows to counteract that inconvenience - I'll keep you posted.

DLL injection brings a lot of interesting and powerful things to the table - the topic is very niche and technical, but in the next 6-12 months I'll be trying to make it accessible to anyone with some C# skills, without deep understanding of internals.

Bugfixes/Improvements

• [Crash] Fixed ColorSearch template-related crash (disposal race) #EA-1146 by @ganya
• [UI] Disabled Cogs animation
• [UI] Fixed a problem with color picker in ColorCheck/PixelSearch
• [Scripting] Added GetCurrentColor in ColorCheckNode
• [Scripting] Added EngineId to TextSearch in CV API - now you can specify which OCR engine to use, e.g. Tesseract (eng) or Windows (rus)
• [Scripting] Breaking change: ISharedResourceRentController: IObservable<AnnotatedBoolean> IsRented => IObservable<AnnotatedBoolean> WhenRented + bool IsRented
• [TextSearch] Fixed Tesseract (numbers) not initializing properly
• [EyePad] Greatly improved loading performance for larger .sln files

Bugfixes/Improvements

• [Crash] Fixed BT Node Position NaN crash
• [UI] Fixed jobs scheduler crash #EA-1121
• [UI] Fixed a problem with UI elements sometimes not showing scroll
• [SendSequence] Added chill time 1ms to TetherScript - this should fix a problem with TetherScript driver not being able to read requests fast enough
• [Scripting] Improvements in scripting system - added AdditionalPath resolution for Managed assemblies in NuGet packages
• [Scripting] Improved script obfuscation quality
• [EyePad] Added Recent files

SendSequence changes

Added two new flags, which target the scenario when you want to play some long-long sequence of actions, but at the same time you want to make it possible that it could be interrupted at any given moment.

E.g. you have a sequence of skills, which are cast inside WhileActive block. Now you want to be able to interrupt it at any given moment (e.g. by toggling hotkey to "Off" state). Previously it was not possible to do so without using Behavior Trees or Macros. But now, with these two new options, it is just a couple of clicks

Can Be Interrupted

As stated in the name, it changes behavior of the action - if, for any reason, Aura gets deactivated, the action will be stopped, even if the sequence has not been completed yet.

But abruptly stopping sequences of inputs is not really a great idea most of the time - if, for example, action has pressed some button and NOT released it yet, if it will be interrupted, the button will stay pressed, probably breaking something.

That is where the second flag comes in handy:

Restore Keyboard State

This flag remembers keys, pressed by the sequence and will release them automatically at the end of the action. So even if the action was interrupted in the very middle, there will be no "stuck" keys.

Bugfixes/Improvements

• [Crash] Fixed crash which happened when Export window was closed too quickly
• [UI] Fixed text editor soft-crash which happened in some cases
• [Core] Fixed Trigger activation mode - "At least one" as not working properly
• [Scripting] Made it possible to implement EA-based authentication mechanism right in your code, meaning you can code your own login procedure which will be relying on EyeAuras Sublicenses
• [SendSequence] Fixed a problem with Restore Mouse position not working as expected in some cases
• [EyePad] Implemented "recent files", try it out in portable version

Macros - Return/Break nodes

Adding two new nodes which should help to create better and smarter Macros!

Return

Return node allows you to exit the macro whenever you want to, even right in the middle of some sequence of operations. E.g. if character has died it does not make much sense to continue running the main loop. Equivalent of return operation in C#

Break

Break is more niche - it allows you to exit the current scope (not the macro!), e.g. if you're inside some Repeat loop, you can jump out of it if needed. Equivalent of break operation in C#

Wiki

C# Scripting - Blazor Windows

Added a series of articles in Russian/English about programming using EyeAuras Blazor Windows API

• Intro
• WebView
• Hello, World
• Creating a Toggle
• Making UI Interactive
• Adding multiple different controls
• Applying styles
• Inline CSS
• External CSS

Behavior Tree / Macro

Added a whole bunch of articles about Behavior Tree / Macro nodes. Note that most of these articles are available in both Russian and English.

• IsActive - checks whether parent Tree/Macro is currently Active
• Interrupter - (advanced) node, that allows to break execution of Behavior Tree if some condition is met
• Return - allows to stop the macro
• Break - allows to Break from the loop or code block
• MouseMove Abs - moves cursor somewhere on the screen (or to something)
• MouseMove Rel - moves cursor relatively to its current position
• CheckKeyState - checks whether some key is currently being held
• KeyPress - simulate keypresses
• Send Text - inputs text either via copy-pasting it or inputting each character individually

Bugfixes/Improvements

• [SendSequence] Added Random Offset (like in MouseMove nodes)
• [CheckIsActive] Fixed node not being properly redrawn
• [BehaviorTree] Fixed a major visual bug which sometimes removed multiple nodes from the tree instead of a selected one

Bugfixes/Improvements

• [Core] Fixed bug which made it so Auras were loaded with invalid initial state, e.g. Triggers are Inactive, yet Aura is Active. Please report if you'll notice that problem again.

Bugfixes/Improvements

• [UI] Improved error display in C# Scripts
• [WaitFor] WaitFor action now behaves exactly as Delay if it does not have any links in it
• [Scripting] Fixed an issue with LocalProcess memory-reader breaking after multiple sequential reloads

Overlapping Panels – Fixed! Strike Back

In 8540 I've tried to fix the problem displayed on the screen below - some of the panels in the program overlap and create unpleasant and glitchy effect. The problem, unfortunately, is not on EA side, but in one of the core frameworks that is developed by Microsoft. In February, they've posted that the bug is finally fixed, so I've tried to upgrade to that version and for the last couple of weeks we've all been testing their fix. As a result of that testing, I have to rollback the change - the new version fixed overlap problem, but introduced 3 new problems:

• performance is noticeably worse
• there are some issues with popping up windows(e.g. Login or Bindings editor)
• but the final nail to the coffin is a broken drag'n'drop - somehow MS managed to screw up one of the core UI functionalities and this is the one for which I could not find any workaround - in EyeAuras drag'n'drop is a core functionality used in Behavior Trees and Macros.

So, for now, the airspace issue is back. I'll keep monitoring the situation.

Bugfixes/Improvements

• [UI] Rolled back to WebView2

Bugfixes/Improvements

• [UI] Fixed a problem with Popups not reacting on mouse clicks - WebView2 issue
• [UI] TargetWindow - changed expression to be WindowHandle || ProcessName || WindowTitle instead of WindowHandle || WindowTitle || ProcessName

New Release – 1.8 (RU/EN)

What's New?

Mini-apps – EyeAuras-based Standalone Applications

Over the past few months, most of the development has been focused on C# scripting. Many changes were introduced, primarily aimed at simplifying development and improving compatibility with various NuGet packages. The focus shifted from visual programming towards improving the user experience when working with scripts. The goal is to make it as easy and intuitive as possible to create mini-apps that do something useful — whether it be a small automation tool or a full-fledged bot. Under the hood, they will leverage the full power of EyeAuras, but on the surface — it's entirely up to you.

To support this, there's already a powerful feature set:

• Packs – the ability to bundle your application into a portable ZIP archive -- Includes built-in support for updates, rollbacks, settings persistence, etc. Everything EyeAuras has gained over the years is now available to your apps.
• Script Protection – the code you write will be protected from prying eyes -- Essential for most paid applications. You don't even have to worry about how it works internally.
• Sublicenses – if your mini-app is not free, you can easily integrate a sublicensing system based on EyeAuras infrastructure for license payments and tracking, while you receive the revenue.

And that’s not all — crypto payment support and full UI hiding will be added soon, along with many other improvements. The mission is to drastically reduce the time between having an idea and getting your app running on a happy user's machine.

I believe mini-apps may become the primary way to fund the rest of EyeAuras development (discussed below). Time will tell how accurate that assumption is.

What About Behavior Trees, Macros, Auras?

Nothing bad! Yes, upcoming months will likely be script-focused, but the roadmap includes:

Full Migration of EyeAuras to a New UI Framework

This includes auras, triggers, and actions. The annoying lags when switching auras will finally be gone. Load times will improve by ~3–5 seconds. This migration will take about one year.

Introduction of a New Automation System – Blueprints

We already have Auras, Macros, Behavior Trees, and Scripts. Each has its strengths: Trees for bots, Auras for small automations (e.g., auto-pots), Macros for predefined action sequences, and Scripts as a universal hammer.

But there’s always room to grow. Inspired by Unreal Engine Blueprints, we aim to create a new visual programming tool: Blueprints. The idea is to place Auras and logic blocks on the same canvas (similar to BT editor) and define interactions between them — reactions to aura triggers, execution sequences, event logic, loops, etc. You can also call BTs and Macros from within.

This will take months, but initial prototypes may appear later this year.


EyeAuras SDK (NuGet Package)

This is the logical evolution of mini-apps — but with your app as the primary product, and EyeAuras becomes a toolkit.

Want to capture the screen? Done. Simulate input using 10+ methods? No problem. Embed C# scripting so users can write their own automation logic? Yes — EyeAuras scripting is now a standalone, mature engine.

Every capability in EyeAuras is available as a plug-in module.

The technical challenges have been solved. Early SDK versions can already be used in C# projects via NuGet. Licensing/distribution details are being finalized. The SDK will be commercial — one-time purchase, use it however and as much as you like. It will be a fully autonomous product, not tied to EyeAuras infrastructure.

Expect more info in the second half of the year.

DMA / FPGA Integration EN / RU

📎 More info, examples, and scripts — here

DMA (Direct Memory Access) is a technology that allows reading or writing data directly to computer RAM without involving the CPU or OS. This makes it possible to access any process’s memory, even those protected by anti-cheat systems or technologies like Kernel Patch Protection (KPP), HVCI, and user-mode hooks.

What does it offer?

• Full access to all memory — including the kernel and protected processes. Both read and write are supported.
• Analyze anti-cheat-protected games without risk of detection.
• Use EyeAuras C# scripting on top of raw hardware. You work with memory as if it’s ReadProcessMemory, but behind the scenes, you’re talking directly to the PCIe bus.

All of this is now available in the familiar EyeAuras scripting model — no need for HDL, PCIe knowledge, virtualization, or drivers.

Status & Roadmap

• ✅ Basic DMA read/write
• ✅ EXE/DLL module resolution via virtual addresses
• ✅ Integrated with IMemory and IProcess APIs
• ⏳ Advanced diagnostics/debugging tools (for cases of firmware instability or failures)
• ⏳ Read/write performance improvements
• ⏳ DMA-based DLL injection into a target process

ImGui Integration EN / RU

Native ImGui integration is in progress — a modern, imperative-style UI option to complement the existing Blazor model.

ImGui ("Immediate Mode GUI") is a fast, lightweight UI library designed for tools in game engines. Used in many AAA editors, it’s known for its speed, ease of use, and live updates every frame.

In EyeAuras this means:

• Lightning-fast UI rendering without HTML/DOM/JS overhead
• Easy for beginners — simple UIs in 10 lines of code
• Quickly visualize bot state: checkboxes, logs, counters, overlays
• Suitable for one-file mini-apps with UI + logic in a single .csx

Here's an example (also covered in the guide):

AddNewExtension<ImGuiContainerExtensions>();

var osd = GetService<IImGuiExperimentalApi>()
    .AddTo(ExecutionAnchors);

osd.AddRenderer(() =>
{
    ImGui.Begin("My UI");
    ImGui.Text("Control window flags and interaction behavior.");

    var isActive = Trigger.TriggerValue ?? false;
    if (ImGui.Checkbox("Is Active", ref isActive))
    {
        Trigger.TriggerValue = isActive;
    }
    ImGui.SameLine();
    ImGui.TextDisabled("(Gets/Sets whether Trigger is active or not)");

    ImGui.Separator();

    if (Trigger.IsActive == true)
    {
        ImGui.TextColored(new Vector4(0f, 1f, 0f, 1f), "Trigger is currently ACTIVE");
    }
    else
    {
        ImGui.TextColored(new Vector4(1f, 0f, 0f, 1f), "Trigger is currently INACTIVE");
    }

    ImGui.End();
});

Now you can build truly standalone mini-apps inside a single .csx file.

Usb2Kbd – Hardware Input Emulator EN / RU

Usb2Kbd is a hardware input emulator supported in EyeAuras since ~2021.

Now you can build your own for about $10 using an inexpensive board from AliExpress or Amazon.

Here’s a detailed step-by-step guide: Russian / English

The backend has also been improved and the settings window redesigned for a better user experience.

Behavior Trees / Macros

Action Nodes Now Have Outputs

All action nodes (e.g., Wait, MouseMove, KeyPress, etc.) now support outputs. The linked node is executed only if the current one succeeds.

Default Properties Support

You can now set Target Window and Input Simulator for each tree or macro individually. As before, properties can still be set at the folder level — this adds flexibility, not a replacement.

C# Scripting Improvements

Referencing Other Scripts from BTs / Macros

You can now reference another Aura containing a C# Script action — similar to referencing a different project in software development.

All types and classes defined in that script become available for use in your BTs or Macros.

This feature has been around for a while but was previously hidden from public view as it wasn’t stable enough.


How is this useful?

Now you can define a C# class that analyzes the game — via memory or CV — and feeds data into your Behavior Tree. Instead of cluttering the BT with dozens of variables and conditions, you can encapsulate all logic in a single class (e.g., TheGame).

Example bot that uses this model

More info here

Razor Namespace Declaration No Longer Required

Here’s a typical Razor component from before:

UserComponent.razor

@namespace GameGrind
@inherits BlazorReactiveComponent
<!-- your Razor/HTML code -->

UserComponent.cs

namespace GameGrind;

public partial class UserComponent : BlazorReactiveComponent {
    // some code
}

That namespace (GameGrind) used to be autogenerated, making it hard to copy/paste between scripts without conflicts.

Now, namespace declarations are optional — EyeAuras injects them at compile time. Less code = fewer headaches.

Two New ML + OSD Examples

Fixed an issue with ComputerVision API not loading models/images via HTTP. Two example bots were added:

Aim Trainer 2D ML Aimbot+ESP

This example shows how to:

• Find a window by title
• Use ComputerVision to find images, run ML, OCR, etc.
• Use SendInput to simulate user input
• Use OnScreenCanvas to draw overlays
• Detect objects with a pretrained ML model
• Aim the mouse and click center
• Draw object/window position on-screen via OSD


Aim Trainer 2D ML Aimbot+ESP (ImGui)

Same as above, but uses ImGui for UI and overlays.

Performance Improvements

Upgrade to .NET 8

.NET is the platform that powers EyeAuras. .NET 8 was chosen due to a new memory manager prototype that outperforms all previous versions.

EyeAuras traditionally prefers increased memory usage for higher performance, so a fast memory collector isn’t a luxury — it’s a necessity. This version still uses the older GC, but once the new GC is stable, it will be enabled.


Folder Property Editor Rewrite

The editor now uses the new UI framework — faster and more responsive.

Old Version:

New Version:

Macro UI Optimization

Macro rendering has been significantly reworked. You’ll notice the difference especially in large macros (50+ nodes). More updates are coming.

Overlapping Panels – Fixed!

This long-standing bug caused panels to overlap — most notably C# Action overlapping Event Log. It’s known as the WPF Airspace issue and has existed for over 12 years. In Microsoft’s UI stack used by EyeAuras, it’s been around since July 2020.


After years of waiting, Microsoft finally fixed it. There was no real workaround, so we had to wait.

This fix is not just about better UI on small screens — it unblocks the long-awaited migration of triggers/actions to the new UI. Previously, everything had to be rewritten at once. Now, it can be done gradually — much more manageable.

Bugfixes / Improvements

• [Crash] Fixed crash in folder property editor
• [Overlays] Adjusted Hide/Show sequence — overlays appear faster
• [UI] Improved drag-and-drop responsiveness in BTs/Macros
• [Macros] Fixed drag-and-drop in Repeat/IfThenElse
• [Macros] Cloning now includes entire hierarchy, not just one node
• [BT] Fixed PopOut behavior
• [UI] Improved drag/resize behavior
• [DMA] Fixed LeechCore init timing issues
• [DMA] Fixed FPGA board disposal issue
• [BT] Fixed CTRL+A bug — sometimes selected too much
• [BT] Parallel node loading — large trees load faster
• [Scripting] PoeShared.Blazor.Controls exposed by default (e.g. ReactiveButton)
• [UI] Logs now show reason for script cancellation (e.g. main window activation)
• [Scripting] Added ReadManaged<T> — slower than Read<T>, but honors MarshalAs
• [Scripting] Added support for x86/x64 target processes (script runtime remains x64)
• [Scripting] BT Editor can now be opened from scripts — build trees dynamically
• [Scripting] Fixed HTTP loading in CV API
• [Scripting] ReadExports now returns human-readable export name along with mangled symbol