LuvMacro v2.0.2

LuvMacro 2.0.2

Discord result messages can now carry a fresh screenshot of your whole screen, taken each time a run reports. Everything else works as in 2.0.1.

Downloads

File	For
LuvMacro-2.0.2-Windows-Setup.exe	Windows 10 / 11, installs for the current user
LuvMacro-2.0.2-Windows-Portable.zip	Windows 10 / 11, no install
SHA256SUMS.txt	checksums for every file above

macOS: no download in this release. It has not been tested on a real Mac.

Verify a download in PowerShell and compare with SHA256SUMS.txt:

Get-FileHash .\LuvMacro-2.0.2-Windows-Setup.exe -Algorithm SHA256

Code signing: not signed. Windows will show a SmartScreen warning when you download and first run it. Choose More info, then Run anyway, or check the checksum first.

Installing 2.0.2

From 1.1.0, 1.1.1, 2.0.0 or 2.0.1: the app offers Update Now, or use Settings > About > Check for updates. Your settings and macros are kept.
From 1.0.1 or earlier: run the setup file once; it upgrades in place and keeps your settings.
The portable zip is only told a new version exists and pointed to the download page.

What's new in 2.0.2

• A fresh screenshot with each Discord result (Windows). The Report how the run went step has a new setting, Attach a screenshot to the Discord message. When the step reports a win, a loss or an unknown result, LuvMacro takes a new picture of your whole screen at that moment and sends it with the message, so every message shows what the screen looked like then, not one stored picture. It works for fixed results too. It is only taken if you have Discord connected and the Result screen picture switch on in Settings, and only for the kinds of result you chose to receive. It is not saved on your computer, and if the capture fails the message is sent without a picture and the macro carries on. It shows everything on your screen, including other windows. The setting is off unless you turn it on, so existing macros behave as before.

New in 2.0.1

• Capture from the screen (Windows). In the editor, on a picture setting, press Capture from the screen, then drag a box around what the macro should look for. LuvMacro hides its own windows, shows your screens frozen and dimmed, and keeps the picture inside the macro. Esc or a right click cancels and nothing changes. The picture is saved at your screen's real size, so it matches what the macro sees when it plays, even on a scaled display, and a capture never replaces a picture you already have. Adding a picture action to a macro with no pictures now starts with a capture.

Still in this version from 2.0.0

• AutoHotkey scripts. Open an .ahk file (AutoHotkey version 2 scripts, plus a smaller part of version 1) and LuvMacro converts it so it can play. LuvMacro never runs AutoHotkey, and your original file is never changed. Scripts keep their own keys, which are listed first. Scripts that need pictures look for them in an img folder next to the script; missing ones are named and the script won't play until they are there. Scripts LuvMacro can't run are refused with a plain message and an error code, and nothing is run.
• Edit your macros. A new Edit button opens a step-by-step editor for recordings, scripts and 2.0 macros. A recording is edited as a copy, so the original file is not changed and still plays as before. In an edited copy, mouse movement is simplified to straight moves and positions stay where you recorded them (window scaling is not kept). The editor can suggest improvements one at a time, and nothing changes unless you press Do it. Saving always writes a LuvMacro (.luvmacro) file; LuvMacro never saves or exports AutoHotkey.
• Import details. For a script, Import details shows what it needs, which keys it uses and how it differs from the original. LuvMacro also tells you if your screen is a different size than the script was made for.
• Settings in its own window. Settings opens beside the main window with four tabs (General, Recording, Playback and About), so the main window stays in view.
• What's New appears once after you update, and can be opened again from Settings > About.
• Optional Discord notifications. Settings > General > Discord Notifications > Connect Discord opens your browser to allow LuvMacro, then sends you a test message; it only says "Connected" after that message really arrived. After that LuvMacro can send you, privately: win and loss results (for macros that report them), problems, and under More options started/finished/stopped messages, a session summary and a warning after several defeats in a row (which can also stop the macro). Everything starts quiet: results and problems only, and no picture. A small picture of the result screen can be added to wins and losses if you turn it on. LuvMacro's service keeps only your Discord ID (encrypted) so it can message you; Disconnect removes it, Remove my Discord data removes it even without the app, and it expires after 180 days unused. You need to be in the LuvMacro Discord server, because Discord only lets the bot message people who share a server with it; your own Discord privacy settings can still block it, and LuvMacro tells you when they do.
• Report how the run went (new macro step). A macro can say whether a run was a win or a loss, directly or by recognising pictures of the result screens. It never changes how the macro plays, and when it can't tell the result is unknown, never a win or a loss. Macros that don't use it work exactly as before. See docs/DISCORD_NOTIFICATIONS.md.
• Emergency stop and Start over. Stop (F8 by default) ends a recording or a script at once, and any key or mouse button that was held down is let go. A script that keeps running also gets a Start over button.

