In order to have a salvage bitch and have the salvage bitch perform everything automatically, a corp is required to relay the salvage instruction (via bm's).
point 1 : Not everyone has the luxury of being in a corp.
point 2: People might want to keep PVP chars and industrial chars in seperate corps.
State retained between run and stop
If the bot doesn't pick up a bookmark perfectly (various reasons), the state cannot be flushed by a stop - run cycle. For example, if the bm wasn't picked up correctly the bot will want to go back to the station repeatedly, even if you fix the bookmarks by renaming them and dropping the old ones.
suggestion
let players controll the salvager manually, and let the salvager be taken to a bm-like location (for example a acceltation gate) and from that point on the bot keeps salvaging (and following gates) till it is done, end with a auditory signal and change the bot state to stopped.
Or hook the salvaging logic minus the warp and bookmark logic into a mini mode.
Issue 2 : cap spam
Cap depleted spam, should cut off when cap is detected at 10%, might be detectable at the eve protocol level, Or at least it's annoying to hear the "cap depleted" message 5 times a second.
Issue 1: Fleet Requirement
In order to have a salvage bitch and have the salvage bitch perform everything automatically, a corp is required to relay the salvage instruction (via bm's).
point 1 : Not everyone has the luxury of being in a corp.
point 2: People might want to keep PVP chars and industrial chars in seperate corps.
State retained between run and stop
If the bot doesn't pick up a bookmark perfectly (various reasons), the state cannot be flushed by a stop - run cycle. For example, if the bm wasn't picked up correctly the bot will want to go back to the station repeatedly, even if you fix the bookmarks by renaming them and dropping the old ones.
suggestion
let players controll the salvager manually, and let the salvager be taken to a bm-like location (for example a acceltation gate) and from that point on the bot keeps salvaging (and following gates) till it is done, end with a auditory signal and change the bot state to stopped.
Or hook the salvaging logic minus the warp and bookmark logic into a mini mode.
Issue 2 : cap spam
Cap depleted spam, should cut off when cap is detected at 10%, might be detectable at the eve protocol level, Or at least it's annoying to hear the "cap depleted" message 5 times a second.