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
Describe the bug
When running the Fury nano, Keepers (Clan or Omni, not neutral) get a special attack item that can be used on a fighting target. The item does indeed become available while the nano is running, but it cannot be used in combat, giving the "Action is not available" error when attempted. This problem occurs after zoning with the Fury nano running.
The special attack item remains in the Shift-2 actions menu after zoning, but cannot be used again until the Fury nano is recast. It is as if the Fury item becomes invalid upon zoning.
This may possibly be related to #608, which describes another temporary item that malfunctions after zoning.
To Reproduce
Steps to reproduce the behavior:
Be Keeper (Clan or Omni)
Run Fury
Zone
Attempt to use action "Righteous Fury" (Clan) or "Unhallowed Fury" (Omni)
It doesn't work
Expected behavior
The Fury item should continue to work after zoning.
Screenshots
The text was updated successfully, but these errors were encountered:
Describe the bug
When running the Fury nano, Keepers (Clan or Omni, not neutral) get a special attack item that can be used on a fighting target. The item does indeed become available while the nano is running, but it cannot be used in combat, giving the "Action is not available" error when attempted. This problem occurs after zoning with the Fury nano running.
The special attack item remains in the Shift-2 actions menu after zoning, but cannot be used again until the Fury nano is recast. It is as if the Fury item becomes invalid upon zoning.
This may possibly be related to #608, which describes another temporary item that malfunctions after zoning.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The Fury item should continue to work after zoning.
Screenshots
The text was updated successfully, but these errors were encountered: