First post, made account here only to praise this bot, and have some feature requests. I'll continue to edit this post to append more ideas as my tiny brain continues to work hard.
1) Once the bot finds the exit area of the map (e.g. while doing sarn, it finds encampment entrance) the bot should enter that and then start new instance from there. What it is doing right now is, exiting game and starting a new one - so it's relogging like 50 times overnight, which is a red flag and would be caught by GGG soon.
2) Picking up rares was implemented, however I would like to have two more functions added to it:
[identify_rare] = true / false (identifies rares vs keep them unid)
[vendor_rare] = true / false (vendors all rare items found to get more currency)If identification is off and vendoring is true, then the bot would start producing orbs of transmutation by selling rares. If identification is on and vendoring is true, then the bot would start producing orbs of alteration by selling rares.3) Pickit is very basic at this time. However as another user suggested that if you're hovering your mouse pointer over something and press ctrl+c, the item description is copied in the clipboard. The clipboard can easily be read by the bot to check for criteria to keep the item. For example, in the pickit, I should be able to specify to keep only rings with 20% chaos resistance or more.
[itemname] ring, [quality] = rare, [chaosres] >=204) Check town NPC inventory for specified items (shopbot) - six links, tricolor linked etc. Since the NPC inventory resets in 24 hours or when you level up, whichever is earlier, the shopbot will keep its own logfile and enter a timestamp when it last checked for the NPC items, and will also enter player's name and level, and date checked there. Next time you run the shopbot, shopbot checks to see its own logfile. If player level has changed, or timestamp is more than 24 hours old, then look for new NPC items, otherwise just kill shopbot.5) I don't want the bot to exit game and relogin. Instead, I want it to open a town portal, get to town, and then start a new instance. There is no reason it should relogin by exiting the game!
6) The ability to load "profiles" (e.g. one profile for daytime when I set it to pickup rares, and one for nighttime when it'll only pickup uniques and 6L etc). This actually would be the easiest thing to implement because it just needs the config files copied into the working folder.
7) (Redundant as pathing is now implemented): I understand pathing is under development. While the full pathing is implemented, you can at least have the bot use a "movement skill" in a fixed coordinate (e.g. use leap slam or lightning teleport). It's not the best solution, but it'll be something better than what we already have, and we don't have to wait for the full pathing to be invented and implemented.
8) The bot should keep track of number of mana / life flask uses per hour and number of chickens per hour. That way we will have an indication of how efficient is our current gear/skill setup in terms of killing vs dying.
9) As the bot is running, it should display "timers" (e.g. time since last kill, time since last movement, time for current game, total time of current botting session). That information could be useful to everyone. This is a feature request for next version when the bot will actually have an official GUI.
10) Live log: The bot keeps logs in a text file. It should also display the same thing in the status bar when it will have a GUI some day. This will be useful in monitoring errors in realtime rather than digging up the log file manually. For example, in the bot GUI status bar, it should display the last five lines of log (e.g. "started new game, trying to find new monster, exited due to not being able to find new monster")
11) Sometimes the bot clicks a story item (e.g. a wall graffitti or one of those large Karui heads). This keeps it occupied for several seconds. Can we have a "story detection" and click "continue" button in the story if detected? This actually happened with me three times today.
12) Sometimes the bot enters another area by mistake (I think it's the new pathfinder doing this) by the doorway at the entrance or exit of an area. If that happens, the bot should detect it, and we should be able to set an option either to continue in the "wrong" area, or use the entrance again to go back to the previous area.
13) When the bot encounters a rare monster with "Allies cannot die" mod, that monster should become the number one target, overriding everything else until the monster dies.
14) If the life is critically low, the bot should try using that "instant" recovery flask I specifically put there. If an instant recovery flask is not available or it's emptied out, then the bot should chicken. Basically this adds another layer of protection before chickening out, buying some more time to kill that tough monster.
15) Monsters with energy shield - there should be an option to use chaos-based damage on it. E.g. when encounter monster with energy shield, specifically use poison arrow instead of lightning arrow.
16) If the player is attacking, is moving position coordinates, but the hitpoints of the target monster are not going down, that means we could be desynched. In that case, bot should try issuing an /oos command in an attempt to resync it. This is what a "real" player would do, and our bot is trying to emulate a real player as the "gold-standard".
17) Follow mode: You can set the name of player to follow. The bot will accept party invitations from that player, and start following them whichever area they are in. The follow mode will also have an option to loot or ignore items dropped by killing monsters, and also another option to just follow passively (I'd do this just for auras) or to actively participate in combat. (Tip: Right now I'm able to have the bot follow me using a summoned monster - bot thinks the summon is killable, and he just follows my summon wherever I go )
18) Gem leveling: Set option to stop leveling a particular gem (e.g. Grace) after a specified level has been reached (e.g. do not level up Grace past level 12)
19) Cursing: Skip casting curse if there is 20) Gems whitelist: Pickup gems of quality >n, but always pickup these gems no matter the quality. e.g. portal gem.
21) xp/hour overlay, time to next level estimated, and playtime lost if you die at this moment.
22) Overlay clock, playing for how much time this session, and idle since x minutes.
23) Kill all unique bosses by default, but I should be able to add an option to ignore a particular monster (credits Madmayhem) e.g.
monster_ignore = Kole24) In skills.ini file, I should be able to increase the priority of a skill by x if my HP/mana/ES goes below n. (Credits Madmayhem)
25) When inventory full, stop picking up items and just play for pure xp, or logout.
WhenFullInventory = 1
; 1 = stop picking up further items except orbs
; 2 = logout
Thanks and great job to the developers.
