Exilebuddy Beta/Release Thread (2.4.0+)

Welcome to the Exilebuddy Release thread for 2.4.0+!

• Additional game patches are expected this week. Expect botting time to fluctuate.

Exilebuddy only supports the International version of Path of Exile (managed by GGG). Other version are not supported.

English is the only currently supported language.

Please start with the Support F.A.Q.. All support issues should go in the Support Forum. Please remember to attach a full log if you're in need of support.

Users will be compensated for the downtime once a Release version is ready. Once again, we thank users for their patience during this update process.

General

Path of Exile is a game that updates frequently. Please understand that the bot has to be updated each client update, regardless of how "simple" the patch might seem to be. We do not do automatic build and deploys for user safety. The bot will be updated as soon as possible when an update happens, but the timing and complexity of changes will have an effect on how soon a new build is made. If additional downtime is expected, we'll try to post a forum sticky to let users know as this happens.

Here are some relevant threads to be aware of:
[Official] Exilebuddy - Monthly Key System is now live
[Official] Exilebuddy - the Way Forward
Exilebuddy Roadmap Thread #1
Upcoming Downtime for 2.4.0

Default Bot/Routine

Please see the updated Getting Started (EN) guide in this thread.

Exilebuddy comes with a grind bot, a quest bot, and basic routine for users to bot with. For guides on these, please see the following links. They are pretty outdated now, but are still the best reference currently available.

QuestBot: Please see the new [2.4.0] QuestBot Guide/Support/Discussion thread.
OldGrindBot: Please see the old OldGrindBot Guide.
OldRoutine: Please see the old OldRoutine Guide.

Default Plugins

Exilebuddy comes with a number of default plugins that show API examples of how to perform various actions. Most of these plugins should be self-explanatory, but here are a few existing guides.
AutoPassives Plugin
AutoLogin Plugin
GemLeveler Plugin
ItemFilterEditor Plugin
Monoliths Plugin

Release Specifics

• The game is still undergoing updates to improve stability, so users should expect all sorts of client issues. Please babysit your bots!
• API support for a few things such as Passives, the Social Panel, and Event Notifications is still delayed, but will hopefully return in the near future.
• It is highly recommenced you play though the game yourself before attempting to bot. Otherwise, you'll run into a lot of issues not understanding how things work.
• A certain amount of "babysitting" is required with Exilebuddy. It is our goal to reduce this as much as possible, but it will take time and a lot of testing as the game continues to change.
• Botting hardcore leagues is not recommended.
• OldGrindBot is a basic grind bot. It is not meant to be used from level 1 and does not play though the game for you and do quests or master missions. If you choose to bot on low level characters that are under geared, the bot will struggle. This is the current design of the bot implementation we provide.
• OldRoutine is a basic routine that is designed around the idea of using a few skills based on mobs around the player. This design works for basic builds, but does not offer the customization required for more complex builds. While a new routine is planned, users should consider making their own build specific routines that takes advantage of the API to have something that caters to their needs.
• The game must not be minimized at any time for the bot to work. Windowed or windowed fullscreen tend to work best. Fullscreen is not recommended.
• Please enable "Always Highlight" in the PoE client UI options. If you don't the bot will have issues with some interactions.
• "Move Only" needs to be on your skill bar in a slot other than the Left Mouse Button.
• You should enable "Key Pickup" in the PoE client options so the bot doesn't click on random items.
• To avoid "gui overlap" please rebind middle and right mouse buttons and do not use a ranged skill on left mouse button.
• You should not leave the bot unattended in an area you have not botted before. Some areas work well, some do not. It depends on your build and the RNG of the map generation. Some areas have known issues that we cannot fix yet, because changing logic would result in other areas breaking.

Downloads

Beta
Release

Previous Release Threads:

Exilebuddy Beta/Release Thread (2.3.0+)
Exilebuddy Beta/Release Thread (2.2.1+)
Exilebuddy Release Thread (The Awakening 2.0.0)

 

Beta Changelog

#1561 [31 Jul 17 23:43] (2.6.3.5)

• Updates for 2.6.3.5.
• Updated error messages for when there's an issue getting offsets from the auth servers.

...

#1556 [20 Jul 17 06:21] (2.6.2.5)

• Updates for 2.6.2.5.

#1555 [13 Jul 17 23:55] (2.6.2.4)

• Updates for 2.6.2.4.

#1554 [21 Jun 17 02:54] (2.6.2.3)

• Updates for 2.6.2.3.
• [Cross-bot Settings]
  • Added "Vendoring" tab, providing following features:
    • Divination card exchange.
    • Currency exchange (Jewellers to Fusings and such).
    • GCP recipe (sell skill gems with total quality over 40).

#1552 [08 Jun 17 09:03] (2.6.2.2)

• Updates for 2.6.2.2.

#1551 [07 Jun 17 22:39] (2.6.2.1)

• Updates for 2.6.2.1.

#1550 [01 Jun 17 04:48] (2.6.0.18)

• Updates for 2.6.0.18.
• The stat used to detect Eldritch Battery has been fixed.
• AutoLogin updated to allow gateway selection again.

#1548 [24 May 17 04:59] (2.6.0.16)

• Updates for 2.6.0.16.

#1547 [23 May 17 23:23] (2.6.0.15)

• Updates for 2.6.0.15.
• Added a hotkey to open the settings window from inside the bot window (ctrl + tab)

#1546 [10 May 17 06:52] (2.6.0.14)

• Updates for 2.6.0.14.

#1545 [28 Apr 17 00:51] (2.6.0.13)

• Updates for 2.6.0.13.
• Various internal updates for improvements.

#1544 [24 Apr 17 04:01] (2.6.0.12)

• Updates for 2.6.0.12.
• MonolithComponent.IsCorrupted added and Monolith exposes it.
• ThirdPartyLoader updates to address the source zip file handle being kept open longer than intended.

#1542 [21 Apr 17 08:37] (2.6.0.11)

• Updates for 2.6.0.11.
• DevTab updated to use the same Roslyn code compiler ThirdPartyLoader does.
• Loki.Bot.RoslynCodeCompiler is now exposed so devs have access to runtime code compiling.
• The old AssemblyLoader and CodeCompiler have been removed from Loki.Common as they are not used anymore.

#1540 [19 Apr 17 03:34] (2.6.0.10)

• Updates for 2.6.0.10.

#1539 [16 Apr 17 17:10] (2.6.0.9)

• SelectCharacterState.SelectCharacter will now create a file, 'character-selection-debug.txt', when the character name cannot be found. This can be used to help debug name related issues.
• AutoLogin updates:
  • Added a new character list combobox that can be used to select a character to avoid typos.
  • Added a Refresh button to load the character list when on the character selection screen.
  • Upon the character list combobox change, the character to login with will be updated.
• ChatPanel updates:
  • ChatEntry.Sender is now ChatEntry.RemoteName to represent a client change. Outgoing messages no longer contain your name as the 'Sender'.
  • ChatEntry.Flag1 and ChatEntry.Flag2 added. These can be used to determine various types of messages.
    • For example, if Flag1 == 4 when MessageType == Whisper, then it's an outgoing whisper from you.
• Added command line support for 'log_path', which allows specifying a sub-folder in Logs for the current application.
  • For example EB.exe --log_path:"folder1"

#1537 [04 Apr 17 02:30] (2.6.0.9)

• Plugins that do not implement a GUI now show up on the settings window again.
• [MapBot]
  • Fixed an issue with bot crashing after entering a map if area loading was too long.
  • Fixed a rare issue when bot could stuck in infinite loop searching for Augmentation Orbs.

#1534 [01 Apr 17 22:45] (2.6.0.9)

