Disabling auras through GUI

[krone6]

I know I could just open the profile and change how skills behave, though if I want to do that on the fly and through the GUI could I? Currently I want to throw a bunch of auras onto my character to level though I don't want him to cast it, however if I switch to someone else that does use those I'd want the auras to behave differently so he or she does use them or not vs just leveling them. And yes, I did give the forum a search for this topic and looked through support, couldn't find anything on this.

Also thanks for the stash tab update. It's made the chaos plugin so much better and I spend less time (up to 3-4 less minutes) searching tabs that won't ever see anything beyond gems or rings.

 

[pushedx]

The feature isn't implement in ExampleRoutine, but yes, it's possible. It's not something I can do anytime soon though, but I think I can add in a simple system to just blacklist skills by their current skill id to avoid the routine from using them in the aura casting logic sections.

This system is not unlike before, where the routine just listed Auras by name and you could enable/disable them. That design was too limited, and impractical now that auras can be granted from corrupted items, or if you want to use a skill and level a gem with the same name. With that old system, you'd be out of luck.

With the current setup, you'd have to manually manage and actively update the skill ids you want the CR to ignore. This is for the very reason why ExampleRoutine now uses skill slots rather than skill ids / names like previous designs have. Skill ids are based on the current slot and socket index in this game. That data is only valid when you're in game, so if you try automatically managing it, you run into problems when it's not accessible, but the gui needs the new information. If you move a skill or weapon swap, there's no way to associate the old id with the new one, because that's just how this game works.

So, you'll be able to see a list of the current skills / ids (sort of like gem leveler shows), but you'll have to manage adding and removing the ids to and from the blacklist. If you move skillgems around or weapon swap, you'll have to keep in mind you need to fix the ids, otherwise, the wrong skills will be ignored.

If you / anyone else wants to try it yourself, you're basically just looking at:
* Add a List<ushort> SkillBlacklist for blacklisted skill ids to settings.
* Code in the gui for adding/remove ids to/from the settings (sort of like GemLeveler does).
* In the aura handling logic of ExampleRoutine, which is marked by "// Handle aura logic." you basically just add in the blacklist checking before auras are used in two specific spots:
1. if (!ExampleRoutineSettings.Instance.SkillBlacklist.Contains(aura.Id) && !LokiPoe.Me.HasAura(aura.Name) && aura.CanUse(ExampleRoutineSettings.Instance.DebugAuras))
2. if (!ExampleRoutineSettings.Instance.SkillBlacklist.Contains(skill.Id) && (skill.SkillTags.Contains("aura") && !skill.SkillTags.Contains("vaal")) || IsAuraName(skill.Name))

That should be all that is needed to make the auto-aura cast logic skip skills with specific ids.

 

[darkbluefirefly]

The feature isn't implement in ExampleRoutine, but yes, it's possible. It's not something I can do anytime soon though, but I think I can add in a simple system to just blacklist skills by their current skill id to avoid the routine from using them in the aura casting logic sections.

This system is not unlike before, where the routine just listed Auras by name and you could enable/disable them. That design was too limited, and impractical now that auras can be granted from corrupted items, or if you want to use a skill and level a gem with the same name. With that old system, you'd be out of luck.

With the current setup, you'd have to manually manage and actively update the skill ids you want the CR to ignore. This is for the very reason why ExampleRoutine now uses skill slots rather than skill ids / names like previous designs have. Skill ids are based on the current slot and socket index in this game. That data is only valid when you're in game, so if you try automatically managing it, you run into problems when it's not accessible, but the gui needs the new information. If you move a skill or weapon swap, there's no way to associate the old id with the new one, because that's just how this game works.

So, you'll be able to see a list of the current skills / ids (sort of like gem leveler shows), but you'll have to manage adding and removing the ids to and from the blacklist. If you move skillgems around or weapon swap, you'll have to keep in mind you need to fix the ids, otherwise, the wrong skills will be ignored.

If you / anyone else wants to try it yourself, you're basically just looking at:
* Add a List<ushort> SkillBlacklist for blacklisted skill ids to settings.
* Code in the gui for adding/remove ids to/from the settings (sort of like GemLeveler does).
* In the aura handling logic of ExampleRoutine, which is marked by "// Handle aura logic." you basically just add in the blacklist checking before auras are used in two specific spots:
1. if (!ExampleRoutineSettings.Instance.SkillBlacklist.Contains(aura.Id) && !LokiPoe.Me.HasAura(aura.Name) && aura.CanUse(ExampleRoutineSettings.Instance.DebugAuras))
2. if (!ExampleRoutineSettings.Instance.SkillBlacklist.Contains(skill.Id) && (skill.SkillTags.Contains("aura") && !skill.SkillTags.Contains("vaal")) || IsAuraName(skill.Name))

That should be all that is needed to make the auto-aura cast logic skip skills with specific ids.

Hey all,
I'm attempting this already as I think it's a good idea to have this.
What I did is I have 2 listboxes, one with the auras you want, and one black at startup.
Double click( having issues with this, might move over to baml-codebehind) and it moves selected item back and forth.
In the code where it does check for auras, only add those that are on the to use list and ignore the other ones.
But I think blacklisting might work better, we'll see. I first have to get double clicking on the selected item to work, it seems my event handlers aren't working at all on xaml based setups.