PR - /MaxAggro for nukes & a bit of cleanup of ini files. #11
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Replaced Loot Settings.ini with a clean one. Changed default lootlink to say instead of gu. Cleaned unused sections from e3 Data.ini (Such as the individual bots used by Creamo, their bot version etc.). Replaced Saved Groups.ini with a clean one.
for nukes only. Made a couple formatting changes to lessen the eyestrain.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Support for /MaxAggro on nukes in the bot inis.
[Nukes]Main=Smite/Gem|1/MinMana|90/MaxAggro|60will only cast the spell Smite, if you have less than 60% Aggro with the target.
It increases control of aggro generation and helps lessening the chance that the wizard will be tanking.