• Loki.Common.TypeLoader updated to handle errors better.
• ThirdPartySettingsGui added to display current content loaded in the bot.
• LeaguestoneTask updates.
• Settings window updates: https://www.thebuddyforum.com/threads/upcoming-settings-window-updates.298755/
• PlayerEntry.IsOnline updated.
• AvalonEdit added.
• DevTab updates:
  • No longer has a default list of assemblies because all currently loaded assemblies are referenced.
    • This means all 3rdparty content is accessible from the DevTab, it just has to be referenced by namespace as per C# convention.
  • Code TextBox is now an AvalonEdit control to make the plugin actually usable for most people.
• ThirdPartyLoader updates for upcoming changes:
  • All existing content will still work as-is without changes.
  • ThirdPartyConfig class added to represent the new config format. This will be json de/serialized via "3rdparty.json".
  • 3rdparty.json file added to replace "3rdparty.txt" (AssemblyName), "3rdparty-required.txt" (Dependencies), and "3rdparty-files.txt" (FileList).
    • Only 3rdparty content that makes use of "3rdparty.txt" has been updated to use the new "3rdparty.json" format.
      • AreaVisualizer, AutoFlask, AutoLogin, AutoPassives, Breaches, Chicken, DevTab, ExternalCommunication, GemLeveler, GrindZoneChanger, ItemFilterEditor, Monoliths, ObjectExplorer, OldGrindBot, OldRoutine, Overlay, PythonExample, Stats, StuckDetection.
    • Other content will be updated later as breaking changes are required.

Archives:
You need to register and have one post to see spoilers!

 

Release Changelog

#288 [31 Jul 17 23:48] (2.6.3.5)

• Updates for 2.6.3.5.
• Updated error messages for when there's an issue getting offsets from the auth servers.

..

#284 [20 Jul 17 06:26] (2.6.2.5)

• Updates for 2.6.2.5.

#283 [14 Jul 17 00:00] (2.6.2.4)

• Updates for 2.6.2.4.

#282 [21 Jun 17 02:58] (2.6.2.3)

• Updates for 2.6.2.3.
• [Cross-bot Settings]
  • Added "Vendoring" tab, providing following features:
    • Divination card exchange.
    • Currency exchange (Jewellers to Fusings and such).
    • GCP recipe (sell skill gems with total quality over 40).

#281 [08 Jun 17 09:08] (2.6.2.2)

• Updates for 2.6.2.2.

#280 [07 Jun 17 22:44] (2.6.2.1)

• Updates for 2.6.2.1.

#279 [01 Jun 17 04:58] (2.6.0.18)

• Updates for 2.6.0.18.
• The stat used to detect Eldritch Battery has been fixed.
• AutoLogin updated to allow gateway selection again.

#278 [24 May 17 05:07] (2.6.0.16)

• Updates for 2.6.0.16.

#277 [23 May 17 23:28] (2.6.0.15)

• Updates for 2.6.0.15.
• Added a hotkey to open the settings window from inside the bot window (ctrl + tab)

#276 [10 May 17 06:57] (2.6.0.14)

• Updates for 2.6.0.14.

#275 [28 Apr 17 00:56] (2.6.0.13)

• Updates for 2.6.0.13.
• Various internal updates for improvements.

#274 [24 Apr 17 04:10]

• Updates for 2.6.0.12.
• MonolithComponent.IsCorrupted added and Monolith exposes it.
• ThirdPartyLoader updates to address the source zip file handle being kept open longer than intended.

#273 [21 Apr 17 08:46] (2.6.0.11)

• Updates for 2.6.0.11.
• DevTab updated to use the same Roslyn code compiler ThirdPartyLoader does.
• Loki.Bot.RoslynCodeCompiler is now exposed so devs have access to runtime code compiling.
• The old AssemblyLoader and CodeCompiler have been removed from Loki.Common as they are not used anymore.

#272 [19 Apr 17 03:44] (2.6.0.10)

• Updates for 2.6.0.10.
• SelectCharacterState.SelectCharacter will now create a file, 'character-selection-debug.txt', when the character name cannot be found. This can be used to help debug name related issues.
• AutoLogin updates:
  • Added a new character list combobox that can be used to select a character to avoid typos.
  • Added a Refresh button to load the character list when on the character selection screen.
  • Upon the character list combobox change, the character to login with will be updated.
• ChatPanel updates:
  • ChatEntry.Sender is now ChatEntry.RemoteName to represent a client change. Outgoing messages no longer contain your name as the 'Sender'.
  • ChatEntry.Flag1 and ChatEntry.Flag2 added. These can be used to determine various types of messages.
    • For example, if Flag1 == 4 when MessageType == Whisper, then it's an outgoing whisper from you.
• Added command line support for 'log_path', which allows specifying a sub-folder in Logs for the current application.
  • For example EB.exe --log_path:"folder1"

#271 [04 Apr 17 02:34] (2.6.0.9)

• Plugins that do not implement a GUI now show up on the settings window again.
• [MapBot]
  • Fixed an issue with bot crashing after entering a map if area loading was too long.
  • Fixed a rare issue when bot could stuck in infinite loop searching for Augmentation Orbs.
• Loki.Common.TypeLoader updated to handle errors better.
• ThirdPartySettingsGui added to display current content loaded in the bot.
• LeaguestoneTask updates.
• Settings window updates: https://www.thebuddyforum.com/threads/upcoming-settings-window-updates.298755/
• PlayerEntry.IsOnline updated.
• AvalonEdit added.
• DevTab updates:
  • No longer has a default list of assemblies because all currently loaded assemblies are referenced.
    • This means all 3rdparty content is accessible from the DevTab, it just has to be referenced by namespace as per C# convention.
  • Code TextBox is now an AvalonEdit control to make the plugin actually usable for most people.
• ThirdPartyLoader updates for upcoming changes:
  • All existing content will still work as-is without changes.
  • ThirdPartyConfig class added to represent the new config format. This will be json de/serialized via "3rdparty.json".
  • 3rdparty.json file added to replace "3rdparty.txt" (AssemblyName), "3rdparty-required.txt" (Dependencies), and "3rdparty-files.txt" (FileList).
    • Only 3rdparty content that makes use of "3rdparty.txt" has been updated to use the new "3rdparty.json" format.
      • AreaVisualizer, AutoFlask, AutoLogin, AutoPassives, Breaches, Chicken, DevTab, ExternalCommunication, GemLeveler, GrindZoneChanger, ItemFilterEditor, Monoliths, ObjectExplorer, OldGrindBot, OldRoutine, Overlay, PythonExample, Stats, StuckDetection.
    • Other content will be updated later as breaking changes are required.

#267 [16 Mar 17 02:34] (2.6.0.8)

• Updates for 2.6.0.8.

#265 [13 Mar 17 17:48] (2.6.0.6)

• MahApps.Metro updated to 1.4.3 from 1.4.0.
• Microsoft.Net.Compilers updated to 2.0.1 from 1.3.2.
• OGB work-in-progress Leaguestone updates:
  • Added OpenChallengesPanel.
  • Added a PreTransitionToArea coroutine that broadcasts the logic event, ogb_pre_transition_to_area. The event's parameter list is DatWorldAreaWrapper area, bool newInstance.
  • TakeClosestPortal minor logic updates to cover a possible rare case.
  • TakeAreaTransition, TakeWaypointTo, and TakeClosestPortal now await PreTransitionToArea.
  • OldGrindBot has some testing logic commented out related to leaguestone un-equipping between area transitioning.
• Added "Leaguestones" plugin which provides basic leaguestone usage on the Legacy league.
  • Users can set priorities and ignore leaguestones by name or affix in the plugin's gui.
  • Plugin also handles interaction with new NPC Yama the White/Generous, who spawns when corresponding leaguestone is active.
  • This plugin works only with new bots, OldGrindBot is unsupported.
• [EXtensions]
  • Fixed an issue with Perandus chests opening.
  • Added support for Essence and Divination stash tabs.
  • Added stashing option for Leaguestones.
  • Moved Prophecy stashing settings from individual currency to general.
  • Individual currency stashing settings are now all togglable instead of hard switch between all and individual currency.
