Report how the run went
Add the Report how the run went step so a macro can tell LuvMacro a win from a loss. It never changes how the macro plays.
What the step does
Report how the run went tells LuvMacro whether a run was a win or a loss. LuvMacro uses it for Discord notifications and for the session counts. It never changes how the macro plays. Put it at the end of each round.
A macro without this step works exactly as before. It still sends the other messages you chose, but no win and loss messages.
Add it
- Open the macro and press Edit…. For a recording, you edit a copy. See Edit a macro.
- Press Add action, open Screen detection and choose Report how the run went.
- Choose how it decides, below, then press Save changes and Save….
The step's options are Report this result, Picture of the win screen, Picture of the loss screen, the part of the screen to look at, and Give up after (seconds). Further options are Looks in a row before it counts and Remember the result as.
A fixed result
If the macro already knows how the round went, for example inside the branch of an If step, set Report this result to A win, A loss or Unknown. Nothing is looked for on the screen, and no picture is sent to Discord.
From the screen
Attach one or two pictures cut from the real result screens: Picture of the win screen and Picture of the loss screen. The step looks for them the way the other picture steps do. The rules are cautious on purpose:
- Both pictures are looked for on one capture of the game window (or the part of the screen you chose). Matching works as for the other picture steps, with a threshold of 0.9 unless you change it.
- A result is reported only when exactly one picture is seen, on 2 looks in a row (0.5 seconds apart) unless you change it. A screen that flickers or shows both does not count.
- If nothing is recognised, both are recognised, or Give up after (seconds) passes (15 seconds unless you change it), the result is unknown. It is never guessed as a win or a loss.
- Giving only one picture cannot prove the other result. With only a win picture, "not seen" is unknown, not a loss.
- After reporting unknown, the step ends as timed out, so the macro can still branch on it with the timed out condition.
- Remember the result as keeps "win", "loss" or "unknown" in a variable.
Pictures
The pictures travel inside the macro file, so a macro that ships with them works on import with nothing to set up. Make each one with a screenshot tool, crop it to the small part that only appears on that result screen, and save it as a PNG of 2 MB or less. LuvMacro cannot take a picture from your screen yet. See Missing pictures and Screen sizes and scaling.
No game comes with ready-made win and loss pictures. LuvMacro has not been tested with Roblox or any other game, so test your pictures on the real result screens before you rely on them.
The picture in Discord
If you turned on Result screen picture, the picture sent with a win or a loss is the exact capture the step looked at. Nothing is captured later, and nothing outside the game window's own area is included. It is a copy of that screen rectangle, so a window on top of the game would appear in it. A fixed result has no picture.
Older versions
A macro that uses this step is saved in the 2.x file format. LuvMacro 1.x cannot open it and shows its usual message that the file was saved by a newer version. Macros that do not use the step are unchanged.
