Thanks Petersen!
but i am using 10,11 different scripts, plus if you are not a coder, then its kind a toug to figure out, i thought there was script or codes to find out, but guess not, and these timer messages are really anoyning, anyway thanks.
Easiest way (and its still a bit long winded) is to comment out one script at a time in your conf file and restart the bot. Trial and error, you'll soon find the one thats causing it then once you do, post it up in here and we can have a look at it to see whats causing the timer errors.
"Insanity Takes Its Toll, Please Have Exact Change"
Thanks, but the problem is that happens every 4,5 hours, i thought may be someone else had these as well, cos timer errors are common and pain in the neck, so they might have a script or something to trace it out.
there isn't really any way to trace it - well actually there is, but it would be one damn resource hungry script. Only way to trace errors like this is to add debugging lines to scripts - which firstly means working out which one it is. Now personally, I never load any scripts without auditing them first, so I know what exactly they'll be doing (+ it means I can fix any obvious mistakes). For everyone else, I always suggest that you load a script on a testbot first for at least 24 hours before running it for real (as virtually no script goes through any kind of QA, you've gotta do your own)
This will only capture error when loadind the script, aka, at start time and during rehash and restart.
It is along these lines though, the script that will help fix this.
The best bet, would be to rename the timer commands (utimer and timer), and create your own versions.
After changing the commands you send it, they would in turn call the ranmed timmer commands.
The changes that take place, are designed to call a seperate script, when the timer is triggered. These will capture errors, and display the command causing the error.
Its a long shot, but isn't there any way to see what proc called the timer or anything other than the timer number? I coulda swore I saw a way before.. And maybe setting your console +d would give you a bit more info? If both of these fail to work, setup a test bot and run once script at a time until you find the error. It will take a while, but when all else fails....