Tested

• Automated tests on Windows (the full suite plus a separate quality-assurance suite).
• The packaged Windows app's own self-test, and the editor, Settings and import windows checked from screenshots in dark and light themes.
• Discord notifications: automated tests with a fake Discord (connecting, every refusal path, private delivery, the result rules, preferences, statistics, and that none of it holds up a macro). The owner also connected a real Discord account on 1 November 2026 and it worked; the "join the server first" screen was seen for real before the bot was added to the server. Not tried with a real account: blocked direct messages, a link removed on Discord's side, and win/loss pictures from a real game's result screen.
• Attach a screenshot: automated tests (every report gets its own picture, nothing is captured unless the step, the Settings switch and the result kind all allow it, a failed capture changes nothing, two-monitor pictures stay readable). It was also run in the real app on this PC's two monitors against a real Discord connection: five results were sent and all five arrived with their own picture.
• Capture from the screen: automated tests with made-up screens (the box in every direction, scaled displays, several screens, cancelling, the editor's own windows hiding and coming back, a picture too big to keep). The drag overlay was also drawn on a real two-monitor setup at 125% scaling with a test pattern and the saved picture was checked to be exactly the box that was dragged. Not tried: capturing from a game or full-screen program, a screen at other scaling levels, or Windows 10.
• Not tested: Roblox or any other game, anti-cheat, full-screen games, Windows 10, macOS on a real Mac, a real update from one published release to the next, and the signed-installer path (no code-signing certificate yet).

Known limitations

• Roblox and other games are untested; whether a game accepts simulated input is up to the game. Camera control that uses a locked cursor isn't reproduced.
• Programs running as administrator ignore input from LuvMacro.
• Only a part of AutoHotkey is understood. Scripts that run programs, call system functions, use windows of their own or read and write files are refused.
• Pictures a script looks for may not match at a different screen size or scale.
• An edited recording does not keep window scaling, and its mouse movement is simplified.
• Capturing a picture from the screen is Windows only for now. A captured picture gets an automatic name (picture.png, picture-2.png, ...); to use another name, attach a PNG file instead.
• Discord notifications need the LuvMacro Discord server and an internet connection to LuvMacro's notification service; they are off until you connect. No game comes with ready-made win/loss pictures: they have to be made from real screenshots of that game's result screens, and LuvMacro does not claim detection works for any particular game.
• The result picture is a copy of the game window's area of the screen at that moment, so another window on top of it would appear in it, and a minimised or fully covered game can't be seen.
• A macro that uses the new Report how the run went step can't be opened by LuvMacro 1.x, and one that uses Attach a screenshot can't be opened by LuvMacro 2.0.1 or earlier.
• Attach a screenshot sends your whole screen, including other windows, to your own Discord messages. It is Windows only for now, and only tried with fixed results, not on a real game's result screens.
• On macOS the saved Discord link is only protected by file permissions (Windows uses the system's per-user encryption). macOS is not yet tested on real hardware.
• The installer is not code-signed, so the signature check is the app's own.

Privacy

Recording starts only when you press Record. Your recordings and scripts are stored locally and are never uploaded. Looking at the screen for pictures happens only while a script that needs it is playing, stays on your computer and is never saved. It ...

LuvMacro v2.0.1

LuvMacro 2.0.1

Capture a picture from your screen inside the editor. Everything else works as in 2.0.0.

Downloads

File	For
LuvMacro-2.0.1-Windows-Setup.exe	Windows 10 / 11, installs for the current user
LuvMacro-2.0.1-Windows-Portable.zip	Windows 10 / 11, no install
SHA256SUMS.txt	checksums for every file above

macOS: no download in this release. It has not been tested on a real Mac.

Verify a download in PowerShell and compare with SHA256SUMS.txt:

Get-FileHash .\LuvMacro-2.0.1-Windows-Setup.exe -Algorithm SHA256

Code signing: not signed. Windows will show a SmartScreen warning when you download and first run it. Choose More info, then Run anyway, or check the checksum first.

Installing 2.0.1

From 1.1.0, 1.1.1 or 2.0.0: the app offers Update Now, or use Settings > About > Check for updates. Your settings and macros are kept.
From 1.0.1 or earlier: run the setup file once; it upgrades in place and keeps your settings.
The portable zip is only told a new version exists and pointed to the download page.

What's new in 2.0.1

• Capture from the screen (Windows). In the editor, on a picture setting, press Capture from the screen, then drag a box around what the macro should look for. LuvMacro hides its own windows, shows your screens frozen and dimmed, and keeps the picture inside the macro. Esc or a right click cancels and nothing changes. The picture is saved at your screen's real size, so it matches what the macro sees when it plays, even on a scaled display, and a capture never replaces a picture you already have. Adding a picture action to a macro with no pictures now starts with a capture.

Still in this version from 2.0.0

• AutoHotkey scripts. Open an .ahk file (AutoHotkey version 2 scripts, plus a smaller part of version 1) and LuvMacro converts it so it can play. LuvMacro never runs AutoHotkey, and your original file is never changed. Scripts keep their own keys, which are listed first. Scripts that need pictures look for them in an img folder next to the script; missing ones are named and the script won't play until they are there. Scripts LuvMacro can't run are refused with a plain message and an error code, and nothing is run.
• Edit your macros. A new Edit button opens a step-by-step editor for recordings, scripts and 2.0 macros. A recording is edited as a copy, so the original file is not changed and still plays as before. In an edited copy, mouse movement is simplified to straight moves and positions stay where you recorded them (window scaling is not kept). The editor can suggest improvements one at a time, and nothing changes unless you press Do it. Saving always writes a LuvMacro (.luvmacro) file; LuvMacro never saves or exports AutoHotkey.
• Import details. For a script, Import details shows what it needs, which keys it uses and how it differs from the original. LuvMacro also tells you if your screen is a different size than the script was made for.
• Settings in its own window. Settings opens beside the main window with four tabs (General, Recording, Playback and About), so the main window stays in view.
• What's New appears once after you update, and can be opened again from Settings > About.
• Optional Discord notifications. Settings > General > Discord Notifications > Connect Discord opens your browser to allow LuvMacro, then sends you a test message; it only says "Connected" after that message really arrived. After that LuvMacro can send you, privately: win and loss results (for macros that report them), problems, and under More options started/finished/stopped messages, a session summary and a warning after several defeats in a row (which can also stop the macro). Everything starts quiet: results and problems only, and no picture. A small picture of the result screen can be added to wins and losses if you turn it on. LuvMacro's service keeps only your Discord ID (encrypted) so it can message you; Disconnect removes it, Remove my Discord data removes it even without the app, and it expires after 180 days unused. You need to be in the LuvMacro Discord server, because Discord only lets the bot message people who share a server with it; your own Discord privacy settings can still block it, and LuvMacro tells you when they do.
• Report how the run went (new macro step). A macro can say whether a run was a win or a loss, directly or by recognising pictures of the result screens. It never changes how the macro plays, and when it can't tell the result is unknown, never a win or a loss. Macros that don't use it work exactly as before. See docs/DISCORD_NOTIFICATIONS.md.
• Emergency stop and Start over. Stop (F8 by default) ends a recording or a script at once, and any key or mouse button that was held down is let go. A script that keeps running also gets a Start over button.

Tested

• Automated tests on Windows (the full suite plus a separate quality-assurance suite).
• The packaged Windows app's own self-test, and the editor, Settings and import windows checked from screenshots in dark and light themes.
• Discord notifications: automated tests with a fake Discord (connecting, every refusal path, private delivery, the result rules, preferences, statistics, and that none of it holds up a macro). The owner also connected a real Discord account on 1 November 2026 and it worked; the "join the server first" screen was seen for real before the bot was added to the server. Not tried with a real account: blocked direct messages, a link removed on Discord's side, and win/loss pictures from a real game's result screen.
• Capture from the screen: automated tests with made-up screens (the box in every direction, scaled displays, several screens, cancelling, the editor's own windows hiding and coming back, a picture too big to keep). The drag overlay was also drawn on a real two-monitor setup at 125% scaling with a test pattern and the saved picture was checked to be exactly the box that was dragged. Not tried: capturing from a game or full-screen program, a screen at other scaling levels, or Windows 10.
• Not tested: Roblox or any other game, anti-cheat, full-screen games, Windows 10, macOS on a real Mac, a real update from one published release to the next, and the signed-installer path (no code-signing certificate yet).

Known limitations

• Roblox and other games are untested; whether a game accepts simulated input is up to the game. Camera control that uses a locked cursor isn't reproduced.
• Programs running as administrator ignore input from LuvMacro.
• Only a part of AutoHotkey is understood. Scripts that run programs, call system functions, use windows of their own or read and write files are refused.
• Pictures a script looks for may not match at a different screen size or scale.
• An edited recording does not keep window scaling, and its mouse movement is simplified.
• Capturing a picture from the screen is Windows only for now. A captured picture gets an automatic name (picture.png, picture-2.png, ...); to use another name, attach a PNG file instead.
• Discord notifications need the LuvMacro Discord server and an internet connection to LuvMacro's notification service; they are off until you connect. No game comes with ready-made win/loss pictures: they have to be made from real screenshots of that game's result screens, and LuvMacro does not claim detection works for any particular game.
• The result picture is a copy of the game window's area of the screen at that moment, so another window on top of it would appear in it, and a minimised or fully covered game can't be seen.
• A macro that uses the new Report how the run went step can't be opened by LuvMacro 1.x.
• On macOS the saved Discord link is only protected by file permissions (Windows uses the system's per-user encryption). macOS is not yet tested on real hardware.
• The installer is not code-signed, so the signature check is the app's own.

Privacy

Recording starts only when you press Record. Your recordings and scripts are stored locally and are never uploaded. Looking at the screen for pictures happens only while a script that needs it is playing, stays on your computer and is never saved. It is only ever sent if you turn on Discord notifications and the result-screen picture, and then only that one picture of the game window goes to Discord through LuvMacro's service, which does not keep it. By default the only thing the app asks the internet for is whether a newer version exists (you can turn that off in Settings). If you connect Discord it also talks to LuvMacro's notification service, for that only; the full policy is on the LuvMacro website.

Report a problem

Discord.

LuvMacro v2.0.0

LuvMacro 2.0.0

Edit your macros, open compatible AutoHotkey scripts, optional private Discord notifications, and a Settings window that opens beside the main one. Recording, saving and playing work as they did in 1.1.1.

Downloads

File	For
LuvMacro-2.0.0-Windows-Setup.exe	Windows 10 / 11, installs for the current user
LuvMacro-2.0.0-Windows-Portable.zip	Windows 10 / 11, no install
SHA256SUMS.txt	checksums for every file above

macOS: no download in this release. It has not been tested on a real Mac.

Verify a download in PowerShell and compare with SHA256SUMS.txt:

Get-FileHash .\LuvMacro-2.0.0-Windows-Setup.exe -Algorithm SHA256

Code signing: not signed. Windows will show a SmartScreen warning when you download and first run it. Choose More info, then Run anyway, or check the checksum first.

Installing 2.0.0

From 1.1.0 or 1.1.1: the app offers Update Now, or use Settings > About > Check for updates. Your settings and macros are kept.
From 1.0.1 or earlier: run the setup file once; it upgrades in place and keeps your settings.
The portable zip is only told a new version exists and pointed to the download page.

What's new in 2.0.0

• AutoHotkey scripts. Open an .ahk file (AutoHotkey version 2 scripts, plus a smaller part of version 1) and LuvMacro converts it so it can play. LuvMacro never runs AutoHotkey, and your original file is never changed. Scripts keep their own keys, which are listed first. Scripts that need pictures look for them in an img folder next to the script; missing ones are named and the script won't play until they are there. Scripts LuvMacro can't run are refused with a plain message and an error code, and nothing is run.
• Edit your macros. A new Edit button opens a step-by-step editor for recordings, scripts and 2.0 macros. A recording is edited as a copy, so the original file is not changed and still plays as before. In an edited copy, mouse movement is simplified to straight moves and positions stay where you recorded them (window scaling is not kept). The editor can suggest improvements one at a time, and nothing changes unless you press Do it. Saving always writes a LuvMacro (.luvmacro) file; LuvMacro never saves or exports AutoHotkey.
• Import details. For a script, Import details shows what it needs, which keys it uses and how it differs from the original. LuvMacro also tells you if your screen is a different size than the script was made for.
• Settings in its own window. Settings opens beside the main window with four tabs (General, Recording, Playback and About), so the main window stays in view.
• What's New appears once after you update, and can be opened again from Settings > About.
• Optional Discord notifications. Settings > General > Discord Notifications > Connect Discord opens your browser to allow LuvMacro, then sends you a test message; it only says "Connected" after that message really arrived. After that LuvMacro can send you, privately: win and loss results (for macros that report them), problems, and under More options started/finished/stopped messages, a session summary and a warning after several defeats in a row (which can also stop the macro). Everything starts quiet: results and problems only, and no picture. A small picture of the result screen can be added to wins and losses if you turn it on. LuvMacro's service keeps only your Discord ID (encrypted) so it can message you; Disconnect removes it, Remove my Discord data removes it even without the app, and it expires after 180 days unused. You need to be in the LuvMacro Discord server, because Discord only lets the bot message people who share a server with it; your own Discord privacy settings can still block it, and LuvMacro tells you when they do.
• Report how the run went (new macro step). A macro can say whether a run was a win or a loss, directly or by recognising pictures of the result screens. It never changes how the macro plays, and when it can't tell the result is unknown, never a win or a loss. Macros that don't use it work exactly as before. See docs/DISCORD_NOTIFICATIONS.md.
• Emergency stop and Start over. Stop (F8 by default) ends a recording or a script at once, and any key or mouse button that was held down is let go. A script that keeps running also gets a Start over button.

Tested

• Automated tests on Windows (the full suite plus a separate quality-assurance suite).
• The packaged Windows app's own self-test, and the editor, Settings and import windows checked from screenshots in dark and light themes.
• Discord notifications: automated tests with a fake Discord (connecting, every refusal path, private delivery, the result rules, preferences, statistics, and that none of it holds up a macro). The owner also connected a real Discord account on 1 November 2026 and it worked; the "join the server first" screen was seen for real before the bot was added to the server. Not tried with a real account: blocked direct messages, a link removed on Discord's side, and win/loss pictures from a real game's result screen.
• Not tested: Roblox or any other game, anti-cheat, full-screen games, Windows 10, macOS on a real Mac, a real update from one published release to the next, and the signed-installer path (no code-signing certificate yet).

Known limitations

• Roblox and other games are untested; whether a game accepts simulated input is up to the game. Camera control that uses a locked cursor isn't reproduced.
• Programs running as administrator ignore input from LuvMacro.
• Only a part of AutoHotkey is understood. Scripts that run programs, call system functions, use windows of their own or read and write files are refused.
• Pictures a script looks for may not match at a different screen size or scale.
• An edited recording does not keep window scaling, and its mouse movement is simplified.
• There is no way to capture a picture from the screen inside LuvMacro yet; pictures are added from files.
• Discord notifications need the LuvMacro Discord server and an internet connection to LuvMacro's notification service; they are off until you connect. No game comes with ready-made win/loss pictures: they have to be made from real screenshots of that game's result screens, and LuvMacro does not claim detection works for any particular game.
• The result picture is a copy of the game window's area of the screen at that moment, so another window on top of it would appear in it, and a minimised or fully covered game can't be seen.
• A macro that uses the new Report how the run went step can't be opened by LuvMacro 1.x.
• On macOS the saved Discord link is only protected by file permissions (Windows uses the system's per-user encryption). macOS is not yet tested on real hardware.
• The installer is not code-signed, so the signature check is the app's own.

Privacy

Recording starts only when you press Record. Your recordings and scripts are stored locally and are never uploaded. Looking at the screen for pictures happens only while a script that needs it is playing, stays on your computer and is never saved. It is only ever sent if you turn on Discord notifications and the result-screen picture, and then only that one picture of the game window goes to Discord through LuvMacro's service, which does not keep it. By default the only thing the app asks the internet for is whether a newer version exists (you can turn that off in Settings). If you connect Discord it also talks to LuvMacro's notification service, for that only; the full policy is on the LuvMacro website.

Report a problem

Discord.

LuvMacro v1.1.1

LuvMacro 1.1.1

Clearer messages when something goes wrong, and a Troubleshoot tool in Settings that checks for common problems and makes a support report you can paste into a Discord ticket.

Downloads

File	For
LuvMacro-1.1.1-Windows-Setup.exe	Windows 10 / 11, installs for the current user
LuvMacro-1.1.1-Windows-Portable.zip	Windows 10 / 11, no install
SHA256SUMS.txt	checksums for every file above

macOS: no download in this release. The macOS build exists but has not been tested on a real Mac, so it isn't published yet.

Verify a download in PowerShell and compare with SHA256SUMS.txt:

Get-FileHash .\LuvMacro-1.1.1-Windows-Setup.exe -Algorithm SHA256

Code signing: not signed. Windows will show a SmartScreen warning when you download and first run it. Choose More info, then Run anyway, or check the checksum first.

Installing 1.1.1

From 1.1.0: the app offers Update Now by itself (about once a day), or use Settings > Check for updates. Your settings and macros are kept.
From 1.0.1 or earlier: run the setup file once; it upgrades in place and keeps your settings (1.0.1 has no updater).
The portable zip and macOS copies are only told a new version exists and pointed to the download page.

What's new in 1.1.1

• Clearer messages when a file won't open. 1.1.0 and earlier said "This file is too large to be a LuvMacro recording" for any big file, including ones that aren't macros at all. LuvMacro now says what the file is: a recording from another program (TinyTask's .rec files can't be opened), a video, image, archive or other binary file, an empty file, a cut-off copy, or a damaged one. A real macro over the limit says how big it is and what the limit is. Macros you've already recorded open as before, and the file you open is never changed.
• Error codes. Problems now show a code such as LM-1007. The error window has Copy Error Report and Get Help buttons, and technical details are one click away. The codes are listed in docs/ERROR_CODES.md.
• Settings > Troubleshoot. A short guide for the seven most common problems, Run Diagnostics, a repair for a damaged settings file (it keeps a backup and can be undone), and Copy Support Report, which shows you everything before you copy it. Reports never include your recordings, keys, file locations or window titles, and nothing is ever sent for you. A small local log of problems is kept and can be cleared.
• Everything else looks and works as in 1.1.0.

Tested

• Unit tests on Windows, macOS Apple Silicon and macOS Intel (the release workflow).
• The Troubleshoot and error windows were checked from screenshots in dark and light themes.
• Not tested: Roblox or any other game, full-screen games, Windows 10, macOS on a real Mac, a real update from one published release to the next, and the signed-installer path (no code-signing certificate yet).

Known limitations

• Roblox and other games are untested; whether a game accepts simulated input is up to the game. Camera control that uses a locked cursor isn't reproduced.
• Programs running as administrator ignore input from LuvMacro.
• The status bar may not show over exclusive full-screen games.
• macOS is not yet tested on real hardware.
• If the window moves or resizes while you record, that recording can't be scaled; the app tells you.
• Updates need an internet connection and a public release page; the installer is not code-signed, so the signature check is the app's own.
• The cause of the "too large" message some people saw in 1.0.1 hasn't been confirmed. If you still get a file error, the new message shows the file's size: please include it with the error code.

Privacy

Recording starts only when you press Record. Your recordings are stored locally and are never uploaded. The only thing the app asks the internet for is whether a newer version exists (you can turn that off in Settings). Run Diagnostics makes that same request once.

Report a problem

Discord.

LuvMacro v1.1.0

LuvMacro 1.1.0

Macros you record now adapt to a different game window size, LuvMacro can check for new versions and update itself on Windows, and playback stops safely when its window goes away.

Downloads

File	For
LuvMacro-1.1.0-Windows-Setup.exe	Windows 10 / 11, installs for the current user
LuvMacro-1.1.0-Windows-Portable.zip	Windows 10 / 11, no install
SHA256SUMS.txt	checksums for every file above

macOS: no download in this release. The macOS build exists but has not been tested on a real Mac, so it isn't published yet.

Verify a download in PowerShell and compare with SHA256SUMS.txt:

Get-FileHash .\LuvMacro-1.1.0-Windows-Setup.exe -Algorithm SHA256

Code signing: not signed. Windows will show a SmartScreen warning when you download and first run it. Choose More info, then Run anyway, or check the checksum first.

Installing 1.1.0

From 1.0.1 you need to install 1.1.0 by hand once (run the setup file; it upgrades in place and keeps your settings). 1.0.1 has no updater. From 1.1.0 on, the app checks for a newer version about once a day and offers Update Now; Settings > Check for updates checks on demand. The portable zip and macOS copies are only told a new version exists and pointed to the download page.

What's new in 1.1.0

• Macros adapt to the window size. A macro recorded in 1.1.0 remembers the game window it was recorded in. When you play it into a window of a different size or position, mouse positions are scaled to the new window, so you no longer need to change your Windows resolution. Windows on other monitors, including ones left of or above the main screen, work.
• Honest limits. If the new window is a different shape (for example 16:10 instead of 16:9) you get a plain message; the macro still plays. Scaling can't know where a game moved its buttons, so a game with a different layout at another size can still miss.
• Safer playback. Playback stops and lets go of held keys and buttons if the window is closed or minimized, or if a different window of the same program comes forward.
• Older macros keep working exactly as before. A macro saved by 1.0.1 has no window information, so it plays at the recorded screen positions and keeps its screen-size warning. It is never changed or overwritten. To get the new behaviour, record it again in 1.1.0.
• Updates. Check for updates automatically (on by default) and a Check for updates button in Settings. Updates are downloaded over HTTPS and installed only if their signature and checksum match; the app never installs while you are recording or playing, and your macros and settings are not touched.
• Everything else looks and works as in 1.0.1.

Tested

• Unit tests on Windows (coordinate maths, file format, recording, playback, the update checks and downloads with simulated failures).
• On Windows 11, with real mouse input, a macro recorded in a test window was played back after the window was resized and moved, and every click landed at the same relative place; minimizing the window mid-playback stopped it cleanly.
• Not tested: Roblox or any other game, full-screen games, Windows 10, macOS on a real Mac (window scaling is Windows-only for now; a Mac keeps using recorded screen positions), a real update from one published release to the next, and the signed-installer path (no code-signing certificate yet).

Known limitations

• Roblox and other games are untested; whether a game accepts simulated input is up to the game. Camera control that uses a locked cursor isn't reproduced.
• Programs running as administrator ignore input from LuvMacro.
• The status bar may not show over exclusive full-screen games.
• macOS is not yet tested on real hardware.
• If the window moves or resizes while you record, that recording can't be scaled; the app tells you.
• Updates need an internet connection and a public release page; the installer is not code-signed, so the signature check is the app's own.

Privacy

Recording starts only when you press Record. Your recordings are stored locally and are never uploaded. The only thing the app asks the internet for is whether a newer version exists (you can turn that off in Settings).

Report a problem

Discord.