• [MapBot]
  • Rhoa nest breaking is now a togglable option in the gui.
  • Fixed an issue when monster tracking logic could stick to Necrovigil or Divine Shrine mobs if they walked out of immunity aura and then re-entered it.
• [QuestBot]
  • Now QuestBot will open Eternal Laboratory waypoint after Gemling Queen quest on merciless difficulty.
• Added StoneAltarUi:
  • InventoryControl1 - InventoryControl5 added to work with each inventory slot.
  • Activate function added to summon the Talisman boss (does not check summon conditions, only if items are present).
• InventorySlot.Talisman added.
• InventoryControlWrapper.HasTalismanTabOverride added; HasCustomTabOverride will check it.
• CadiroOfferUi is accessible again.
• Various Dat updates to log when an access is made to a memory based ggpk entry that is not loaded in the client yet. For example, running DumpProphecies.cs on the title screen before having logged into the game would warn the Prophecies manager isn't loaded yet.
• A rare exception when accessing Dat entries when out of the framelock should now be avoided. This seems to randomly occur as of the latest game update.

#264 [09 Mar 17 16:28] (2.6.0.6)

• Updates for 2.6.0.6.
• InventoryControlWrapper.UseItem updated to support the Leaguestone slots on the Legacy UI.
• Updates for 2.6.0.5.
• Leaguestone.MinMonsterLevelSuffix and MinMonsterLevelPrefix added to reflect changes made. MinMonsterLevel now refers to the max of these two values.
• Leaguestone.MaxMonsterLevel updated to return level 100 if no max is set.
• Item.IsRelic added to identify Legacy League Relics.
• ChallengesUi updates:
  • InventoryControl_Leaguestone1, InventoryControl_Leaguestone2, and InventoryControl_Leaguestone3 added to refer to each inventory control on the Legacy UI.
  • IsLegacyTabVisible added to know if the legacy tab is visible or not. If it's not, then the legacy related APIs shouldn't be used.
  • IsLegacyTabSelected added to know if the legacy tab is currently selected or not. If it's not, then the legacy related APIs shouldn't be used.
  • SwitchToLegacyTab added to switch to the Legacy tab.
  • IsLeaguestoneUnlocked added to see if a slot is unlocked or not (or, devs can just check player level against the thresholds)
• InventoryControlWrapper.UseItem updated to allow using Leaguestones from the Main inventory only.
• InventoryControlWrapper.HasLeaguestoneTabOverride added; HasCustomTabOverride will check it.
• GemLeveler updates to try and handle the level skill gem hud changes (icon disabled on skill use).
• Added the Leaguestone item class object.
  • CurrentCharges / MaxCharges returns the respective charge count.
  • MinMonsterLevel / MaxMonsterLevel returns the level range the item can apply to.
  • AppliesToCurrentAreaByLevel returns if the item is usable in the current area by level criteria only.
• The function ChargesComponent.GetMaxCharges was added for non-flask items like Leaguestones.
• InventorySlot updates:
  • InventorySlot.Sell removed because it doesn't map to a correct value anymore.
  • InventorySlot.Leaguestone added to refer to the legacy leaguestone inventory.
  • Added ArmourersWorkbench, SharpeningWheel, BowmakersTools, ArtisansBench, Headstones, and BlessingFont to refer to Master device inventories.
  • InventorySlot.PassiveTreeJewels added to refer to equipped passive tree jewels.
