Why a countdown appears before a macro plays
The countdown in Macro by Zaweba gives you time to click into the window the macro works in. Set it from 0 to 10 seconds in Tools > Settings.
That countdown is there to give you time to click into the window the macro should work in. Macro by Zaweba shows it before every replay, 3 seconds by default. You can change it to anything from 0 to 10 seconds in Tools > Settings, and 0 turns it off.
It doesn't get in your way while it runs. The countdown overlay never takes the focus, and clicks pass straight through it to the window underneath.
The problem it solves
A recorded macro replays clicks and keystrokes in whatever window has the focus. When you press Play in Macro, Macro's own window has the focus. Without a pause, the first steps of the replay could land on Macro itself, or on whatever program happened to be behind it.
The countdown gives you a moment to put things right. Press Play, click into the form or spreadsheet or program the macro is meant for, and let the countdown finish. The replay then begins where it should.
Why it never takes the focus
A countdown window that grabbed the focus would cause the very problem it is meant to prevent. So the overlay sits on top without becoming the active window, and a click on it goes to whatever is beneath. You can click into the target window even if the countdown is covering part of it.
When to change it
If you always start macros from their own hotkey while the target window already has the focus, the countdown isn't doing much for you, and a shorter one or 0 is fine. A hotkey such as Ctrl+Alt+1, set per macro in the library, starts the replay from any program, so you're already in the right place.
If you start macros with the Play button or F5 and then have to find the right window, a longer countdown helps. Someone who works across two screens, or whose target program takes a moment to come forward, might prefer 5 seconds or more.
The setting applies to every replay, so pick a value that suits the way you usually work.
It's part of a wider set of safety steps
The countdown is one of several things meant to make replays calm and easy to stop. The other is the panic stop. Holding Esc for one second stops any replay, in any program, at any speed. The replay stops before its next event and lets go of any key or mouse button the macro was holding. Quick taps of Esc, and Esc presses that are part of the macro, are ignored, so a macro that uses Esc to close a dialog still runs normally.
If the panic stop can't be switched on, the macro refuses to start. Between that and the countdown, you always know you can get out.
Countdowns and unattended runs
Macros can be played from the command line with ZawebaMacro.exe --play, which is how Schedule by Zaweba runs them on a timetable. In that case nobody is at the keyboard to click into a window, so the target program needs to be ready and in front already. A countdown can't prepare the screen for you when nobody is there, so plan the starting state of an unattended run with care.
A good habit
Treat the countdown as a moment to check. Is the right window in front? Is the cursor in the first field? Is the list file the one you meant? Three seconds is enough for that glance, and it saves replays that start in the wrong place. If something looks wrong once the replay starts, hold Esc.
