prk/issues
12
3
Fork 0
Code Issues 231 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

Keeper Fury item does not work after zoning #628

New Issue
Closed
opened 2024-02-21 05:34:00 +01:00 by TheTinkeringIdiot · 2 comments
TheTinkeringIdiot commented 2024-02-21 05:34:00 +01:00 (Migrated from github.com)
Copy Link

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

**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](https://github.com/project-rubika/issues/assets/96996793/5666fe6f-5be2-4167-8bf1-f4b36cab3f61)
RaggyLP commented 2024-02-22 19:07:04 +01:00 (Migrated from github.com)
Copy Link

Confirmed, the action is lost on zone.

image
image

Confirmed, the action is lost on zone. ![image](https://github.com/project-rubika/issues/assets/156821187/a1c271c1-e89c-4996-a2b1-2b7e915da3d8) ![image](https://github.com/project-rubika/issues/assets/156821187/9a7d1791-caab-4c1e-86de-db70ea9600f5)
RaggyLP commented 2024-02-24 01:50:23 +01:00 (Migrated from github.com)
Copy Link

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

image
image

Fury now persists across zoning. Confirmed fixed as of 00:49 UTC - 24/02/24. ![image](https://github.com/project-rubika/issues/assets/156821187/b253bf86-aee7-414d-9b98-10b1d61713da) ![image](https://github.com/project-rubika/issues/assets/156821187/828bd4ab-45a3-4d11-ac75-5cd80c114495)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area
blabot
Related to NPC dialog/conversations
area
client
This issue is (or appears to be) client-side
area
encounters
Related to scripted encounters
area
launcher
Related to the launcher
area
missions
Related to randomly generated missions
area
npc-behavior
Related to NPC/monster behaviour
area
performance
Caused by or related to server performance issues
area
portal
Related to the player portal website
area
quests
Issues relating to quests
area
rdb
Caused by RDB issues
area
teams
Issues relating to teaming with other players
area
trading
Related to trading with vendors and/or other players
priority
1
Crashes playfield/server/other players or is game-breaking in a major way
priority
2
Crashes/breaks a character, significant gameplay impact with no workaround
priority
3
Standard or significant gameplay impact with workaround
priority
4
Trivial or minor gameplay impact, with or without workaround, or visual only
shadowlands
Related only to Shadowlands content
state
cant-reproduce
Can't be recreated by another tester
state
duplicate
This issue or pull request already exists
state
fixed
Developer has rolled out changes, needs re-tested to confirm fixed
state
new
Needs to be (re-)tested to ensure the issue is reproducible
state
unrefined
Needs more detail, repro steps or to be cleaned up
state
wontfix
This will not be worked on
type
bug
An implemented feature is not working correctly
type
enhancement
Unimplemented feature, new feature / request
No Label
priority
3
type
bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: prk/issues#628
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?