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
A sequence with Default = 2 and Delves/Scenarios = 2 ran version 1 in a
delve. Two faults combine.
The editor stored a pick equal to the Default as nil, on the assumption
that an absent key resolves to the Default anyway. It does not: in
GetActiveSequenceVersion an absent key means "this rule does not match",
so the loop continues and a LOWER-priority rule claims the content.
Store what the author picked. Editor_Tree re-applied the same rule after
a version reorder, so it did that too.
The rule that then caught everything was Party. GSE.inParty is
IsInGroup(), true inside every delve, dungeon, raid and arena, and Party
is the last entry in the priority list -- so it picked up any instance
whose own rule stored no version. Party means in a party in the WORLD:
skip it when any instance context is active. It still applies grouped in
the world.
The same loop also let junk values win, since 9a17df9 replaced
`not GSE.isEmpty(meta[ctx.metaKey])` with bare truthiness and both "" and
0 are truthy in Lua: 0 resolved to version 1 via the trailing zero check,
"" resolved to "", and the PVP row (which tests PVP but reads Arena)
resolved to nil for PVP set in an arena with no Arena version. A context
now claims the sequence only when its key AND the value it actually reads
name a real version.
Lastly, inParty was only refreshed on a zone change, so joining or
leaving a group left the sequence on the version for the group state it
no longer had.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
0 commit comments