Soop: While what you say is true, I've heard of people running into issues using timer -m. I never have, and the cases I've heard have been few and far between, but it does happen. As for why it happened I have no idea, but best to post a small warning just in case this is one of those cases.
Truth be told, I tried using 100 timers all set to 0 0 and using -m. I had no slowdowns and the CPU usage for Mirc didn't go up measurably.
Also, using the wscript.sleep method doesn't cause Mirc to hang at all. I'm not sure why exactly as I have little understanding of com functions. Mirc keeps right on processing while wscript.sleep is being used.
Last edited by Thrull; 30/09/09 07:19 AM.
