Exilebuddy Release Thread (1.3.0.15+)

About

On January 11, 2015, patch 1.3.0.14 (1.3.0i) was deployed. This patch contained what appeared to be an unannounced cheat detection system for Path of Exile. This would be the first client-sided cheat 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.

Cheat Detection and You

During our downtime, a lot of information has been posted on other forums about the cheat 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.

Exilebuddy does not currently modify Path of Exile's cheat detection in any way, shape, or form.

This will remain the case until we are forced to, but no further notifications of this will be made. However, this presents an important issue for users to understand: the continued use of any unauthorized 3rd party software developed without consideration for the new cheat 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 at the same time Path of Exile is running (regardless if it interacts with the client or not) that has a specific process name or window title [Known cheating programs]
• 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 cheat 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 cheat 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 cheat 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 cheat 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 cheat 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.

Download

Please be sure to check the Changelog section below!

Release

Beta

Changelog

The old Exilebuddy Release Thread (1.3.0) is still relevant in terms of bot information, but will no longer be updated with changes.

Release

#91 (1.3.0.17) [23 Jan 15 03:08]

• Beta #989.

#90 (1.3.0.17) [22 Jan 15 04:53]

• Beta #988.

#89 (1.3.0.16) [21 Jan 15 06:49]

• Beta #982 - Beta #987

Beta

#992 (1.3.0.17) [01 Feb 15 14:52 ]

• HasAura bug fix; the previous version was accidentally changed to check LokiPoe.Me, whereas it should check 'this'.

#991 (1.3.0.17) [30 Jan 15 22:13]

• BuddyAuth/Greymagic updates.
• DatWorldAreaWrapper.MonsterLevel added to expose the level for an area.
• The DumpWorldAreas script now includes the monster level.

#989 (1.3.0.17) [23 Jan 15 02:58]

• BuddyUpdater is now launched with a dynamic window title.
• Added Logger.OpenLogAndExitProcess.
• An experimental startup optimization is being tried in BETA builds, courtesy of Apoc.

#988 (1.3.0.17) [22 Jan 15 04:42]

• Updates for 1.3.0.17.

#987 (1.3.0.16) [21 Jan 15 06:38]

• The Exilebuddy process name should no longer be logged. If it appears from other error messages, please report it and it'll be censored out. Please remember to rename your Exilebuddy exes on a regular basis.

#986 (1.3.0.16) [20 Jan 15 07:00]

• Updates for 1.3.0.16.

#985 (1.3.0.15) [19 Jan 15 12:29]

• Exilebuddy will now instantly close if the last directory name part contains 'exilebuddy'. An error is logged, and the log file is started to tell users to rename the directory for their security.

#982 (1.3.0.15) [19 Jan 15 06:12]

• Updates for 1.3.0.14/15.
• Added InGameState.IsPvpOnlyOverlayOpen and InGameState.AcceptPvpOnlyWarning. These are to know when the overlay is opened from talking to Leo the first time, and a function to close it.
• Added the setting, DisableDoNotDisturbOnBotStop.
• All window and message box titles have a dynamic element to them.
• Exilebuddy will now instantly close if the process name is exilebuddy or exilebuddybeta. An error is logged, and the log file is started to tell users to rename the process for their security.
• LogStartupInfo is now called at app init rather than after login. This should help identify OS issues sooner.
• Various improvements to GreyMagic to help avoid some potential issues in the future.

 

We are adding 14 days to all keys to thank you for your patience and support during this downtime.