Swapping items with the same stat modifiers exponentially increases the stat until zone. (Stacking) #472
Labels
No labels
area
blabot
area
client
area
encounters
area
launcher
area
missions
area
npc-behavior
area
performance
area
portal
area
quests
area
rdb
area
teams
area
trading
area
zone
priority
1
priority
2
priority
3
priority
4
shadowlands
state
cant-reproduce
state
duplicate
state
fixed
state
new
state
unrefined
state
verified
state
wontfix
type
bug
type
enhancement
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: prk/issues#472
Loading…
Add table
Add a link
Reference in a new issue
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?
Describe the bug
Swapping an item with the same modifiers on it will increase the stat by the same amount infinitely, until the player zones.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
An items previous stat increase/modifier should be cleared when a new item is placed in that slot.
Screenshots

Character info:
Playfield info:
@RaggyLP - please test when you can (when servers back online)
Confirmed fixed on Weapons. swapping the same gun doesn't generate a stacking stat, however, tested using Trader Star swapping on Util 1 and it still generated a stacking effect on the client for that slot. This however, wasn't accepted by the server:
Your Shotgun is required to be at least 2250! You're unable to wear this item..
f519c436
-82e1-4253-ba96-5f48e91a4818Confirmed. Did not replicate for me using the Clan token board, but using the Beast Star did indeed stack using the described method.
Priority lowered to 2 - issue is only shown client-side and offers no significant gameplay advantage that I know of
Should be resolved. Please confirm.
Confirmed fixed for me. Will hold closing to give Raggy a chance to test.
Confirmed fixed as of 22:14 UTC - 17/02/24. Nicely done guys (: