- Welcome to AlomWare Toolbox Forum.
Recent posts
#91
General Discussion / Re: Auto-clicker
Last post by oblivion - April 03, 2026, 01:43:05 PMHi Paul,
Try this. Notepad fullscreen, Toolbox minimised. The test from previously, with a single modification, then try to abort it with Esc.
Esc stops it and it (a) doesn't restart, and (b) doesn't crash Toolbox.
Change the parameter in line 1 by adding a pair of zeroes to the end, try again. This time, the loop stutters and continues until you hold Esc down and, once it's stopped, the crash happens.
Now do you see why I think it's a bug?
Try this. Notepad fullscreen, Toolbox minimised. The test from previously, with a single modification, then try to abort it with Esc.
Code Select
(Start)
HOW TO USE: Copy from Start to End, and then paste into an action.
REFERENCE : See an example of pasting at alomware.com/paste.png
0001 String: Assign "10000"
0002 Action: Repeat this block "string$"
0003 Macro: Type keys or use mouse "{@300,450}{leftclick}{z25}"
0004 Action: End of block ""
(End)
Esc stops it and it (a) doesn't restart, and (b) doesn't crash Toolbox.
Change the parameter in line 1 by adding a pair of zeroes to the end, try again. This time, the loop stutters and continues until you hold Esc down and, once it's stopped, the crash happens.
Now do you see why I think it's a bug?
#92
General Discussion / Re: Auto-clicker
Last post by Paul (Lead Developer) - April 03, 2026, 11:45:51 AMQuote from: oblivion on April 02, 2026, 11:27:46 PMI remain determined that 15 and 16 shouldn't be necessaryI think you're misunderstanding how Esc works with "Macro: Type keys or use mouse". Pressing it does indeed abort the macro, but you're then restarting the macro again (because it's in a loop), so the old escaped macro has correctly stopped but a new one has started instead. It's like whack-a-mole. That's why an extra check for Esc is needed (step 15) to abort the loop itself, instead of just aborting the macro. Steps 15 and 16 are need to make it like pulling out the plug on a whack-a-mole machine so no more moles can pop up after you whack one (Esc on the macro).
Quote from: oblivion on April 02, 2026, 11:27:46 PMtried to click {@string$} and it didn't work
This works here as expected:
Code Select
(Start)
HOW TO USE: Copy from Start to End, and then paste into an action.
REFERENCE : See an example of pasting at alomware.com/paste.png
0001 String: Assign "123,456"
0002 Macro: Type keys or use mouse "{@string$}{leftclick}{z25}"
(End)
#93
General Discussion / Re: Auto-clicker
Last post by oblivion - April 02, 2026, 11:27:46 PMI've rewritten the code to simplify things a bit. Well, quite a lot. It's now just a forever loop.
I thought about posting this in the Tips area but I remain determined that 15 and 16 shouldn't be necessary (and don't need to be present if the loop's set to repeat for, say, 10000 steps), and that the coding's very specific to a two-monitor setup where the monitors have different characteristics, so it's barely even a template...
And I only mention it at all because my first go at this routine set string$ to the appropriate coordinates then tried to click {@string$} and it didn't work. So maybe that's a request?
Code Select
(Start)
HOW TO USE: Copy from Start to End, and then paste into an action.
REFERENCE : See an example of pasting at alomware.com/paste.png
0001 Action: Comment "This macro was targeted for: Cookie Clicker"
0002 Action: Comment "You can edit the 'Window: Assign' step to change the target."
0003 Window: Assign "Cookie Clicker.exe"
0004 Macro: For assigned window only "1"
0005 Window: Activate for use ""
0006 Macro: Typing speed "def"
0007 Alert: Ask for a choice "Where is Cookie Clicker?~External monitor~Laptop screen~"
0008 Action: Do next step if "alert$=blank$"
0009 Action: Finish ""
0010 Action: Repeat this block "forever"
0011 Action: Do next step if "alert$=External monitor"
0012 Macro: Type keys or use mouse "{@370,600}{leftclick}{z25}"
0013 Action: Do next step if "alert$=Laptop screen"
0014 Macro: Type keys or use mouse "{@300,450}{leftclick}{z25}"
0015 Action: Do next step if "{esc}=1"
0016 Action: Finish ""
0017 Action: End of block ""
0018 Action: Finish ""
(End)I thought about posting this in the Tips area but I remain determined that 15 and 16 shouldn't be necessary (and don't need to be present if the loop's set to repeat for, say, 10000 steps), and that the coding's very specific to a two-monitor setup where the monitors have different characteristics, so it's barely even a template...
And I only mention it at all because my first go at this routine set string$ to the appropriate coordinates then tried to click {@string$} and it didn't work. So maybe that's a request?
#94
General Discussion / Re: Auto-clicker
Last post by oblivion - April 02, 2026, 05:29:06 AMOK, that seems to fix it. Still don't really understand why the "forever" loop behaves differently to the finite version but a fix is a fix 
#95
General Discussion / Re: Auto-clicker
Last post by Paul (Lead Developer) - April 01, 2026, 06:16:19 PMOkay, I can see what you mean now, from your last snippet. Here's what's happening: The Esc key is correctly aborting the macro in step 3, as expected. But then you're restarting the same aborted macro again immediately... and forever. So you need to manually check for the Esc key being held down in the block (step 4 below), and then abort the repeating block as well. Like this:
Having said this, the action shouldn't crash Toolbox when done your original way, so I need to look into that.
So you need to manually check for the Esc key being held down in the block (step 4 below), and then abort the repeating block as well. Like this:Code Select
(Start)
HOW TO USE: Copy from Start to End, and then paste into an action.
REFERENCE : See an example of pasting at alomware.com/paste.png
0001 String: Assign "forever"
0002 Action: Repeat this block "string$"
0003 Macro: Type keys or use mouse "{leftclick}{z25}"
0004 Action: Do next step if "{esc}=0"
0005 Action: End of block ""
(End)Having said this, the action shouldn't crash Toolbox when done your original way, so I need to look into that.
#96
General Discussion / Re: Auto-clicker
Last post by oblivion - April 01, 2026, 01:12:53 AMI think you can test it with anything. Open notepad fullscreen and let it rip.
As far as I can tell, it's utterly reliable as long as you're not triggering the forever parameter on the block that starts on line 11. Only one Esc required to terminate it. If it's running indefinitely (or, previously, with a very large number for the loop) then a single Esc causes a hiccup and a continue, then Esc needs to be leaned on, then Toolbox (quietly) crashes. No errors, nothing like that, it just goes away.
For what it's worth, I've reworked it slightly so I don't have to remember which coordinates I want the mouse to click at. The action now looks like this:
However, I think you could test just by opening notepad fullscreen and running a script that just consisted of lines 21-24 then aborting it with Esc after 20 seconds or so.
I've just tried it.
You won't see much happening, apart from the flickering of the Toolbox icon in the notification area, but you should see exactly what I mean when you try to stop the loop.
As far as I can tell, it's utterly reliable as long as you're not triggering the forever parameter on the block that starts on line 11. Only one Esc required to terminate it. If it's running indefinitely (or, previously, with a very large number for the loop) then a single Esc causes a hiccup and a continue, then Esc needs to be leaned on, then Toolbox (quietly) crashes. No errors, nothing like that, it just goes away.
For what it's worth, I've reworked it slightly so I don't have to remember which coordinates I want the mouse to click at. The action now looks like this:
Code Select
(Start)
HOW TO USE: Copy from Start to End, and then paste into an action.
REFERENCE : See an example of pasting at alomware.com/paste.png
0001 Action: Comment "This macro was targeted for: Cookie Clicker"
0002 Action: Comment "You can edit the 'Window: Assign' step to change the target."
0003 Window: Assign "Cookie Clicker.exe"
0004 Macro: For assigned window only "1"
0005 Window: Activate for use ""
0006 Macro: Typing speed "def"
0007 Alert: Ask for a choice "Where is Cookie Clicker?~External monitor~Laptop screen~"
0008 Action: Do this block if "alert$=External monitor"
0009 Alert: Ask for a line of text "How many clicks?"
0010 String: Assign "alert$"
0011 Action: Do next step if "string$>99999"
0012 String: Assign "forever"
0013 Action: Repeat this block "string$"
0014 Macro: Type keys or use mouse "{@370,600}{leftclick}{z25}"
0015 Action: End of block ""
0016 Action: End of block ""
0017 Action: Do this block if "alert$=Laptop screen"
0018 Alert: Ask for a line of text "How many clicks?"
0019 String: Assign "alert$"
0020 Action: Do next step if "string$>99999"
0021 String: Assign "forever"
0022 Action: Repeat this block "string$"
0023 Macro: Type keys or use mouse "{@300,450}{leftclick}{z25}"
0024 Action: End of block ""
(End)However, I think you could test just by opening notepad fullscreen and running a script that just consisted of lines 21-24 then aborting it with Esc after 20 seconds or so.
I've just tried it.
Code Select
(Start)
HOW TO USE: Copy from Start to End, and then paste into an action.
REFERENCE : See an example of pasting at alomware.com/paste.png
0001 String: Assign "forever"
0002 Action: Repeat this block "string$"
0003 Macro: Type keys or use mouse "{@300,450}{leftclick}{z25}"
0004 Action: End of block ""
(End)You won't see much happening, apart from the flickering of the Toolbox icon in the notification area, but you should see exactly what I mean when you try to stop the loop.
#97
General Discussion / Re: Auto-clicker
Last post by Paul (Lead Developer) - March 31, 2026, 07:57:54 PMHave you got another free app that you (and I) can test it with? I don't want to buy Cookie Cutter on Steam just to look deeper into it.
When you say Toolbox terminates, do you mean it literally crashes or quits so that it's no longer running?
When you say Toolbox terminates, do you mean it literally crashes or quits so that it's no longer running?
#98
General Discussion / Re: Auto-clicker
Last post by oblivion - March 31, 2026, 02:02:12 AMOh. Well, that was a quick experiment.
The updated code is:
So it works, as far as it goes. Asking for 1000 clicks in line 7 delivers 1000 clicks then ends. Asking for 5000 clicks in line 7 and then interrupting (with Esc) after a thousand or two aborts processing as expected.
Asking for 5000000 clicks should set the block repeat instruction in line 11 to "forever" -- and apparently does. However, while it clicks away cheerfully at the assigned location indefinitely, an interruption (which is now a requirement!) needs to be made twice and then Toolbox terminates. Toolbox is running as admin (it can't see the target program if not, for some reason) and minimised.
The block that's being executed doesn't change, just the loop parameters do. And it's not about the number of times you go round the loop, I don't think, because it neither crashes nor fails to complete 5000, but DOES crash if it's been round the loop with the "forever" parameter fewer than 5000 times and is then terminated with Esc.
The updated code is:
Code Select
(Start)
HOW TO USE: Copy from Start to End, and then paste into an action.
REFERENCE : See an example of pasting at alomware.com/paste.png
0001 Action: Comment "This macro was targeted for: Cookie Clicker"
0002 Action: Comment "You can edit the 'Window: Assign' step to change the target."
0003 Window: Assign "Cookie Clicker.exe"
0004 Macro: For assigned window only "1"
0005 Window: Activate for use ""
0006 Macro: Typing speed "def"
0007 Alert: Ask for a line of text "How many clicks?"
0008 String: Assign "alert$"
0009 Action: Do next step if "string$>99999"
0010 String: Assign "forever"
0011 Action: Repeat this block "string$"
0012 Action: Comment "Next line is for external monitor, line after for internal"
0013 Macro: Type keys or use mouse "{@370,600}{leftclick}{z25}"
0014 ;Macro: Type keys or use mouse "{@300,450}{leftclick}{z25}"
0015 Action: End of block ""
(End)So it works, as far as it goes. Asking for 1000 clicks in line 7 delivers 1000 clicks then ends. Asking for 5000 clicks in line 7 and then interrupting (with Esc) after a thousand or two aborts processing as expected.
Asking for 5000000 clicks should set the block repeat instruction in line 11 to "forever" -- and apparently does. However, while it clicks away cheerfully at the assigned location indefinitely, an interruption (which is now a requirement!) needs to be made twice and then Toolbox terminates. Toolbox is running as admin (it can't see the target program if not, for some reason) and minimised.
The block that's being executed doesn't change, just the loop parameters do. And it's not about the number of times you go round the loop, I don't think, because it neither crashes nor fails to complete 5000, but DOES crash if it's been round the loop with the "forever" parameter fewer than 5000 times and is then terminated with Esc.
#99
General Discussion / Re: Auto-clicker
Last post by oblivion - March 31, 2026, 01:31:15 AMThanks for looking, Paul.
The script is fine up to about 15000 clicks -- haven't tested it incrementally beyond that. The problems only occurred with loops of half a million and beyond but I think what I might do is put in a condition to click indefinitely if the number input is >99,999 -- see what happens then. If the issue is "too many loops" it'll happen again, and if it's "counting down from half a million" then it won't.
Mouse positioning isn't an issue as I'm handling that within the script anyway.
The script is fine up to about 15000 clicks -- haven't tested it incrementally beyond that. The problems only occurred with loops of half a million and beyond but I think what I might do is put in a condition to click indefinitely if the number input is >99,999 -- see what happens then. If the issue is "too many loops" it'll happen again, and if it's "counting down from half a million" then it won't.
Mouse positioning isn't an issue as I'm handling that within the script anyway.
#100
Solutions / Trouble changing priority of p...
Last post by Paul (Lead Developer) - March 30, 2026, 10:09:14 PMQuestion: Trouble changing priority of program in registry
"I'd like to permanently set a program to have a higher priority than normal. I found a few websites recommending the same registry change but it doesn't seem to have any effect."
This user wants a certain program to always open with a specific process priority set. He wanted to use the Windows Registry to do it, but that's dangerous and not recommended. Instead, just use AlomWare Toolbox to change any app's process priority when it starts, and avoid the risky Registry and batch files altogether.
So, how is it done? Let's demonstrate by making PeaZip always open in High priority instead of Normal priority. When PeaZip opens, middle-click its icon area to open AlomWare Toolbox's Power menu. Then highlight the "CPU priority" item and select "High" to change its priority:
Next we want to make PeaZip always open that way, so again middle-click its icon area but this time select "Opening state > Open like this" from the Power menu:
A confirmation window will now open for PeaZip, so select "Use app name" and click "OK" to save this PeaZip opening state:
That's it! Now whenever PeaZip opens, it will be in High process priority instead of Normal. The Task Manager confirms it:
Did you know: If you change some other settings in the Power menu before selecting "Opening state > Open like this", then those settings will get saved for the opening state as well. So you could make PeaZip open on top of all other windows, and/or always open it dimmed, and/or open it transparent, etc. Cool!
"I'd like to permanently set a program to have a higher priority than normal. I found a few websites recommending the same registry change but it doesn't seem to have any effect."
This user wants a certain program to always open with a specific process priority set. He wanted to use the Windows Registry to do it, but that's dangerous and not recommended. Instead, just use AlomWare Toolbox to change any app's process priority when it starts, and avoid the risky Registry and batch files altogether.
So, how is it done? Let's demonstrate by making PeaZip always open in High priority instead of Normal priority. When PeaZip opens, middle-click its icon area to open AlomWare Toolbox's Power menu. Then highlight the "CPU priority" item and select "High" to change its priority:
Next we want to make PeaZip always open that way, so again middle-click its icon area but this time select "Opening state > Open like this" from the Power menu:
A confirmation window will now open for PeaZip, so select "Use app name" and click "OK" to save this PeaZip opening state:
That's it! Now whenever PeaZip opens, it will be in High process priority instead of Normal. The Task Manager confirms it:
Did you know: If you change some other settings in the Power menu before selecting "Opening state > Open like this", then those settings will get saved for the opening state as well. So you could make PeaZip open on top of all other windows, and/or always open it dimmed, and/or open it transparent, etc. Cool!