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.
New user guides have been made that contain all the up-to-date information regarding Exilebuddy. They will be opened for discussion "soon", but are being updated as needed based on Beta changes. I know it's a lot to read, but please read them before asking general questions as they should contain all the information you need to know. If anything is missing though, I'll get it added.
Exilebuddy Project Guide - Read this for an overview of the Exilebuddy project.
Exilebuddy User's Guide - Read this for an overview of how the Exilebuddy GUI is setup.
BasicGrindBot Guide - Read this for an overview on how BasicGrindBot works.
ExampleRoutine Guide - Read this for an overview on how ExampleRoutine works.
Exilebuddy Plugins Guide - Read this for an overview about the plugins that come with Exilebuddy.
Beta #915
This version should fix the two main issues with the TravelThoughBossArea task.
Changelog
Beta #914
This version contains the bulk of the remaining changes to Beta. Almost all the fixible known issues have have been addressed with these changes. There are certain issues that will have to remain unfixible for the foreseeable future. More information about those will come with the official stable Release for 1.2.
The largest change is the removal of Functions.MoveTowards in favor of the PlayerMover class (as we had before). The idea behind the PlayerMover is to allow users to implement custom moving. If you want to use leap Slam for movement, you could write a new IPlayerMover and use that skill to move when applicable. Likewise for other things such as Whirling Blades or Lightning Warp. Using skills such as those does come with a lot of desync or other issues, so it's your job to work though those if that's what you really want.
A lot of new plugin examples have been added for users to reference to. Most of these were present with the previous Beta, so they are being included again for users to get an idea of the possibilities with Exilebuddy. The new plugins guide gives a brief overview of everything, but users should reference the code or ask when in doubt before using plugins they do not understand. If you're going to use the AutoResync, I'd strongly suggest not trying to bot too much unattended, as /oos commands are tracked by the server and prolonged use might make your account stand out more than a normal player who doesn't play nearly as long.
As many issues relating to low FPS as possible have been addressed, but low FPS will not be officially supported. However, using the new plugin to change settings, the bot should at least be usable for movement compared to before. The stuttering in town cannot be fixed, so it's advisable not to do town runs under low FPS since it'll look bot like. There is a minimal FPS required though, as anything under 10 FPS affects the bot/client too much, but FPS between 10-30 should mostly work 'ok'. No other changes can be made to improve lower FPS support, so this is as good as it'll be (unless you try writing your own bot code to use instead).
Various bugs mentioned should now be fixed as well. The boss area logic has been updated to process multiple locations to avoid getting stuck at corrupted area transitions. The act 3 town issue when using Clarissa has been fixed by simply not using her to stash. The issue where the bot tries to open a locked strongbox has been fixed by checking for the locked chest property. CRs should implement logic for killing all of the special strongbox monsters for better support as well. In certain areas, these monsters spawn across many rooms or run far away, so there are cases where the bot might miss a strongbox opening.
Lastly, the ability to read the quest tracker entries has been added to the API for users interested in trying to work with missions. This allows users to work with the current state of missions, as otherwise, there is no way to figure out what needs to be done as missions aren't included in the normal quest system (just a generic mission state, no specifics).
Changelog
Known Issues
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.
New user guides have been made that contain all the up-to-date information regarding Exilebuddy. They will be opened for discussion "soon", but are being updated as needed based on Beta changes. I know it's a lot to read, but please read them before asking general questions as they should contain all the information you need to know. If anything is missing though, I'll get it added.
Exilebuddy Project Guide - Read this for an overview of the Exilebuddy project.
Exilebuddy User's Guide - Read this for an overview of how the Exilebuddy GUI is setup.
BasicGrindBot Guide - Read this for an overview on how BasicGrindBot works.
ExampleRoutine Guide - Read this for an overview on how ExampleRoutine works.
Exilebuddy Plugins Guide - Read this for an overview about the plugins that come with Exilebuddy.
Beta #915
This version should fix the two main issues with the TravelThoughBossArea task.
Changelog
- TravelThroughBossAreasTask should now clear the previous location to avoid getting stuck near corrupted area transitions.
- TravelThroughBossAreasTask now attempts to reset logic after death to handle issues in boss areas where the character is placed in previous areas.
Beta #914
This version contains the bulk of the remaining changes to Beta. Almost all the fixible known issues have have been addressed with these changes. There are certain issues that will have to remain unfixible for the foreseeable future. More information about those will come with the official stable Release for 1.2.
The largest change is the removal of Functions.MoveTowards in favor of the PlayerMover class (as we had before). The idea behind the PlayerMover is to allow users to implement custom moving. If you want to use leap Slam for movement, you could write a new IPlayerMover and use that skill to move when applicable. Likewise for other things such as Whirling Blades or Lightning Warp. Using skills such as those does come with a lot of desync or other issues, so it's your job to work though those if that's what you really want.
A lot of new plugin examples have been added for users to reference to. Most of these were present with the previous Beta, so they are being included again for users to get an idea of the possibilities with Exilebuddy. The new plugins guide gives a brief overview of everything, but users should reference the code or ask when in doubt before using plugins they do not understand. If you're going to use the AutoResync, I'd strongly suggest not trying to bot too much unattended, as /oos commands are tracked by the server and prolonged use might make your account stand out more than a normal player who doesn't play nearly as long.
As many issues relating to low FPS as possible have been addressed, but low FPS will not be officially supported. However, using the new plugin to change settings, the bot should at least be usable for movement compared to before. The stuttering in town cannot be fixed, so it's advisable not to do town runs under low FPS since it'll look bot like. There is a minimal FPS required though, as anything under 10 FPS affects the bot/client too much, but FPS between 10-30 should mostly work 'ok'. No other changes can be made to improve lower FPS support, so this is as good as it'll be (unless you try writing your own bot code to use instead).
Various bugs mentioned should now be fixed as well. The boss area logic has been updated to process multiple locations to avoid getting stuck at corrupted area transitions. The act 3 town issue when using Clarissa has been fixed by simply not using her to stash. The issue where the bot tries to open a locked strongbox has been fixed by checking for the locked chest property. CRs should implement logic for killing all of the special strongbox monsters for better support as well. In certain areas, these monsters spawn across many rooms or run far away, so there are cases where the bot might miss a strongbox opening.
Lastly, the ability to read the quest tracker entries has been added to the API for users interested in trying to work with missions. This allows users to work with the current state of missions, as otherwise, there is no way to figure out what needs to be done as missions aren't included in the normal quest system (just a generic mission state, no specifics).
Changelog
- LokiPoe.InGameState.QuestTrackerEntries added for users to process mission quests, which are not a part of the normal quest system.
- Added a new GemLeveler plugin example using the new API.
- SortInventoryTask moved after HandleInventoryItemsTask to avoid double sorting.
- Added a ChaosChanceRecipe plugin example showing adding more complex functionality.
- AutoResync will wait a full delay before auto-syncing, and reset on new areas, so /oos isn't triggered right away.
- OpenChestTask now checks for locked chests first.
- MinTimeBetweenResyncMs can only be set >= 10000.
- Added BasicGrindBotSettings.EnableEarlyExplorationComplete and ExplorationCompletePercent for preventing full explores of an area.
- ExplorationCompleteTask now exposes a static Completed event handler that is called when exploration has been completed.
- GrindZoneChanger plugin example added.
- AutoResync will stop triggering past 30m in an instance.
- AutoResync plugin example added.
- WaitForStashTabContents updated to try and detect slow loading pages that otherwise cause exceptions to be thrown. Removed InGameState.WaitForStashTabContents.
- Added UnblockCorruptedAreaTransitionTask, which uses Loose Gate and Sarcophagus blocking area transitions.
- SellItemsCoroutine now only uses weapons vendor in act 3 to avoid issues moving from accessories to stash.
- AreaStateCache now stores a list of static locations with the same name.
- StaticLocations is now a List<Vector2i> rather than a Vector2i.
- TravelThroughBossAreasTask updated to hopefully avoid issues with corrupted area transitions in The Upper Sceptre of God.
- Added a LowFpsHelper plugin to assist users who try to run lower FPS.
- LokiPoe.LowFpsMode has been added to help address some issues with low FPS settings. Low FPS is not officially supported, and there are some aspects of the API that are affected by it in unfixible ways, but the biggest issue has been identified with movement and a workaround added.
- ExilePather.GetPointsOnSegment, ExilePather.Raycast, and ExilePather.FindPath now take LokiPoe.LowFpsMode into consideration to not leave the framelock to perform pathfinding operations. ExilePather.WalkablePositionFor is an expensive function as it is, and is not meant to be called a lot, so it does not check the flag.
- ResurrectTask will now try to resurrect one more time for each mode before giving up.
- PlayerMover class added. IPlayerMover is the interface used to change movement.
- Functions.MoveTowards -> PlayerMover.MoveTowards.
- DualTotemRoutine is not included anymore, as it was just to test a concept, and is not usable.
- SkillGem.Level is now an int instead of uint.
- Tooltips updated for ExampleRoutine ranges.
- Vaal auras are excluded from normal aura logic in ExampleRoutine.
- DominusFight plugin no longer executes when not in an overworld area.
- Settings helpers removed in favor of a generic versions, SetSettingsDelegate and GetSettingsDelegate.
Known Issues
- Exceptions thrown from the CR due to memory going bad.
- Lack of support for skills granted though items.
- Various chest opening issues in Docks.
- Movement issues in City of Sarn.
- Various stuck issues behind large chests/strongboxes or various tents in Act 2.
Last edited:
