Halloween survivor items under “Ascended” rarity
SUMMARY OF THE ISSUE: The “All Hallows-eve lunchbox” and “Will O’ Wisp” flashlight survivor items are marked under the “ascended” rarity when they should be common rarity.
PLATFORM: Xbox Series X
STEP BY STEP INSTRUCTIONS ON HOW THE ISSUE OCCURED: I noticed the halloween survivor items had a different rarity than the other usual event items.
VIDEO: here’s the screenshot of these items being marked as “ascended”
PLAYER LOGS:
- Player logs are required from PC players only.
Tagged:
Under Review
Comments
I am still confused as to why Event Rarity got removed.
If it wasn't removed, none of these bugs would remain.
Chiming in
This is only the case for these specific items. Obviously, this has to be changed asap because Ascended items will be 5k BP instead of their Common price, and equally rare in the Bloodweb.
Every 'Haunted by Daylight'-related add-on or offering is (fortunately) still the correct rarity:
As is every other event item. Some examples:
Coming back to this thread to update that the 9.2.1 patch today actually made this bug worse. Now the All Hallows-Eve lunchbox and Will O’ Wisp survivor items are under the “Rare” rarity instead of Common and the Arcane Dowsing Rod offering is now a “Very Rare” rarity instead of common.
Chiming in again to update that as of today’s hotfix update (9.2.2) the All Hallows’ Eve Lunchbox, Will O’ Wisp and Arcane Dowsing Rod are still the incorrect rarity. Could a dev/community manager please acknowledge that this is an important issue? The Haunted by Daylight event is back next week and im sure the community will not be pleased spending 4k blood points on an event offering or 3,250 blood points on an event item.
Throwing in even more screenshots to illustrate the problem.
This really needs to be fixed before the start of the event!
well it looks like they’ll have to learn the hard way and let the community riot tomorrow when the event starts. They got 3 weeks of notice ahead of the event to get this bug fixed and didn’t even give acknowledgment to the issue. Truly a shame to see. This could’ve been so easily prevented lol
@ThatRyanB could we please have someone look into this? Or a confirmation that this is going to be fixed before the event starts tomorrow?