Download - Please download a clean copy of Beta for each version. Do not "update", because the changes will break other versions. Before reporting issues, please make sure you are using a clean copy. Please attach a full log if you have any problems. I've made sure as much debugging information is logged as possible to track down various issues that might happen. I need the full log though, and not partial snippets. If you do not feel comfortable posting a full log, you can PM me it instead with a link to your thread. Beta #890 - Overview 1. Please place the "Move only" skill on your skillbar, but not in Left Mouse Button. 2. Make sure "Always Highlight" is enabled (PoE Options-> Ui or press Z) 3. Make sure "Key Pickup" is enabled (PoE Options-> Ui) Most of today's work was working out the changes needed to get waypoint data correct again and checking into why new instances aren't being made. While at it, support has been added for the Eternal Laboratory and your Hideout if you have one. There does exist a chat command to take your to your hideout in town, but there's no wrapper functions for performing that action yet. In addition, the TagWaypointTask has been added to the BasicGrindBot (something the last beta had), so the bot will grab waypoints in new areas. Please remember the bot still doesn't have some early quest processing yet, so it won't do the mud flats quest for you. Support for things like that, the local area transitions to get into bosses, and other fun things like that are on the todo list, but after most of the bigger issues are taken care of first. The CR has some minor changes, but once again, priority right now is working out API issues and fixing the largest post 1.2 issue with memory going bad in the CR. Upcoming changes include plans for a simple targeting system so users can prioritize targets like before, adding in grid tracking so the CR can clear all mobs, and some additions to skill logic. Aura logic now has much longer delays between casting in a hope to fix the issues reported with it casting over and over. I'm not sure why it's only happening for some people, but we'll see if this helps or not. Changelog: Updates for 1.2.1.3 AlertPlugin added, as it'll be useful to more people this way. Added TagWaypointTask. The bot will now grab a waypoint for the current area if it doesn't have it. Copy/paste fixes for AlertBot. Fixed a GUI bug where disabled plugins still had their settings shown. AreaStateCache now correctly uses WorldPanel.AvailableWaypoints. WorldPanel.AvailableWaypoints returns all areas on the world panel with waypoints, and an associated waypoint data object that tells if the waypoint is unlocked. Added the start of DualTotemRoutine. Added new offsets required. WorldPanel now returns the correct waypoints. WorldPanel.GoToHideout added. The Eternal Laboratory is now supported in TakeWaypoint. SkillBarPanel.Slot updated to use the skillbar rather than GUI, so it should not have as much overhead compared to before. Input.PressKey(Keys.ControlKey); calls removed. Logic error in EscapeState.ExitGame fixed. InteractWith now has some extra debugging to track down control key issues. Quick Guide The current bot is still under work to try and achieve a bare minimal grinding/town run implementation. Certain quality of life features are not in it yet. Additional features, such as iding items, selling, have not made it back in yet, but will be added later if the current build is working noticeably better for users. There exists one more big thing to work around for the post 1.2 changes. That is the error where memory goes bad when the CR Go to the "Settings" tab in the main GUI. From here, you can change "BasicGrindBot" or "ExampleRoutine" settings. Currently, you can only select the grind zone for "BasicGrindBot". The bot can now navigate though towns, so as long as you have the appropriate quest state to reach an area, the bot should make it. After the bot finishes the grind zone, it will take area transitions back and forth for new instances until it needs to go to town. The bot does not have any quest logic, and does not know that you are or aren't able to use an area transition, so if you grind an area that you don't have all the quests done for, it can and most likely will get stuck. Hover over the GUI labels in "ExampleRoutine" to understand what each setting is for. Your "Left Mouse Button" slot, the top left most one, is slot 1. Your "T" slot, second row, far right, is slot 8. Simply assign the slot #s to the skill category that you want to associate each skill with. The CR has a specific set of logic for determining when a slot is used. Users must make their own specialized CRs if they need different logic or behaviors. Our CR is just one big example of doing a bunch of different things, so it will never be able to do everything, nor could we maintain such a CR in a game like this. A quick run down about how the default CR is currently designed, as there was some confusion with the previous version. This CR offers a generic way of trying to support as many "generic builds" as possible that make use of multiple skills under different combat scenarios. It allows for the use of multiple auras, curses, and one totem. If you assign a skill that is auto-used by the CR to a skill slot, it will be spam cast, and not work correctly, because casting such skills require additional logic not coded into the skill slots themselves. Single Target Melee Skill Slot is used when there is a single target or boss-like mob in melee range. Single Target Ranged Skill Slot is used when such a target is outside of melee range. Aoe Melee Skill Slot is used when there are numerous mobs around the player. Aoe Ranged Skill Slot is used when such mobs are outside of melee range. If you do not need a specific behavior, selecting -1 will make the bot not use a skill under that scenario, but a skill will always be used. For example, if you only set Single Target Melee Skill Slot, that slot will be used for all other conditions automatically if the are unassigned. The CR for this version contains some changes to address some of the main issues people have noticed. The CR will now skip more mobs that lie outside combat range to avoid various issues with looping back and forth. This is purely a CR behavior, and if you use a custom CR or modify ExampleRoutine, it can be changed. The CR does not have target priority yet, so there are several combat cases involving necros where it can get stuck. Since the bot is not in an afk-able state yet, this isn't a huge deal, and it's strongly advisable to babysit your bot for the time being as things are still getting worked out. In addition, the CR does not handle desync or other cases where the skill it's casting fails to hit the target (due to game mechanics). Known Issues The bot doesn't have a stuck detection plugin yet, so there are some areas where stuck issues might be more common than others. The City of Sarn has some known issues with the bot hugging the wall and getting stuck. Adjustments to the pathfinding for this area and some others are still on the todo list. There is still a potential exception issue for when objects go invalid and the CR tries to process them. This typically results in the bot being stopped and the character logging out to the character selection screen. This issue is currently being worked on, but it's not an easy fix, so it'll take some time before it's solved for good. Other than that, any issues with the CR are just CR issues from it being a large generic example. The BasicGrindBot implementation does not handle any combat issues itself. Right now, not much time can be spent on trying to get the CR expanded for more things, because that's not its goal. Certain skills have not been added to the CR yet. Trying to get them all will be considered, but for now, as long as most are used correctly, adding in others is just a task that takes time.
I think this has been like this from 1.2 beta release but I just found out that bot doesn't pick up quality gems on default item filter setting. I had to change maximum quality to 20 in setting in order for bot to pick it up. Not sure if i was the only one who didn't figure this out, but just wanted to share with everyone
After last update the bot got a problem with range attack. I use melee skills but sometimes ranged targets isn't close enough to hit them.
Same here, when bot finds ranged monsters he tries to hit them with melee without getting close to them. A workaround is to lower the combat range so it will simply skip them, or move and get closer.
Sometimes when the instance is clear, it run to an exit point and when the bot must reset the instance its just port back without reset the previous one and start running again its need to reset it manually. For example im running in Lunaris Temple 2, if the bot find exit Lunaris Temple 1 when its complete the Lunaris Temple 2, it can reset the map, but when its find as exit to Lunaris Temple 3, the bot doesn't reset the instance he just run to previous one. Also the bot doesn't open Strongboxes - White - Blue - Gold in this area. But sometimes it open a Blue, dunno why its happen. Edit: I forgot to say that sometimes the bot ignore Masters NPC's and sometimes is not.
I use Infernal Blow (close attack) and this version is very VERY bad at it. It starts attacking 1-2 meters away from the monsters, not biggest problem is monsters also is melee, but caster/range mobs dont come close. so the bot just stands there spamming my melee attack. and gives this error: [Logic] UseAt returned InvalidSlot. [Logic] UseAt returned InvalidSlot. [Logic] UseAt returned InvalidSlot. [Logic] UseAt returned InvalidSlot. [Logic] UseAt returned InvalidSlot. I added my log View attachment Exilebuddy 981720 2014-09-03 10.34.txt I added a screenshot so you can see how far away it is: It just stands there attacking in the air
Fixed, thanks for reporting. I made the default filter just pickup all skillgems, to avoid issues of having to keep names up to date, and I left in the MaxQuality check.
There is an issue with your CR config then. Please post how you have it setup, and i'll get you pointed in the right direction.
Code: [Tick] Exception during execution:Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> System.Exception: GuessTownExitLocation called when curArea = 3_3_town for exit The Upper Sceptre of God Loki.Bot.Logic.Bots.BasicGrindBot.TravelToGrindZoneTask.(String ) Loki.Bot.Logic.Bots.BasicGrindBot.TravelToGrindZoneTask..() When I set the grindzone to be upper god, and start the bot at barracks, it takes town run and then these error comes out.
Try this: https://gist.github.com/anonymous/0587de7b32d4054895a1 Exit the bot, delete the old ExampleRoutine.cs, make a new ExampleRoutine.cs file with those contents, then try again.
I'll need a full log please. Basically, your area change took long enough for the bot to not handle it correctly.
This worked pushedx. Also I solved my problem from before where it would stick hovering over the flask area by turning my combat range down further to 50. So now all is working as it should now to get hideouts and selling working
sloved, it seems I need to unlock the door the sceptre of god first. And I got another little problem that the door lock "EpicDoor" can't be interact with bot correctly, the log is like Code: [Myplugin] Now attempting to interact with the Metadata/QuestObjects/EpicDoor/EpicDoor. [InteractWith] Now attempting to highlight 27681. holdCtrl = False. [InteractWith] The target 27681 could not be highlighted. have tried both the coroutines way and clickMLB() need more test though... Sorry for having no fulllog, I restart the bot so often that it's hard to find them.
Is your Always Highlight setting enabled? If it is, and you still can't interact, I'll go check that object to figure out why it's not targeting it correctly.
