Having problems when using ATTAC in conjunction w/TWX.
Attac will sometimes (more than not) auto-shutdown while connected to twx. I'm thinking it may be a inactivity delay or something built into attac. Happens only while scripts are running, and with ATTACs registration scheme, i.e parsing the "Hello, " REG_NAME "welcome to:" will tell attac that it is not reg'd and limit the wonderful built in scripts.
You need to make sure that ATTAC is parsing data when you log in.
If you turn off the ATTAC parsing to make TWX run faster... make sure to WAIT until you in the game or it wont register properly.
earth.
I don't think u understood exactly what I meant. (Too much info)... Attac shuts down while TWX is running scripts.
The login situation goes as such:
start twx.
connect to server.com:2002
fire up attac.
connect to 127.0.0.1:23
type in Lucky Dog
type in "A" for game a
and login ... everything is fine at this point.
run aroudn killin folks and such then pop a script in .twx
go wash up from all the killin and come back script fine...
then all of a sudden bye bye attac window.
(unprovoked and not same script running)
fire attac back up and can't pbust more than 14 planets etc...
Any ideas. I thought it might be a built it feautre to close the window in the event of a time delay in running external scripts or something.
when you create your game ( or click attac->options from menu. on the first screen you see with the games, there is an option to Close Window on Exit. Change that to never. see what happens.
earth.
The scripts that I'm using are predominately a WSSM script, PPT script, or PBust scripts. Neither of these log in or out of game.
The scripts will run fine for some time and then ATTAC will close the window (meanwhile script still running). I will then restart ATTAC and it will connect back to TWX but willnot update the sidebar stats or be considered registered. I am able to get it to Register itself by shutting down attac a couple of times and then exiting the game and log back in it.
As far as I can figure... Attac will only shutdown when it seems like there might be some sort of buffer overflow? Since it only happens when running scripts, and the way twx runs scripts, I think it just goes too fast for attac to keep up, so therefore, it shuts down. (Yet with no error message, which doesn't help the debugging part.)
And as far as when attac closes... In order for attac to re-recognize your registration information, you have to hit $c, then $c again to reconnect into the game. (Just make sure you have 'Helper parses Data' checked)
So, as far as the coder is concerned, maybe he should consider upping the buffer limit, or at least allowing some sort of debugging information to be saved to the computer. (ie. buffer overflow, buffer underflow, expecting blah, but got blah1, etc.) and maybe he should also drop the old TWAR way of checking registrations and just start writing some sort of registration algorythim into attac, and give us all serial numbers.