Tray-resident combo-input daemon for the cabinet. Ten slots of "hold X, press Y → send Z", where X and Y can each be a keyboard key or an XInput gamepad button, in any mix. Neon shell matching FFBBlaster MASTER.
.NET 8 WinForms. Runs on Windows x64 and can be built on Windows, macOS, or Linux.
Download the latest Windows release.
Extract ArcadeMacros-Windows-v1.1.1.zip and run ArcadeMacros.exe. The portable
release includes the .NET runtime; no separate runtime installation is needed.
Layout preview recreated from the UI code; not a native Windows screenshot.
Adds an optional DONATE / BUY ME A COFFEE link in the lower-right footer. It opens the PayPal donation page in the default browser. The app does not collect payment details or initiate a payment.
To update, exit Arcade Macros from its tray menu and replace ArcadeMacros.exe.
Keep your existing arcademacros.settings.json beside it to retain your macros.
Install the .NET 8 SDK, then run from the repository folder:
dotnet publish ArcadeMacros.csproj -c Release -r win-x64 -o distOn macOS or Linux, the build script also archives each build:
bash build.shRun the platform-neutral unit tests with:
dotnet test tests/ArcadeMacros.Tests/ArcadeMacros.Tests.csprojOutput is dist/ArcadeMacros.exe — self-contained, single file, nothing to
install on the cabinet. Around 65 MB compressed; ./build.sh light gives you a
~2 MB exe instead if you'd rather put the .NET 8 Desktop Runtime on the cabinet
once.
The line that makes this work from macOS is <EnableWindowsTargeting>true</EnableWindowsTargeting>
in the csproj. Without it the SDK refuses to restore the Windows Desktop packs
on a non-Windows host.
The WinForms app and input hooks require Windows. The parser and configuration unit tests can run on macOS or Linux.
-
Copy
ArcadeMacros.exesomewhere writable — a tools folder, not Program Files. Settings go inarcademacros.settings.jsonbeside it. -
Double-click. First launch opens the config window; later launches start silent in the tray.
-
Test in this order, because each step rules out a layer:
- Slot 1, keyboard only. Hold
1, pressUp, sends{Tab}. Test in Notepad. This proves the hook, the combo logic, and the sender. - Add a pad. Set HOLD to
PAD1:BACK— the PADS light in the header should go cyan when the controller is connected. Confirms XInput binding and struct offsets. - Scope it. Put
BigBox.exein ONLY IN and confirm the macro goes quiet everywhere else. - Then a game. This is where SendInput's scan codes get their real test.
- Slot 1, keyboard only. Hold
If something doesn't work, knowing which of those four steps broke tells us where the bug is.
| Field | Meaning |
|---|---|
| NAME | Row label. Cosmetic. |
| ENABLED | Whether the slot registers at all. |
| HOLD | Prefix input. SET, then press a key or a pad button. |
| PRESS | Trigger input. Same. |
| SENDS | {Tab}, ^{F4}, {Ctrl down}{Esc}{Ctrl up}, {F5 3} to repeat, or run:C:\path\thing.exe. |
| ONLY IN | BigBox.exe, a bare process name, or a window-title fragment. ahk_exe X is understood too. Blank = everywhere. |
| HOLD KEY LIVE / SWALLOWED | Keyboard-only. LIVE lets the hold key through to the game. SWALLOWED eats it while held and sends the real key if you tap and release without completing a combo. |
Row LED: dark = not armed, cyan = live, amber = armed but everything is paused.
Pause hotkey defaults to Ctrl+Alt+F12; the tray menu has the same toggle.
Edits apply when you hit SAVE & APPLY, not as you type — the engine works from a snapshot so macros can't change under you mid-edit.
Keyboard input goes through a WH_KEYBOARD_LL hook, which can suppress keys.
XInput has no hook, only a poll. So each slot takes one of three paths,
chosen automatically:
| Hold | Press | Path |
|---|---|---|
| key | key | hook sees the press, checks the hold, suppresses the press |
| pad | key | same, except the hold is read from live pad state |
| any | pad | poll thread (8 ms) sees the rising edge |
A pad button in a macro always also reaches the game. Polling can't consume
input. BACK is the usual safe choice for a hold button. Because of this the
pass-through toggle greys out whenever a pad is involved — it only means
something for a keyboard-only combo.
Three details worth knowing, since they're where this differs from the AutoHotkey version:
- Key state is tracked in the hook itself, not read from
GetAsyncKeyState. A suppressed key never reaches the system, so the API would report it as up. - Everything injected carries
dwExtraInfo = 0x5A17CADE, and the hook ignores anything wearing that mark. Otherwise the app would trigger itself. - Keystrokes go out with scan codes as well as virtual keys. Emulators reading raw input or DirectInput see scan codes only, which is the usual reason a macro works on the desktop and does nothing in a game.
The footer button, and it picks its method from how you launched the app:
- Normal launch →
HKCU\...\CurrentVersion\Run, readsSTART WITH WINDOWS: ON. - Run as administrator → Task Scheduler logon task at highest privileges,
reads
START WITH WINDOWS: ADMIN.
Use the admin route if BigBox or TeknoParrot runs elevated. A non-elevated process can't send input into an elevated window, so macros will look dead in exactly those games and nowhere else.
ArcadeMacros.csproj EnableWindowsTargeting lives here
app.manifest PerMonitorV2 DPI, asInvoker
build.sh the Mac build
src/Native.cs every P/Invoke
src/KeyNames.cs VK <-> name, extended-key table
src/InputToken.cs one type covering keys and pad buttons
src/GamePads.cs XInput poll thread
src/Sender.cs SENDS parser + SendInput
src/MacroEngine.cs the hook, combo matching, suppression, window filter
src/Config.cs JSON settings beside the exe
src/Startup.cs Run key / scheduled task
src/Theme.cs palette, fonts, tray menu renderer
src/NeonControls.cs NeonButton, NeonField, SlotList
src/MainForm.cs window layout and painting
src/DonationLink.cs optional PayPal link
src/CaptureForm.cs "press a key" overlay
src/Program.cs entry point and tray
- The Windows executable is cross-compiled on macOS. The new donation link has not been exercised in a Windows session during development.
- No profile switching — one set of ten slots.
- Analog sticks aren't inputs, only the sixteen digital buttons plus the two triggers as on/off past 25% travel.
- Can't emit gamepad output, only keystrokes. That would need ViGEm.
