Welcome, Guest
Please Login or Register.    Lost Password?

new update broke docking at citadels
(0 viewing) 
Go to bottomPage: 123
TOPIC: new update broke docking at citadels
#51335
Re: new update broke docking at citadels 6 Years ago Karma: 825
Did not get mail. Set subject as 'log files'

Send me client's log. General log is not required (and normally disabled in settings). Set subject as 'log files'
Slav2
Admin
Posts: 16822
graph
User Offline Click here to see the profile of this user
Last Edit: 2018/09/19 10:32 By Slav2.
The administrator has disabled public write access.
Send logs to my mail - with subject 'log files' to pass spam filter.
How to record logs in knowledge base
 
#51337
Re: new update broke docking at citadels 6 Years ago Karma: 0
Slav2 wrote:
Did not get mail. Set subject as 'log files'

Send me client's log. General log is not required (and normally disabled in settings). Set subject as 'log files'



Sorry about that. Resent the right log.

Thank you.
love4youro
Fresh Boarder
Posts: 16
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#51348
Re: new update broke docking at citadels 6 Years ago Karma: 825
Do you have competitors who use the same anomalies like your bot? It looks like bot failed to find new anomaly, one anomaly was marked as occupied as PC ship was in local. Add non priority anomaly keyword. When priority anomaly is not found bot may use nonpriority anomaly and clean space in scanner for other anomalies.
Slav2
Admin
Posts: 16822
graph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
Send logs to my mail - with subject 'log files' to pass spam filter.
How to record logs in knowledge base
 
#51354
Re: new update broke docking at citadels 6 Years ago Karma: 0
Slav2 wrote:
Do you have competitors who use the same anomalies like your bot? It looks like bot failed to find new anomaly, one anomaly was marked as occupied as PC ship was in local. Add non priority anomaly keyword. When priority anomaly is not found bot may use nonpriority anomaly and clean space in scanner for other anomalies.

Yes, I did that with adding a star (*) but if both occupied, will crash again.


Also sent you another reply with log from looter, have some problems with it.


P.S. How to make Eve not close if crash occurs?
love4youro
Fresh Boarder
Posts: 16
graphgraph
User Offline Click here to see the profile of this user
Last Edit: 2018/09/21 10:35 By love4youro.
The administrator has disabled public write access.
 
#51358
Re: new update broke docking at citadels 6 Years ago Karma: 825
Crash in my terms is when bot closed eve for the second time in an hour and completely stopped operation. If bot failed to find anomalies it will wait and check for anomalies again in some time. You can define more non priority keywords to avoid waiting.
Slav2
Admin
Posts: 16822
graph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
Send logs to my mail - with subject 'log files' to pass spam filter.
How to record logs in knowledge base
 
#51361
Re: new update broke docking at citadels 6 Years ago Karma: 0
Ok, then, will add more. But how to make bot to not crash if can't warp ( being neut in local but npc scrambled ). It shouldn't recall drones if scrambled. Priority should be to kill NPC then start warping if enemy on avoid appear. Anyway, If not possible to fix, then give me a solution to stop the crash of the client so I can manually take care of.
love4youro
Fresh Boarder
Posts: 16
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
Go to topPage: 123
Moderators: Slav2
© Macro Laboratory 2024
All rights reserved!
Design by Ivan Kozyrin