Getting this error which I guess is breaking count:

47x WarpDeplete/Events.lua:197: attempt to index local 'CriteriaInfo' (a nil value)
[string "@WarpDeplete/Events.lua"]:197: in function GetEnemyForcesCount' [string "@WarpDeplete/Events.lua"]:210: in function UpdateForces'
[string "@WarpDeplete/Events.lua"]:513: in function ?' [string "@!KalielsTracker/Libs/CallbackHandler-1.0-8/CallbackHandler-1.0.lua"]:109: in function <...ker/Libs/CallbackHandler-1.0/CallbackHandler-1.0.lua:109> [string "=[C]"]: ? [string "@!KalielsTracker/Libs/CallbackHandler-1.0-8/CallbackHandler-1.0.lua"]:19: in function <...ker/Libs/CallbackHandler-1.0/CallbackHandler-1.0.lua:15> [string "@!KalielsTracker/Libs/CallbackHandler-1.0-8/CallbackHandler-1.0.lua"]:54: in function Fire'
[string "@Betails/Libs/AceEvent-3.0-4/AceEvent-3.0.lua"]:120: in function <...ceBetails/Libs/AceEvent-3.0/AceEvent-3.0.lua:119>

Locals:
self =

{
modules = {
}
Glow = {
}
db = {
}
defaultObjectivesState = {
}
bar1 = {
}
name = "WarpDeplete"
LSM = {
}
L = {
}
bar2 = {
}
defaultForcesState = {
}
bars = {
}
bar3 = {
}
baseName = "WarpDeplete"
defaultModuleState = true
forcesState = {
}
Util = {
}
frames = {
}
enabledState = true
forces = {
}
configDialog = {
}
optionsGeneralFrame = Frame {
}
isUnlocked = false
keyDetailsState = {
}
objectivesState = {
}
challengeState = {
}
defaultModuleLibraries = {
}
defaultKeyDetailsState = {
}
timerState = {
}
orderedModules = {
}
isShown = true
defaultChallengeState = {
}
defaultTimerState = {
}
}
stepCount = 0
CriteriaInfo = nil
(*temporary) = 0
(*temporary) = false
(*temporary) = false
(*temporary) = false
(*temporary) = "attempt to index local 'CriteriaInfo' (a nil value)"

"There is currently nothing in the wow api that returns current mob-count. This has already been reported and is up to Blizzard to add back into the game. I have changed the aura to only use percentage for now as that is the only way of doing it at the moment. (they only provide rounded percentage with 0 decimals). This also means that the "current pull" display can only be an estimation as I have no way of knowing the decimal numbers."

Apparently this is a thing, could be why?

Yeah, that's definitely the issue. Most of the other bugs were fixed already, but this requires some more work, so we opted to already put out a usable version while this issue is still present. It is being worked on.

Fixed in #76