Zugg Software :: View topic

Beginner Joined: 06 Feb 2025 Posts: 24

So first, when i say lockups, i mean the screen freezes while stuff happens behind the scenes and eventually, it unlocks and things scroll by super fast. And, i might know why.

So, lets say I have a trigger and i want to do some things on that trigger. Instead of just encoding the actions inside the trigger, i make an alias. This way, it can be called by either the trigger or manually.

But, inside that trigger i run more aliases for different things, and those aliases sometimes do other things. In the meantime, im executing all of these things and they're sort of keeping the trigger from finishing.

Eventually, ill run so many commands that the command stack or something gets filled and everything pauses. Sometimes this pause lasts as long as 30-40 seconds, which can be a lifetime sometimes.

Im thinking of a couple solutions, but figured maybe I'd ask if anyone has seen this. Im mostly doing this for code-reuse and modularity.

One direct question i have, is there a way you can execute an alias without waiting for it to return? So, a trigger can execute an alias but not wait for it to return?

The rest i think I know how to fix. But knowing that would be helpful.

Beginner Joined: 06 Feb 2025 Posts: 24

Ok, maybe i dont know how to fix the other things. Doc says functions are like aliases that return a value. So much for that idea.

GURU Joined: 10 Oct 2000 Posts: 875 Location: USA

Posted: Sun Feb 15, 2026 3:33 am

A shortcut to force any script to be threaded is to insert a
#WAIT 0
at the start. Not near as powerful as proper threading, but if you just need to do a %mapquerry, or most anything involving database manipulation, or will otherwhise cause the system to hang for processing, it will do the trick.