• Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Exilebuddy Release Thread (1.3.0)

    Discussion in 'Archives' started by pushedx, Dec 14, 2014.

    Thread Status:
    Not open for further replies.
    1. pushedx

      pushedx Moderator Moderator Buddy Core Dev

      Joined:
      Sep 24, 2013
      Messages:
      4,252
      Likes Received:
      290
      Trophy Points:
      83
      Welcome to the Exilebuddy Release thread for 1.3.0!

      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.

      All current guides for Exilebuddy are now in the Exilebuddy Guides section.

      If you're new to Exilebuddy, it is highly recommend you read over the posted guides and stickies multiple times before diving into Exilebuddy. For existing users who have been following the Beta, the guides and stickies contain some additional information that is worth checking over again.

      1.3.0 specifics

      This section will briefly go over known 1.3.0 issues.
      • Botting hardcore leagues is not recommended. It is possible there are new mechanics in the league that are not handled yet, so your character will most likely die if you are not watching it and are unable to help it out in time. Please report any instances of this, but short term leagues are not fully supported.
      • BasicGrindBot 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.
      • ExampleRoutine does not seek out and destroy mobs. This is how it's designed. Tormented Rogues tend to run away, so if you don't kill them fast enough, it's most likely the bot will not follow it to kill it, since the routine does not tell it to. Users must make their own changes to make their routines track down and kill mobs that only last a limited amount of time.
      • The new skills have not been tested, and any new mechanics involving them, such as minion clones, are not supported at this time. As time goes on, we'll look into ensuring fully support for as many skills as possible, but for now, the new skills are use at your own risk.
      • The instance manager has changed some in 1.3.0. As a result, new code is being used for it. While it seems to be working correctly from our tests, please be on the lookout for any issues when it comes to bot being at the Instance Manager GUI.
      • Please remember to dump new game files for 1.3.0 rather than using old versions. Please see the "The "Dev" Tab: Runtime Development Using CodeDOM" guide to do so.

      Versions

      Release

      #88 (1.3.0.14) [Next Version]

      #87 (Poe 1.3.0.11) [29 Dec 14 08:43]
      • Beta #976 - #978

      #86 (Poe 1.3.0.7) [23 Dec 14 04:50]
      • Beta #975

      #85 (Poe 1.3.0.6) [22 Dec 14 05:50]
      • Beta #974

      #84 (Poe 1.3.0.5) [20 Dec 14 14:55]
      • Beta #973

      #83 (Poe 1.3.0.4) [18 Dec 14 15:20]
      • Beta #972.

      #82 (Poe 1.3.0.2) [16 Dec 14 15:03]
      • Beta #968 - #970.

      Beta

      #980 (1.3.0.14) [Next Version]
      • Updates for 1.3.0.14.
      • Added the setting, DisableDoNotDisturbOnBotStop.

      #979 (Poe 1.3.0.11) [05 Jan 15 15:49]
      • Summon Raging Spirits is now cast at a location of the best target rather than around the caster.
      • More example filter logic added to MyItemEvaluator.
      • The item class now correctly creates SocketableItem types from items such as rings that don't match the other primary armor types. This fixes a bug where gems in rings would not show up in the GemLeveler plugin.
      • ObjectManager.AllObjectsOverride added. This flag is false by default to keep the original behavior. When enabled, the ObjectManager will now expose all objects (with ids < 0). These objects are skill effects, projectiles, terrain doodads, and other things of that nature.
      • The CustomItemFilter plugin is now included with the bot as an example of dynamic item filters.
      • Blood Rage is now cast when in Combat Range as opposed to as soon as there's a target to kill.

      #978 (Poe 1.3.0.11) [29 Dec 14 08:36]
      • Updates for 1.3.0.11.
      • AreaStateCache.ItemLocations has had a type change of Location to ItemLocation. Code based on the previous type needs to be changed. This is so users can access cached item information along with the location. Rarity and Type has been added to start with, but more can be added as needed.
      • ExampleRoutine contains an example of filtering out Piety's portals.

      #977 (Poe 1.3.0.7) [28 Dec 14 09:13]
      • Chest.AffixStats, Chest.ExplicitAffixes, Chest.ImplicitAffixes, Chest.ImplicitStats, Chest.ExplicitStats, Chest.ImplicitProperties, Chest.ExplicitProperties, and Chest.CraftedProperties wrappers added. These do the same thing as the ones in Monster, except for chests. Before, users would have to access the information though the Components.ObjectMagicPropertiesComponent manually.
      • BasicGrindBot.TriggerOnLoot is now public, to allow users to trigger their own OnLoot events if they make their own LootItemsTask.
      • Added BasicGrindBot.TriggerOnStash for users to trigger OnStash events.
      • LoginState.Login will now return NoCredentials if the user wants to login with credentials and did not set them. Before, the bot would throw an exception since an empty string was attempted to be used to login with.
      • StashItemsCoroutine now takes a TriggerOnStashDelegate parameter to trigger when an item is about to be stashed. This is so users can be notified of stashed items for tracking purposes.
      • StashTask now takes a TriggerOnStashDelegate parameter to trigger when an item is about to be stashed. This is passed though Coroutines.StashItemsCoroutine, which is called internally.
      • LootItemsTask's triggerOnLoot delegate is now optional and defaults to null. This is to avoid breaking the API from the additions to StashTask/StashItemsCoroutine, without forcing users to implement the trigger delegates.
      • A bug where AreaStateCache spams exceptions due to multiple entries should finally be fixed. A location was being added more than once, rather than being updated if it already existed.
      • WaitForWorldPanel will now wait up to 10s by default for the WorldPanel to open as opposed to 1s.
      • TravelToGrindZoneTask will now try up to 5 times, rather than 3, to take an area transition or waypoint.
      • TravelToGrindZoneTask will now delay 3s after a failed waypoint attempt. This is to be consistent with a failed area transition attempt.

      #976 (Poe 1.3.0.7) [25 Dec 14 02:17]
      • ExampleRoutine now ignores mobs under the Divine shrine's effect. Thanks to ExVault for providing the data to fix this.
      • IdItemsUsingInventoryCoroutine now returns IdItemsCoroutineError.UnidentifiedItemsRemaining if the coroutine completes and there are still items left to be identified. Before, it would return None, signaling all items had been ided.

      #975 (Poe 1.3.0.7) [23 Dec 14 04:38]
      • Updates for 1.3.0.7.

      #974 (Poe 1.3.0.6) [22 Dec 14 05:44]
      • Updates for 1.3.0.6.

      #973 (Poe 1.3.0.5) [20 Dec 14 05:53]
      • Updates for 1.3.0.5.
      • ExampleRoutine.CombatTargetingOnWeightCalculation now adds weight to monsters that give the aura monster_aura_cannot_die.
      • The ConfigurationWindow now shows the login window 5 times before closing Exilebuddy in the event there's an error authing your key with the server. Before, it was possible for the GUI to throw an exception from trying to re-show the enter key dialog again when it was visible.
      • Updates to Exilebuddy are now checked before you are logged in to BuddyAuth. This is to help reduce the chance of Max Sessions for low session users if there was an error during the update process.
      • Exilebuddy's update logic has been updated to check the major/minor version number before updating. This is to allow us to change the major/minor version of EB and prevent the updater from updating an old bot version, which would lead to problems due to old files being in the directory that might prevent the bot from starting up correctly. Now, a message will be displayed telling the user EB is out-of-date and that they need to download a clean copy.
      • ExampleRoutine now logs why it's calling PlayerMover.MoveTowards.

      #972 (Poe 1.3.0.4) [18 Dec 14 05:50]
      • Updates for 1.3.0.4.

      #971 (Poe 1.3.0.3) [17 Dec 14 05:54]
      • LokiPoe.InGameState.ChatMessages should now really work correctly after 1.3.0 GUI changes.

      #970 (Poe 1.3.0.3) [16 Dec 14 01:24]
      • StashPanel/GuildStashPanel have updates to fix GUI changes that broke SwitchToTab.
      • LokiPoe.InGameState.ChatMessages should now work correctly after 1.3.0 GUI changes.

      #969 (Poe 1.3.0.3) [15 Dec 14 07:08]
      • Updates for 1.3.0.3

      #968 (Poe 1.3.0.2) [15 Dec 14 00:15]
      • Updates for 1.3.0.
      • ExplorationCompleteTask.TranstionToTake now attempts to return an area transition that AreaStateCache knows of, and is reachable. This fixes an issue where the bot was unable to take an area transition out of the Brutus boss room when AreaTransition was set for the exploration complete behavior.
      • NetworkObject.MinimapIcon added. This allows users to know the minimap icon type shown for an object. This is useful for being able to identify mission mobs or objectives.
      • Master experience is now exposed though Player. You can now access: CurExpVorici, CurExpTora, CurExpCatarina, CurExpZana, CurExpVagan, CurExpElreon, CurExpHaku, and CurExpLeo though any Player object (e.g., LokiPoe.Me).
      • DefaultPlayerMover.MoveTowards now does a path distance check again to try and avoid cases of the bot moving though obstacles due to the destination being closer than other points along the path around the obstacle.
      • Actor.TormentIsTouched and Actor.TormentIsPossessed added to distinguish torment buffed mobs.
      • LokiPoe.InGameState.ChatMessages is currently broken due to client changes. It will not return any messages. A fix is being looked into still.
       
      Last edited: Jan 11, 2015
    Thread Status:
    Not open for further replies.

    Share This Page