You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make sure the bug also happen when Details! is the only addon enabled.
Game and Details! version
Use /details to grab these two.
Describe the bug
Steps to Reproduce (what did you do to make the bug happen):
i just log into the game and error happens.
Result (what happens when you follow the steps above):
same thing
Expected (what you think the expected behavior would be when following the steps):
to work
When the bug started (a date, wow path release, details update, etc)?
10/1/2024, 11.0.2.56819, details-details.13090.161.zip
Additional information:
Lua Error
Post here lua errors, if you aren't getting any, use /console scriptErrors 1
2x Details/functions/ej_cache.lua:118: attempt to index field 'CurrentContent' (a nil value)
[string "@Details/functions/ej_cache.lua"]:118: in function IsCurrentContent' [string "@Details/functions/storage.lua"]:466: in function IsZoneIdFromCurrentExpansion'
[string "@Details/core/parser.lua"]:5465: in function <Details/core/parser.lua:5349>
Locals:
id = 2657
(*temporary) = nil
(*temporary) = "attempt to index field 'CurrentContent' (a nil value)"
Details222 =
Combat Log
Include a link to a combatlog file if the error is about not detecting a skill, usable item or item proc.
The log can be as simple as hitting a mob with white damage and using the item/skill.
Other Information
If necessary, add more info here.
The text was updated successfully, but these errors were encountered:
Before Start!
Make sure the bug also happen when Details! is the only addon enabled.
Game and Details! version
Use /details to grab these two.
Describe the bug
Steps to Reproduce (what did you do to make the bug happen):
i just log into the game and error happens.
Result (what happens when you follow the steps above):
same thing
Expected (what you think the expected behavior would be when following the steps):
to work
When the bug started (a date, wow path release, details update, etc)?
10/1/2024, 11.0.2.56819, details-details.13090.161.zip
Additional information:
Lua Error
Post here lua errors, if you aren't getting any, use /console scriptErrors 1
2x Details/functions/ej_cache.lua:118: attempt to index field 'CurrentContent' (a nil value)
[string "@Details/functions/ej_cache.lua"]:118: in function
IsCurrentContent' [string "@Details/functions/storage.lua"]:466: in function
IsZoneIdFromCurrentExpansion'[string "@Details/core/parser.lua"]:5465: in function <Details/core/parser.lua:5349>
Locals:
{id = 2657
(*temporary) = nil
(*temporary) = "attempt to index field 'CurrentContent' (a nil value)"
Details222 =
PlayerStats =
}
Cache =
}
ClassCache =
}
UnitIdCache =
}
CustomItemList =
}
PetContainer =
}
SpecHelpers =
}
Notes =
}
PFrame = Frame {
}
InstanceDifficulty =
}
TimeMachine =
}
Roskash =
}
ColorScheme =
}
Unknown = "Unknown"
EncounterJournalDump =
}
BarIconSetList =
}
OneHourAuras =
}
CurrentDPS =
}
Mixins =
}
Parser =
}
EJCache =
}
AutoRunCode =
}
MythicPlusBreakdown =
}
Actors =
}
Combat =
}
SaveVariables =
}
Tvs = 110002
Scheduler =
}
LoadSavedVariables =
}
GarbageCollector =
}
OptionsPanel =
}
WarcraftLogs =
}
IgnoredWorldAuras =
}
DamageSpells =
}
OnUseItem =
}
ProfilingCache =
}
Cooldowns =
}
TrainingDummiesNpcId =
}
StartUp =
}
Date =
}
ContextManager =
}
Instances =
}
Pets =
}
Segments =
}
AuraScan =
}
PrivateInstanceText = FontString {
}
Textures =
}
Profiling =
}
Debug =
}
Tables =
}
Perf =
}
CooldownTracking =
}
ParsePercent =
}
TimeCapture =
}
GuessSpecSchedules =
}
MythicPlus =
}
parser_frame = Frame {
}
PlayerBreakdown =
}
BreakdownWindow =
}
storage =
}
RegisteredFramesToColor =
}
}
Screenshots
Post images of the bug if necessary.
Combat Log
Include a link to a combatlog file if the error is about not detecting a skill, usable item or item proc.
The log can be as simple as hitting a mob with white damage and using the item/skill.
Other Information
If necessary, add more info here.
The text was updated successfully, but these errors were encountered: