A simple addon to estimate success chances for Covenant missions based on combined unit strength of ally & enemy teams.
Disclaimer: The logic used to gauge the success chances is unproven.
It deliberately doesn't attempt to factor in friendly/enemy unit abilities and is intended more as a rough guideline to warn you when you likely have no chance of success with your current units for a given mission.
Languages supported:
- English
- Chinese (Simplified) - Azpilicuet@CN主宰之剑
- Chinese (Traditional) - BNS (三皈依 - 暗影之月)@miliui, arranged by Azpilicuet@CN主宰之剑
- French - JEUD
- German - Aurantea@SteamwheedleCartelEU
- Italian - zemaree@github
- Korean - killberos
- Portuguese (Brazil) - Mufasto
- Russian - Hubbotu
- Spanish - Araxieel
- Spanish (Latin American) - bakadeshisho
This addon is OK but fairs on the safe side. As a result it will often tell you missions are impossible when they are winnable.
On the other hand CovenantMissionHelper is a MUST HAVE and VERY accurate. It can even swap the positioning of the NPCs you choose for the mission to minimize HP losses. I just completed a test to see how good it was at extreme cases: MIssion>"Defiled But Protected", I used all 50+ combatants and it told me all would die but one and that it would have 75 HP left... so I went for it. The result? We won by 75 HP as predicted!! By comparison "Covenant Mission Success Estimates" told me that the mission was impossible.
I think this addon needs update to 9.0.5 as missions became easier due to this patch. I use this in combination with Venture plan addon and this addon says I will fail when venture says success and Venture currently is correct and not covenant. Thanks for the addon though look forward to update.
In reply to spotts:
This addon's estimates come from the Health/Damage values given by the existing in-game mission UI. If Blizzard has updated those numbers to reflect balance changes in the missions, then this addon's estimates will adjust accordingly.
The estimates given are conservative and based on very simple logic by design, intended more to save people from wasting time/resources on missions they'll definitely fail, rather than to give detailed advice about the mission chances.
Found my answer.
Thank you for the update. Not an issue it seems since Table worked perfect after update but BugSack is getting the following error.
2x CovenantMissionHelper\Board.lua:331: attempt to index field '?' (a nil value)
[string "@CovenantMissionHelper\Board.lua"]:331: in function `onUnitTakeDamage'
[string "@CovenantMissionHelper\Board.lua"]:296: in function `makeUnitAction'
[string "@CovenantMissionHelper\Board.lua"]:161: in function `fight'
[string "@CovenantMissionHelper\Board.lua"]:142: in function `simulate'
[string "@CovenantMissionHelper\CovenantMissionHelper-0.1.lua"]:38: in function `simulateFight'
[string "@CovenantMissionHelper\CovenantMissionHelper-0.1.lua"]:20: in function <...dOns\CovenantMissionHelper\CovenantMissionHelper.lua:15>
[string "=[C]"]: ?
[string "=[C]"]: in function `UpdateAllyPower'
[string "@Blizzard_GarrisonUI\Blizzard_CovenantMissionUI.lua"]:647: in function <...s\Blizzard_GarrisonUI\Blizzard_CovenantMissionUI.lua:608>
[string "=[C]"]: in function `AssignFollowerToMission'
[string "@Blizzard_GarrisonUI\Blizzard_CovenantMissionUI.lua"]:957: in function `AddFollower'
[string "@Blizzard_GarrisonTemplates\Blizzard_GarrisonSharedTemplates.lua"]:1024: in function `GarrisonFollowerListButton_OnClick'
[string "*:OnClick"]:1: in function <[string "*:OnClick"]:1>
Locals:
self = <table> {
hasRandomSpells = false
initialEnemiesHP = 8360
isEmpty = false
units = <table> {
}
initialAlliesHP = 1225
max_rounds = 100
missionID = 2205
baseXP = 400
isCalcRandom = false
winXP = 400
isMissionOver = false
probability = 100
}
spellID = 11
casterBoardIndex = <table> {
spells = <table> {
}
reflect = 124
untargetable = false
currentHealth = 1764
role = 1
name = "Tempted Scholar"
boardIndex = 5
ID = 3852907
buffs = <table> {
}
maxHealth = 2240
attack = 124
}
eventTargetInfo = <table> {
oldHealth = 97
boardIndex = 2
points = 124
maxHealth = 1225
newHealth = 0
}
(*temporary) = <function> defined @CovenantMissionHelper\CovenantMissionHelper.lua:154
(*temporary) = <table> {
Spell = <table> {
}
Buff = <table> {
}
Unit = <table> {
}
log = <function> defined @CovenantMissionHelper\CovenantMissionHelper.lua:154
debug_log = <function> defined @CovenantMissionHelper\CovenantMissionHelper.lua:159
MetaBoard = <table> {
}
TargetManager = <table> {
}
DataTables = <table> {
}
Board = <table> {
}
}
(*temporary) = <function> defined =[C]:-1
(*temporary) = "|cFFFF7700 %s kill %s |r"
(*temporary) = nil
(*temporary) = <table> {
1 = <table> {
}
}
(*temporary) = <function> defined =[C]:-1
(*temporary) = "attempt to index field '?' (a nil value)"
In reply to Galthariel:
That's an error in the CovenantMissionHelper addon, not this one - Looks like a bug. It doesn't have anything to do with this addon, and I'm 99% sure it isn't caused by this one either since there's nothing in the stack trace you posted that references this addon.
In reply to Kvalyr:
You're right. Thank you and I'm sorry for posting it here.
Addon is working perfect and flawlessly so this is a feature request only in case isn't too much trouble to implement. I would like to mouse over the current mission to see what companion or companions are doing that particular mission and/or over the companion to see what mission he is doing. Thanks in advance :-)
This is pretty cool but like the author says it's a rough estimate, very rough even. You have to take into consideration *what* your troops are doing and the enemy. For example if you're night fae that flips over the table completely and if you're kyrion you're going to struggle hard. As time goes on I hope these addons become a lot better at doing the math because the mission tables this time around are pretty cool. BfA was a huge flop.
Would it be possible to get this to work alongside Garrison Mission Manager?
Hello, I have this add-on installed for a while now but I Don't see how I am supposed to use it. is there a command I can use to get to some addon settings?
In reply to SpikeAndEd:
Please see the screenshots. It adds a panel to the Covenant Mission window. There are no settings to change.
In reply to Kvalyr:
Hey Kvalyr, Thank you so much for a quick reply. I Tried many things to get this add-on to work but noticed that it wasn't just this add-on that wasn't working. I had to switch my add-on manager and Its working perfectly fine now. Thanks for a swift reply and an amazing add-on to make things much easier. Have a great day.
aren't these called adventures instead of missions? i mean everyone call them missions but they are named adiffrent. i was browsing for keyword adventure adventures for days now.
In reply to Morwo01:
You could also search for 'Covenant' :)
They've been called Missions in previous iterations of the Mission Table in WoD, Legion, BfA, etc. and the Blizzard UI code calls them missions too. I can only put so many words in the title of the addon for searchability before it gets silly.
Hello.
Would you change word order in Korean localization?
[For example]
It would take [x] round(s) for [y] team to beat [z] team.
-->
[x] round(s) for [y] team to beat [z] team it would take.
This word order is correct in our country. :)
In reply to killberos:
Thanks! I'll make that change soon.
In reply to Kvalyr:
[+Addition]
It would take [x] round(s) for [y] team to beat [z] team
--->
for [y] team to beat [z] team [x] round(s) It would take.
Sry.
My bad. :(
It's final word order.
In reply to killberos:
Thanks! I've tried to implement these changes in 0.3.4, please let me know if it looks right in-game!
Hello, is there a chance to make it compatible with Master Plan?
I'm still using it a lot, but with your covenant addon, Master Plan does not work. No lua errors are shown.
And I noticed that your addon has three names, depending on where you look (here, addon folder, ingame addon list). A consistent name would be nice :).
In reply to Selthi:
0.3.0 (available when CurseForge approves the file) contains a compatibility fix for Master Plan that should resolve the issue. I've removed "Simple" from the addon name in the addon list - that's a good callout, as I renamed it on here a while back, but I won't be renaming the addon folder.