Mission Running Bot

05/05/2015 21:47 0ptimist#121
Release Version 2015.04.04.13:

Änderungen seit der letzten Version:
  • Bugfix
    • Bot did not scroll through overview which could result in a loop or ignoring of objects.
05/11/2015 19:18 Wanze3#122
Hi,
mir ist aufgefallen, das es hin und wieder vorkommt, das abgefarmte Asteroiden weiterhin ausgegraut in der Mining Liste auftauchen, hier geht der Bot in einen Loop über, so das er versucht diese Asteroiden auszuwählen, was jedoch nicht geht. Liesse es sich einbauen, das alle paar Minuten/Klicks, ein anderes Tab geöfnet wird und dann zurück auf die Mining Seite gewechselt wird? Durch diesen Wechsel werden die ausgegrauten Asteroiden entfernt.
05/13/2015 21:55 0ptimist#123
Quote:
Originally Posted by Wanze3 View Post
Hi,
mir ist aufgefallen, das es hin und wieder vorkommt, das abgefarmte Asteroiden weiterhin ausgegraut in der Mining Liste auftauchen, hier geht der Bot in einen Loop über, so das er versucht diese Asteroiden auszuwählen, was jedoch nicht geht. Liesse es sich einbauen, das alle paar Minuten/Klicks, ein anderes Tab geöfnet wird und dann zurück auf die Mining Seite gewechselt wird? Durch diesen Wechsel werden die ausgegrauten Asteroiden entfernt.
Interessant, war mir noch nicht aufgefallen. Und gut zu wissen das durch den Wechsel des Tab die veralteten Einträge entfernt werden. Ich merke mir das vor für die Entwicklung des Miningbot.
05/15/2015 20:02 thesaltonsea#124
Hello and sorry for the english :) I have some questions - is the bot reading only the client (OCR) or it is injecting something in the .exe and .dll's ?
05/15/2015 22:40 0ptimist#125
Quote:
Originally Posted by thesaltonsea View Post
Hello and sorry for the english :) I have some questions - is the bot reading only the client (OCR) or it is injecting something in the .exe and .dll's ?
The Bot does not inject or write to the Eve Online Client.
It gets information from the Eve Online Client by reading its memory (not OCR).
05/15/2015 22:42 thesaltonsea#126
Thanks for the fast response :) Thats good news, will give it a try :) Does it support npc null sec l4 missions ?
05/16/2015 10:03 0ptimist#127
Quote:
Originally Posted by thesaltonsea View Post
Thanks for the fast response :) Thats good news, will give it a try :) Does it support npc null sec l4 missions ?
The current Version of mission runner and miner do not support nullsec. It will not accept missions in lowsec or nullsec.
Support for l4 missions is limited, you can see which ones are supported in the missions list displayed by the Bot.
05/17/2015 20:38 Qade#128
Hello.
Thank You for this bot,
I've been testing it for couple days now, and it works really well.


I have some thoughts/suggestions. If You're interested in some ideas. :) Just a couple of random things I would like to see in the future. :)

1. Align to station after reaching mining position and activating miners, and after every move, and stop ship prealined. (That would speed up jumping to dump ore, gank escape time)

2. Full ore hold miner cut-off. (example: When You have only, say, 500m capacity left and your ship gets 3000m every cycle, bot should stop mining after 1/6 of cycle.)

3. Scavenger drones. (It would be nice if the bot could launch a single scavenger drone after a rat attack to pick up stuff)

4. Immediate warp off on player attack or while criminal or suspect players are present in system, or when couple of non-mining ships warp into your belt (it usually signifies ganking attempt. Its better to be safe than sorry :) )

5. Chat window visible. (I dont know why this bot is closing my chat window. I often have Eve open on my second PC, it would be nice to have the option to see what is going on in local)

6. Miner cycle setting. (an option to set a timer for the bot to switch off and on miners every couple of seconds, eg. 1/3 of cycle, to avoid empty cycles. Sometimes using a Survey scanner is just a waste of perfectly good slot. :) )

7. Bookmark jump (it would be nice if the bot could place a bookmark after getting close to the ore deposit and use it next time to warp straight to ore location. It would minimise travel time)

8. Random belt jump (the bot seems to prefer to jump to belt 1)

9. Chat window monitoring (for gankers and other undesirable ppl :) )

10. Auto restart after disconnects.

11. The possibility to setup automatic cargo missions running.

So...(a bit lengthy wish list :) ),but really, thank You again for all this work that You already put into this.
05/18/2015 21:46 0ptimist#129
Quote:
Originally Posted by Qade View Post
I have some thoughts/suggestions. If You're interested in some ideas. :) Just a couple of random things I would like to see in the future. :)
I have some comments/questions:

