Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keeper Fury item does not work after zoning #628

Closed
TheTinkeringIdiot opened this issue Feb 21, 2024 · 2 comments
Closed

Keeper Fury item does not work after zoning #628

TheTinkeringIdiot opened this issue Feb 21, 2024 · 2 comments
Labels
bug Something isn't working priority-3

Comments

@TheTinkeringIdiot
Copy link
Collaborator

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:

  1. Be Keeper (Clan or Omni)
  2. Run Fury
  3. Zone
  4. Attempt to use action "Righteous Fury" (Clan) or "Unhallowed Fury" (Omni)
  5. It doesn't work

Expected behavior
The Fury item should continue to work after zoning.

Screenshots
image

@TheTinkeringIdiot TheTinkeringIdiot added bug Something isn't working needs-verification This is a new issue or affects a recently changed system and requires a tester to confirm the issue labels Feb 21, 2024
@RaggyLP
Copy link
Collaborator

RaggyLP commented Feb 22, 2024

Confirmed, the action is lost on zone.

image
image

@RaggyLP RaggyLP added priority-2 priority-3 and removed needs-verification This is a new issue or affects a recently changed system and requires a tester to confirm the issue priority-2 labels Feb 22, 2024
@RaggyLP
Copy link
Collaborator

RaggyLP commented Feb 24, 2024

Fury now persists across zoning. Confirmed fixed as of 00:49 UTC - 24/02/24.

image
image

@RaggyLP RaggyLP closed this as completed Feb 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority-3
Projects
None yet
Development

No branches or pull requests

2 participants