- The new map tab is unsupported and there are no plans to support that tab moving forward due to the complexity of the underlying inventory system used for it.
- A simple Abyss plugin has been added.
- Item.IsShaperItem added for the cosmic background items.
- Item.IsElderItem added for the tentacle background items.
- InstanceInfo.ElderInfluencedAreas added.
- InstanceInfo.ShaperInfluencedAreas added.
- The quest to move the fuel carts in "The Beacon" is now much more combat intensive. Changes have been made to prevent the routine from locking up on infinite monsters, but if your character does not have good defenses or enough aoe DPS, chances are it'll get stuck or die a lot now. Please monitor this quest manually to be sure your bots can get through it.
- OldRoutine updates:
- Changes have been made to work around the quest changes of the fuel cart quest in "The Beacon" area.
- Orb of Storms is now cast on a fixed interval.
- StashTabInfo updates:
- InventoryId will return 0 for the new unsupported map tabs. Check against IsPremiumMap to avoid possible logic issues if you're using this member.
- DisplayIndex is now an ushort.
- Added LinkedParentId which is related to the new changes for map tabs.
- InventoryTabPermissions enum added.
- InventoryTabType enum added to handle the different types of tabs (normal, currency, etc...).
- InventoryTabFlags enum added to handle the new tab flags.
- InventoryTabMapSeries enum added for the 4 map series types listed on the tab.
- MemberFlags now returns a type of 'InventoryTabPermissions' rather than an 'int'.
- OfficerFlags now returns a type of 'InventoryTabPermissions' rather than an 'int'.
- MapSeries added (InventoryTabMapSeries enum).
- IsPremiumMap added.
- IsPremiumSpecial now checks IsPremiumMap.
- TabType added to expose the new tab types. This is what the 'Is' properties check against.
- TabFlags added to expose the new tab flags. This is what the 'Is_Flagged' properties check against.
- To avoid confusion due to internal tab data changes, and the dual meaning of 'premium':
- IsPremium now refers to the Premium standard stash tab (the standard size with color header). Before, it would refer to any non-standard stash tab. This is for consistency with the other Is properties, such as IsPremiumQuad or IsPremiumEssence.
- IsPremiumFlagged has been added to refer to any non-standard stash tab that has the premium flag on it. All non-standard tabs are premium flagged currently.
- For consistency: IsPublic -> IsPublicFlagged, IsRemoveOnly -> IsRemoveOnlyFlagged, IsHidden -> IsHiddenFlagged to help avoid confusion with the premium wording.
- TransitionTypes.Labyrinth added for Labyrinth area transitions (type 5) as they otherwise would show up as 'Unknown'.
- InventoryControl.HasRewardTabOverride added to distinguish the new RewardUi controls.
- RewardUi changes
- InventoryControl removed as there is no longer one inventory control for the reward UI.
- InventoryControls added, which is a list of InventoryControlWrappers that represent all the quest rewards.
- Use the 'CustomTabItem' property to get the item with these InventoryControlWrappers as you would with any other special tab. The id-less variants of the API have to be used for these controls as with the other special tabs.
- SocketColor.Abyss added.
- Socket matching logic updated to properly match Abyss and White sockets.
- LinkedSocketColors, SocketedSkillGemsByLinks, and SocketedGems are now properly logged in Item.Dump.
- To avoid breaking changes, various places where the "Skill Gem" text is used will be kept as-is rather than rename to account for the fact Abyss Jewels can now be equipped.
- InventoryControlWrapper.EquipSkillGem updated to handle Abyss Jewels.
- MapComponent.MapSeries added and is exposed through Item.MapSeries.
- StashUi.MapTab placeholder added, but there's no API support for that tab.
- Updates for 3.1.0.5
- Updates for 3.1.0.4
- Updates for 3.1.0.3
- Updates for 3.1.0.2
- Updates for 3.1.0.1
There were a lot of client changes in this expansion, so we expect people to find random little things that are broken with the API. We'll test as much as possible to address the obvious stuff, but it's not possible to comprehensively test everything, so as usual we warn users to make sure they remember to monitor their bots to watch out for things that break.