Yes. Yes it does work in 6.35 - It doesn't work correctly, but it does work.
Whenever you report a problem with a script, it helps if you described what's the problem. Does it not do anything at all, or does it do the wrong thing, or does it generate errors in the status window, etc
Oh, and most of all, please tell us what we're supposed to do to make the script work, so we don't have to read the entire thread or analyze a script to figure it out.
First of all, you may want to consider upgrading your v6.35, since there have been many bug fixes and new features added since then. If you click on the "news" link at the top of this page, there's a link to the
versions.txt that lists most but not all of the changes between versions, with the newer changes at the top. That is a huge file, and your v6.35 is mentioned on row 3160, so you can see there's been a lot of changes since then.
One of the most important changes was a fix that prevents irc:// chat links at a webpage from launching your mirc.exe using a mirc.ini and scripts that are located on someone else's webpage, and you can imagine what would happen then. You should immediately go to options/irc/catcher and uncheck the box below "chat links" that is labeled "enable support". I'm not saying this eliminates the risk, but it can't hurt. But also, the chat links support is enabled by default, so if your mirc.ini gets destroyed during a computer crash, it gets restored with default settings, and that can cause chat links to be enabled before you realize it happened.
If your reason for using 6.35 is that you use an irc server that does not support the UTF8 encoding, the newer mIRC has an option to disable that and use the old codepages instead. If you have another script that works on the old version and won't work on the newer one, come by #mircscripting on SwiftIRC or Undernet servers, or #mirc on Libera.Chat EFnet etc, and there may be someone who can help fix the script so it can work with newer versions.
- -
First thing to check when a script does not work: go to the options menu of script editor and make sure that "identifier warning" is enabled. It is disabled by default, and if you make a spelling error in a script that makes it call $identifier_that_does_not_exist then this setting creates an error message and stops the script, so you can be alerted for the need to fix the script. Without the option checkboxed, the identifier returns a blank string, which can cause a script to mis-behave when the identifier should always return *something*.
Next, make sure you do not have another ON TEXT event handler in that same script file on a row above it that would intercept message instead of this script.
When I run this code in 6.35, it works mostly correctly, with the only problem being that sometimes one of the countdown numbers is delayed by 1 second and shows out of order. So it would show "5", and then 2 seconds later it would show "3" then "4" then continue the countdown. I even had the "Go" display before the "1".
This problem with the timer does not exist in the newer mIRC, and would require redesigning your script completely to evade the bug when it runs in 6.35
Because this sends out 5 messages so quickly, it's possible that your anti-flood settings can delay some of these countdown messages, which is something that cannot be eliminated.
Also, your script cannot tell the difference between "!countdown 6.5" and "!countdown abc". If they use "!countdown 4.5", it counts down from 4, but never shows the "GO"
So come on by one of the help channels and see if there's someone that can help you with getting setup in one of the newer versions.
