Hey Fellow Botters, As BW is back on its feet, its time for some additions this bot could really use. I posted a semi list some while back, but this will the new one. In my oppinion these are needed and requested multiple times over the years now. [x] Interaction with Taxi/Travel/Elevator crashes the game / bot. [v] API documentation (now online, see developer section) [x] New quest window doesnt accept quests [x] Mounting logic: - [x] If mounting on vehicle, try mounting on the fly. If no mounted, stop movement then try to mount - [x] If mounting is not possible, use Rocket Boost. [x] Gathering logic: - [x] If the bots goes gathering the companion mostly handles this. But the bot doesnt wait for if the companion did the gathering already or is still busy. If we have multiple nodes to gather from closeby, the bot goes quickly threw all nodes but in the end, mostly one is used, as the companion got an 'overwritten' gather command. [x] Macrobinocular support (we get more dailies nowadays with this type of action) [x] Seeker Droid is more a pain in the ass, but then we can fully implement GSI dailies. [x] A way of implementing NoCombat in MoveTo's [x] A way of implementing NoCombat for Companion [x] Quicktravel support [x] Repairdroid support [x] UseObject logic: - [x] Use object multiple times wasnt working back in the day and i dont think this has been looked at. [x] Reset instance [x] Reset Quest [x] Crew Skill Missions support (maybe via plugin?) If you have more ideas what could be added, reply and ill add them to the list. Anyways let me know your feedback and hope more is getting implemented by Aevitas (Thanks in advance for this). Info: [v] Is implemented or fixed [x] not implemented or fixed
This is already on the list (repairdroid) This should be handled inside the mounting logic. Ill add it.
Stop movement before mount would need to be a configurable option, I paid the 2m to mount on the move as I'm sure many people have and would actually prefer to not stop to mount. Quick travel would be AMAZING.
Ability to vendor medpacs/allow it to A blacklist that works or remeshes to areas on zones that the bot very commonly gets stuck
Have you tried editing "protected.xml" in your settings folder, or does it not work as it used to anymore?
I updated the mounting logic request, to enhance the explanation for the mounting logic. config option should not be used in my opinion, but handled by the logic. Putting it on the list, but i know for a fact someone made a plugin for that, but maybe kept private. For vendoring edit the protected.xml to your likings. A global blacklist would be nice, but also the downside. It will contact nav even more and if a false stuck is triggered it will be send to the server, making botting less effective. If more think it will be a better option let me know.
The blacklist is an interesting idea but I'm not sure if a full remesh would be needed but to blacklist part of the mesh to remove people from getting stuck on that part over and over. Perhaps a weight system to blacklist, 3x reports from 3x different users then would blacklist the spot. I know there was a tree on alderann that caused many of us some issues. With a weight system you would be less likely to report a false positive and have it adjust the mesh in any way.
Timestamps for the bot, so it's much easier and quicker than going into the log to find when and what made the bot stop.
