I have been running mIRC scripts in the background while i do other computing tasks.

The issue occurs when I am working with python in command prompt, sometimes my debugging/testing
will require me to ctrl+break out of the python program.

The issue is mIRC is accepting the ctrl+breaks as well, and then it breaks whatever mIRC script i have running
in the background.

Command prompt doesn't register the ctrl+break unless the window is focused on, so i think maybe mIRC needs
a similar setup. That the program needs to be active or focused on, before it accept the breaks. Maybe this needs
to be an optional parameter, whether to listen for ctrl+break globally or not.

Let me know if you have any questions, Thanks!

Thanks for your bug report. The way control+break works has been through quite a few changes over the years. Unfortunately, Windows does not allow a busy/non-responsive window to become active. This means that if a script is running that makes the mIRC window busy/non-responsive (a common occurrence for long running scripts), it can no longer detect control+breaks unless it does so globally.