I've looked and could not find this. Looking for a script that will keep the bot alive. The current problem I'm having is that sometimes the bot pings out and never reconnects.
Thanks
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.
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.
bot keep alive
Re: bot keep alive
I wonder why it pings out in the first place.
Do you have any scripts loaded?
Comment them ALL out, and start the bot. Let it run a day or whatever it takes, to see if that changes things.
If it does, then you know that one of your scripts is blocking the bot. Could be that the bot is not responding to the server's ping.
Is there anything in the bot's log, that might be a clue?
Or perhaps you leave your client logged into the partyline?... have you seen anything there, that might clue you as to what is really happening?
Do you have any scripts loaded?
Comment them ALL out, and start the bot. Let it run a day or whatever it takes, to see if that changes things.
If it does, then you know that one of your scripts is blocking the bot. Could be that the bot is not responding to the server's ping.
Is there anything in the bot's log, that might be a clue?
Or perhaps you leave your client logged into the partyline?... have you seen anything there, that might clue you as to what is really happening?
Your original request was for a script to keep the bot alive. We could come up with something to make the bot ping the server, or you, or whatever - periodically. But to what avail? You've just said that sometimes it takes forever.
See what I mean? This is why I was more concerned with the cause.
Perhaps somebody else will jump in here with an idea.
p.s.
if you want to name the two respective networks/servers and tell us which is the culprit, maybe somebody will have already had experience with them to share, and you might wake them up.
See what I mean? This is why I was more concerned with the cause.
Perhaps somebody else will jump in here with an idea.
p.s.
if you want to name the two respective networks/servers and tell us which is the culprit, maybe somebody will have already had experience with them to share, and you might wake them up.
Run it in debug? Or set console to debug and watch for errors, then trace?dutch1918 wrote:I an using v1.8... How would I check to see what the deeper problem might be so it can be fixed
We explore.. and you call us criminals. We seek after knowledge.. and you call us criminals. We exist without skin color, without nationality, without religious bias.. and you call us criminals.