Community
Hub
Mark all as read Notifications (0)
View all notifications
My account
Not a member yet?
Register now and join our community!

Wrong unlock requirements of Ancient Relic items on PC

Warhammer 40K Bug Report
By Distemper 15.10.2022
Marcopolocs replied 28.10.2022
8

Hi there !

Recently many players found they get ancient relics with unreasonable unlock requirements  such as "execute 100000 enemies".

Please look into this and fix, thanks !

This post was edited 16.10.2022 by Distemper
Store Page
Share
previous post back to community page next post
8 comments
Newest Oldest Best
Save This Order
Set this current order state as My default.
Wrong unlock requirements of Ancient Relic items on PC
Your Thoughts? Please login to place your opinion. Not a member yet? Register here and now!
16.10.2022
Update: uploaded pic of one such item (see above). This is weird.
16.10.2022
Some players describe this issue as :"Items were normal when they dropped in mission, but the unlock requirements changed after returning to bridge."
16.10.2022
+1
Distemper
I agree.  I had a rifle drop that I loved that I have to execute 100,000 enemies to use.  I'm level 59.  By the time I finish executing all those enemies, I'll have outlevelled that rifle and be level 100.
17.10.2022
DofaDofa

https://imgur.com/meEtJIT  This is a picture of my wrongful requirements.

This comment was edited 17.10.2022 by DofaDofa
17.10.2022
DofaDofa

Normally such requirements would be 50 or 100 executions, if I remember correctly.


Actually , the time would be enough to make several, if not dozens of characters to reach lv100 LOL



This comment was edited 17.10.2022 by Distemper
17.10.2022
+2
Added the screenshot to our to-do bug list. Thanks @DISTEMPER‍ !


There is another bugged unlock req which is about using Booster Inoculator component waaaay too many times. That got forwarded too.

20.10.2022
Marcopolocs

Did you get my screenshot too?  I didn't know how to upload it so I attached it to the message as a link.

This comment was edited 20.10.2022 by DofaDofa
28.10.2022
DofaDofa
The issue should be fixed. There was a backend problem and the whole requirement system screwed up. We handled the problem last week it's just that I was out of action and could not inform you.