Skip to content

data: Fix signet of spite alternative power interaction... maybe?#993

Draft
marcustyphoon wants to merge 2 commits intomainfrom
signet-of-spite-alternative-power
Draft

data: Fix signet of spite alternative power interaction... maybe?#993
marcustyphoon wants to merge 2 commits intomainfrom
signet-of-spite-alternative-power

Conversation

@marcustyphoon
Copy link
Collaborator

This is kind of a mess; I have to think about this. This would make "soul shards/nightmare weapon/painful bond in shroud" wrong, for one.

Naively adopting the current scenarios system for shroud instead of doing this probably doesn't fix this either. Making signet of spite have advancedUptimeSimulation: { correlation: { category: shroud, group: false } } } is great because it would apply the signet power to only some of the soul shards, but bad because it would force signet of spite uptime to be entered as 100 - shroud uptime, i.e. it wouldn't let you simulate casting the signet. Condi harbinger does.

Truthfully, it's probably easiest to ignore the small amount of time the signet is uncast in that case (if a condi build took it, they probably cast it close to off cooldown; if a power build took it, they probably don't cast it) and just implement "signet of spite is always applied out of shroud and never applied in shroud." This would still make "soul shards/nightmare weapon/painful bond in shroud" wrong. Eugh.

@marcustyphoon marcustyphoon force-pushed the signet-of-spite-alternative-power branch from 70d797a to 60d3d37 Compare January 3, 2026 08:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant