This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.


For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.

BogusTrivia help

Support & discussion of released scripts, and announcements of new releases.
Post Reply
k
kato
Voice
Posts: 16
Joined: Sun Mar 23, 2008 7:40 pm

BogusTrivia help

Post by kato »

HI all the game runs for a while and then I get has quit IRC (Quit: triv: fatal error), Then after that when I go to restart the bot I notice the t2.commands.tcl is gone and have to upload it again if i dont the bot doesnot reboot up, any ideas, any and all help will be appericated thanks

Kato
User avatar
starr
Voice
Posts: 26
Joined: Sun Mar 18, 2007 1:18 am
Location: Tennessee
Contact:

Post by starr »

Please provide a bit more information.

1. Eggdrop or Windrop and Version.
2. Unix Shell or your own Unix Machine?
3. If Windrop, Windows Version and sp version installed.
4. TCL version installed.
5. Bogustrivia Version.
6. Are your running any other scripts with bogustrivia?
7. Upgrade or clean install of bogustrivia?
8. Was is ever working properly?

Thanks
User avatar
speechles
Revered One
Posts: 1398
Joined: Sat Aug 26, 2006 10:19 pm
Location: emerald triangle, california (coastal redwoods)

Post by speechles »

If you read (within bogus trivia are things to read, read them) you will find you are doing something wrong, not the script. Arbitrarily doing things, will lead to arbitrary results. You can never be sure of anything unless you are sure everything has been set up correctly. So before you give us any details or anything more, simply follow the directions 100%, to the T. Anything you skip could be your problem.

Code: Select all

proc TChkDed {} {  set ctimrs [utimers]
 set sterm "* TShoTriv *"  ;  set strm2 "* TShoTrv2 *"
 if {[lsearch $ctimrs $sterm]=="-1" && [lsearch $ctimrs $strm2]=="-1"} {
   set qresn "triv: fatal error"  ;  die $qresn
 }
}
Here is where your message is coming from. What it looks like, is the bot sets up some utimers to track time on some things (amount of time to guess the trivia perhaps?). This is the "timer check or die" procedure above, if while the script is running both of these timers die (read this as, the script can't find it's timers running so panics), so does your script. So find where you broke it and fix it, one of your settings must be borked.
Post Reply