Jump to content

Join our Slack

Talk to other users and have a great time
Slack Server

Welcome to our Community

Click here to get your Exiled Bot license
Donation Store

Recommended Posts

no_bot does not mean there is no bot found, it means no bot window found, don't try to understand the [Debug] messages, it is for me :)

 

And enable debugging only if there is some sort of bug and want to send the log file to me, Debug messages will make a lots of log, so the file will be big

hm having a similiar issue. autopoe starts poe but idles then. doesn't seem to recognize the login window.

 

Current Status: loading

Current bot status: no_bot

 

doubt its a setting issue, actually used the same *.ini ;)

Edited by stef

Share this post


Link to post
Share on other sites

hm having a similiar issue. autopoe starts poe but idles then. doesn't seem to recognize the login window.

 

Current Status: loading

Current bot status: no_bot

 

doubt its a setting issue, actually used the same *.ini ;)

With the newest autopoe version?

Share this post


Link to post
Share on other sites

With the newest autopoe version?

yeah. not working with last version for me. same as posted

Current Status: loading

Current bot status: no_bot

autopoe not run bot, and not restart it if i close it manually

Share this post


Link to post
Share on other sites

BlackSun, can u add future to close this windows aswell, like u did for exiledbot.exe ?

gjti.png

 

its stop all thing till i step up and close it manually.

Edited by mbxnir

Share this post


Link to post
Share on other sites

BlackSun, can u add future to close this windows aswell, like u did for exiledbot.exe ?

its stop all thing till i step up and close it manually.

Can you provide a log file? I already added that window to the AutoPoE but seems like it is not working and I don't know why.

Share this post


Link to post
Share on other sites

Can you provide a log file? I already added that window to the AutoPoE but seems like it is not working and I don't know why.

i didnt check what time it was. Probably its 6.49

[2/1/2014 3:26:21]: Starting bot

[2/1/2014 3:46:43]: Clicking on login button

[2/1/2014 3:46:44]: Starting bot

[2/1/2014 3:56:58]: Clicking on login button

[2/1/2014 3:56:59]: Starting bot

[2/1/2014 5:43:45]: Clicking on login button

[2/1/2014 5:43:46]: Starting bot

[2/1/2014 6:37:30]: Client timed out, restarting

[2/1/2014 6:37:52]: Starting client

[2/1/2014 6:44:53]: Client timed out, restarting

[2/1/2014 6:45:04]: Starting client

[2/1/2014 6:49:19]: Clicking on login button

[2/1/2014 6:49:21]: Running bot

[2/1/2014 6:49:26]: Starting bot

[2/1/2014 9:21:08]: Clicking on login button

[2/1/2014 9:21:10]: Starting bot

[2/1/2014 12:21:35]: Clicking on login button

[2/1/2014 12:21:37]: Starting bot

I will post correct log when get this error again. Thx for reply.

 

Edited by mbxnir

Share this post


Link to post
Share on other sites

i dont need a fix :)

 

Just for your information Blacksun :

when they had the no_bot,(previous) problem, i haven't a problem.

But now is updated, and i had the no_bot problem.

I think its due to the fact i was using VMware 10.

 

So i installed Vmware 7, and i got no problem anymore. Kinda weird.

 

Anyway , Good work  :)

Edited by drmaboul

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...