• The new chest, Relic Vault, was added to OldGrindBot's chest settings to be opened by default.
• ItemFilterEditor now has a default Leaguestones pickup filter. Existing filters will need to manually match this type.
• Item.IsLeaguestoneType added to match items with the metadata "Metadata/Items/Leaguestones/". This will not match the "Mystery Leaguestone" item which is a currency item.
• Item.IsMysteryLeaguestone added to match the "Mystery Leaguestone" currency item type.
• CreateCharacterState.SelectLeague updated to CreateCharacterState.SelectLeagueEx to reflect the changes in supporting SSF leagues.
• Added the CheckForTrialOfAscendancyStuckTask to OGB.
• Updates for 2.6.0.4.
• Updates for 2.6.0.3.
• Updates for 2.6.0.2.
• Updates for 2.6.0.1.
• Known Issues:
  • SocialUi.InviteToParty can now fail due to the panel being scrolled down as it's no longer a footer gui element.
  • ChargesComponent logic might need to be reworked since non-flash items can have charges now.
  • Obstacle placement for Trial of Ascendancy doors seems to break more now.
  • Skill gem level up icons disable in the client after skill use.
  • Client auto-interacts when LMB is held while moving.

You need to register and have one post to see spoilers!

 

Getting Started (EN)

Getting Started (EN)

Run "ExilebuddyBETA.exe".

For fast access to Support, please click on the "Support" text in the top right corner of the GUI. In order to receive support for Exilebuddy, you must have bought your key from exilebuddy.com. You should be able to see the key you purchased through the BuddyAuth key page. If you use any 3rd party patchers or keys not originating from us, you may experience crashes, or other broken behavior. We will not be able to help you with your problems in those cases. If you encounter any bot crashes, you will need to attach a full, unedited log. You can find your logs in the Logs folder of Exilebuddy.

Pre-requisites
You need to register and have one post to see spoilers!
Client Settings
You need to register and have one post to see spoilers!
Step 1: Language Selection
You need to register and have one post to see spoilers!
Step 2: Configuration Selection
You need to register and have one post to see spoilers!
Step 3: Update
You need to register and have one post to see spoilers!
Step 4: Login
You need to register and have one post to see spoilers!
Step 5: Process Selection
You need to register and have one post to see spoilers!
Step 6: Main Window
You need to register and have one post to see spoilers!
Step 7: Settings Window
You need to register and have one post to see spoilers!
Hotkeys
You need to register and have one post to see spoilers!
Misc
You need to register and have one post to see spoilers!

 

***** Detection Awareness

***** Detection and You

On January 11, 2015, patch 1.3.0.14 (1.3.0i) was deployed. This patch contained what appeared to be an unannounced ***** detection system for Path of Exile. This would be the first client-sided ***** detection system ever used in the game, so an updated build of Exilebuddy was not pushed that day, and an announcement thread was made to notify users of the downtime. When it was absolutely clear what was added to the client, and conclusive proof backing that was obtained, a second announcement was made to let users know why there would be additional downtime. We are now ready to move forward with the next version of Exilebuddy, but before we do, there's some important information for users to know.

On July 9, 2015, a new variant of this system was first deployed on the CBT realm, and is now a part of the Release realm. This resulted in additional downtime for Exilebuddy past the original expected release date. While Exilebuddy was already down for maintenance, people *****ing did in fact get detected and banned. While downtime is frustrating, user security is a high priority, and we'll do our best to ensure Exilebuddy is as safe as possible amidst this.

During our downtime, a lot of information has been posted on other forums about the ***** detection system Path of Exile now uses. We cannot comment on others' research, observations, or speculations in relation to how it might/might not affect Exilebuddy. Based on the information available to us, we've made changes to Exilebuddy necessary to provide the safest possible means of botting.

