Search results

Moved to Support. Please attach a full log. It's indeed possible something got out of sync on your client, but the quest should be working fine for 3.3.

Beta #1748 has just been deployed. A new release will be built soon as well.

Exilebuddy is undergoing expected maintenance for the 3.3.0c update. If there are any foreseen delays in pushing an update tonight, we'll let users know. Until then the update is expected to take several hours at minimal.

Please rename the folder as well as the exe so it does not have Exilebuddy in it!

It's in the next Beta/Release, which would have been earlier this week, but GGG's pre-announced big patch for earlier this week never came, so we're just waiting to push the changes along with that to avoid confusion and issues between it being an optional update without a game patch, but still...

You'll have to get Support from the author of the EquipPlugin on this issue, but this forum is 'ok' to use for that if you want to link them your thread.

That is not a feature ItemFilterEditor supports out of the box. However, we'll include new logic to limit picking up Wisdom/Portals based on an inventory limit count to help avoid that issue, as it's been requested for a while now and been put off since we wanted to update the entire filter, but...

Since you've confirmed the game creates separate instances for each charge, rather than having 1 instance where it increases the charge (welcome to the inconsistencies of PoE), all you have to do get your total charge count is: var chargedDashCount = LokiPoe.Me.Auras.Count(a =>...

Hopefully this league, but depends on the upcoming game changes as well. New party system will affect EB and cause dev time to be spent on that soon and another decent sized patch is scheduled for tonight or tomorrow. Making a generic routine that can do everything possible in this game is...

Not without a routine rewrite, or you editing the code to add in the logic to only use that skill on uniques. So it's doable, but not a feature OR supports and won't support since it's an old routine that will be replaced in the near future.

It's possible a casting mechanic changed with EC or something with charges, we'll check it out soon with OldRoutine to be sure.

Our way of thinking is just fine. Users who know what they are doing and are willing to accept the results can execute the code I mentioned above to do what they want.

See my reply here to get a starting idea of what you can look for: https://www.thebuddyforum.com/threads/bot-always-moves-to-melee-range.419493/#post-2554384

No setting for logging because then when things do go wrong, we'd have no way of being able to fix the issue or help them understand the problem!

If someone still wanted to use dnd they could, but from a general perspective, I just just don't think it's a good idea. You'd now have a more bot-like /dnd use activity associated with the account, as it turns dnd on and off until it's the state it wants, and I'm not comfortable with that...

Not recommended, but if you really want to, call this code someone in a plugin or routine: Loki.Common.Logger.ChangeLogFilterLevel(log4net.Core.Level.Off, log4net.Core.Level.Off);

Just as a heads up, another big patch is expected within the next few days as pre-announced by GGG. In the next Beta/Release build, there will be a breaking change to OldRoutine's skill blacklist. Please read this thread ahead of time...

You have an exception from a community plugin that is not supported by us or the author anymore: There's nothing we can do to help you, as you'll need to get community help from wherever you got that code from.

Always attack in place will fix issues with skill that move the player when namelocking isn't used. OR does not cast using namelocking but rather casting at a location that ends up getting mapped near a mob's feet due to highlighting issues in this game. Max Melee Range will affect this, but...

You should be able to find everything you need here: https://www.thebuddyforum.com/threads/autoflask-settings-description.408148/