Quote:
Originally Posted by Qade View Post
2. Full ore hold miner cut-off. (example: When You have only, say, 500m capacity left and your ship gets 3000m every cycle, bot should stop mining after 1/6 of cycle.)
The bot already does this, but there could be a delay of up to 15 seconds from the time the ore hold is full until the bot turns off the miners. Sometimes it fails to read the phase of a module (how many seconds it is into the cycle) that might have caused an additional delay.


Quote:
Originally Posted by Qade View Post
3. Scavenger drones. (It would be nice if the bot could launch a single scavenger drone after a rat attack to pick up stuff)
I have no idea how I would test this, where can I get those scavenger drones?

Quote:
Originally Posted by Qade View Post
4. Immediate warp off on player attack or while criminal or suspect players are present in system, or when couple of non-mining ships warp into your belt (it usually signifies ganking attempt. Its better to be safe than sorry :) )

5. Chat window visible. (I dont know why this bot is closing my chat window. I often have Eve open on my second PC, it would be nice to have the option to see what is going on in local)

8. Random belt jump (the bot seems to prefer to jump to belt 1)

9. Chat window monitoring (for gankers and other undesirable ppl :) )
I am planing to implement those.


Thank you for taking the time to express your thoughts.
05/20/2015 13:01 thesaltonsea#130
So,

i tested the l4 missions with tengu, it was ok for 1-2h. Only got problem with Damsel in Distress, but i think it was because i have 4-5 overview tabs and that confused the bot.

Last night i started testing the mining, but i got a problem - after 20-30 minutes of working the bot is closing the game client without any info in the bot log ... Any ideas what is causing this ?

Keep up the good work :)
05/20/2015 19:17 0ptimist#131
Quote:
Originally Posted by thesaltonsea View Post
So,

i tested the l4 missions with tengu, it was ok for 1-2h. Only got problem with Damsel in Distress, but i think it was because i have 4-5 overview tabs and that confused the bot.

Last night i started testing the mining, but i got a problem - after 20-30 minutes of working the bot is closing the game client without any info in the bot log ... Any ideas what is causing this ?

Keep up the good work :)
About the Damsel in Distress:
I dont know how the L4 Version looks like but when I tested, I got the Level3 Mission every now and then and the Bot had no Problems there. Actually this is one of the most profitable when running L3s with the Bot.

The closing Problem:
The Bot does not contain any logic to close the Eve Client but I saw this happen when the Eve Client was disconnected: A message Box Pops up in the Eve Client and when the ESC Key is pressed (which is used by the Bot to close MessageBoxes), EVE gets closed.
But in such a cases the log would contain an entry which describes the intention (something along the lines "close MessageBox"). So far I have no idea what actually happened.

Did this happen repeatedly?
05/20/2015 19:31 thesaltonsea#132
About the Damesl, first time it done it right, but the second time i got it, it clears the first wave and then just started to switch between overview tabs. I will test it with only 1-2 overview tabs to see how it is.

About the mining, i think there was some "Disconnected" message but i was thinking that it was about the connection between client and the bot. Will test it tonight again.

edit: one more question, when i rename the bot to word.exe (because CCP is watching the running process on the PC's i think), the bot cant read the Eve process . Is it normal or i am doing something wrong ?
05/20/2015 20:59 0ptimist#133
Quote:
Originally Posted by thesaltonsea View Post
About the Damesl, first time it done it right, but the second time i got it, it clears the first wave and then just started to switch between overview tabs. I will test it with only 1-2 overview tabs to see how it is.

About the mining, i think there was some "Disconnected" message but i was thinking that it was about the connection between client and the bot. Will test it tonight again.
I am going to implement a persistent report containing more details then just what fits into the UI. This will make it easier to get to the bottom of such sporadic issues.

Quote:
Originally Posted by thesaltonsea View Post
edit: one more question, when i rename the bot to word.exe (because CCP is watching the running process on the PC's i think), the bot cant read the Eve process . Is it normal or i am doing something wrong ?
I just tested this myself and can confirm renaming the program will not work with the current Version. But this was not the intention, I will change it to be independent from the file name.

However, when it comes to detection by CCP, the most important thing is to look out for behaviour which could cause suspicion among other players or CCP.
If the Bot gets stuck in loops, stop using it until the problem is fixed.
This also includes actions like opening a contextmenu which cannot be seen by other players but could be monitored by CCP.
05/21/2015 02:35 Qade#134
Quote:
Originally Posted by 0ptimist View Post
I have no idea how I would test this, where can I get those scavenger drones?
Oh, I meant Salvager drones. :) My bad. Although it would be awesome if there were Scavenger drones. :)
05/21/2015 10:19 thesaltonsea#135
Yeah, i have removed this mission from the list for now :)

I tested again the mininig , this time it was working for a longer time before it closes , but i wasnt near the pc when it happend.

It will be good to write the log to a text file so we can debug it when we have problems :)