This presents an important issue for users to understand: the continued use of any unauthorized 3rd party software developed without consideration for the new ***** detection system puts your account at additional risk. The following actions are examples of things that can result in your account being banned (at GGG's discretion):

• Loading unauthorized modules into the Path of Exile process space [DLL injection].
• Any Path of Exile code section modifications [Client modding].
• Running unauthorized 3rd party software that interacts with the client [Auto-pot, overlays, etc...].
• Allocating memory in the Path of Exile process [Hooks, detours, non-module based stuff, etc...].

As it stands, Exilebuddy is as safe as we can get it, so no other changes to improve its security can be made until the ***** detection changes (which we expect it to as time goes on). It is the user's responsibility to ensure they are not doing anything prohibited by GGG that will be detected by the ***** detection and thus result in their account being banned. We do expect ban reports to increase as a result, but we understand enough about the new system in place to ensure users Exilebuddy is as safe as possible, and there's nothing else to be changed.

Client Updates

During our downtime, we've made some new tools to help assist us with future client updates. Unfortunately, we need to be extra careful with each patch from here on out to try and avoid releasing an update that causes the bot to be detected by the ***** detection. As a result, each patch will most likely see additional downtime, but we'll try to have EB up and running as soon as possible. When there are ***** detection updates, or other changes that affect the bot, we'll most likely not talk about it unless it's something entirely new and users need to be made aware of it.

Running Exilebuddy

Users must now rename Exilebuddy.exe/ExilebuddyBETA.exe to another random name of their choice to run Exilebuddy. We're sorry for this inconvenience, but it is now necessary with the ***** detection system in place. Since Exilebuddy supports command line arguments, and users have various programs and scripts in which they need to know the exe name, we cannot generate a random name at runtime and relaunch the bot.

In addition, please rename the folder you extract Exilebuddy to as well. The bot will not launch if "Exilebuddy" is in the last path part.

For example:
"C:\Users\MyUser\Downloads\ExilebuddyBETA 0.1.2.3" - Bad
"C:\Users\MyUser\Downloads\EB-qwerty" - Fine (but don't use public examples)

This is required simply as a precaution.

 

Client Telemetry in 2.3.3+

2.4.0: Telemetry system still exists, but has been inactive for a number of updates. This post is simply for reference.

This thread is to inform users of the new client telemetry feature added in 2.3.3.1.

On joining a new area, the client will now start to collect some telemetry data. This data is then sent to the PoE website when you leave the area.

Here's an example of what the telemetry data contains, where "(-)" are strings I manually removed.

You need to register and have one post to see spoilers!
There is no way to opt-out of this system currently, and the client doesn't save the reports to disk for users to verify the info, so please be mindful of this and how it might possibly affect you.

Generally speaking, there's nothing here that directly affects Exilebuddy, but users running extremely low FPS or trying to run game resolutions not officially supported (EB doesn't support either case officially anyways) should be mindful that info is now being reported.

Thank you for reading!

 

Monoliths Plugin

A new plugin has been added for the Essence League! The Monoliths plugin allows users to selectively interact with these objects to spawn the enemies.

You need to register and have one post to see spoilers!
By default, the plugin is disabled, so users need to enable it. Once he plugin has been enabled, the user can enable/disable the logic from running with the "Enabled" option without having to stop the bot and disable the plugin each time.

The "Open" setting tells the plugin if the bot should actually open the monolith or simply move to it. This is useful for simply finding monoliths, or debugging other issues. The bot will not stop though, but rather stand around the monolith, so if any enemies come, the bot will still respond.

The "Minimal/Maximum" Essences settings allow the plugin to skip Monoliths with too few, or too many essences on them.

The plugin uses metadata matching (for future localization support) to match the Essence and monster types. Use the DevTab plugin to dump BaseItemTypes and Monsters to get a list of everything in the game.

Whitelist settings tell the plugin which Monoliths should be considered for opening. By default, all Monoliths are included with a broad Essence/Monster filter.

Blacklist settings tell the plugin which Monoliths should be removed from opening from the pool of objects the whitelist settings found. By default, nothing is blacklisted.

For example, to only open Monoliths with a particular type of essence, the WhitelistEssenceMetadata filter would be changed to those Essences. The default blacklist would remain untouched.

To not open a Monolith with a specific type of monster, the default whitelist would remain the same, but a new metadata entry for the monster would be added to the blacklist.

Users that simply want to open everything won't have to touch settings. The community can come up with sets of filters that work best for various classes or builds, as always.

NOTE: Monolith logic uses post_combat_hook, which means it'll execute before looting and opening chests. This is by design for now, as there's no other common way to make it work between any bot implementation without relying on new tasks.