- Home
- Games
- Company
- Community
- Roadmap
- Media
- Store
- Store Support
- Feedback
- Contact Us
- Warhammer 40K
- Home
- Community
- Hub
- BUG: Assassins cannot generate adrenaline?
BUG: Assassins cannot generate adrenaline?
Warhammer 40K Bug ReportHi guys, aren't assassins supposed to generate adrenaline by killing/hurting enemies?
Why am I not seeing this?
Your Thoughts? Please login to place your opinion. Not a member yet? Register here and now!
That would be strange if your class resource would not go up as this works perfectly fine in the game. By hitting and killing enemies, the adrenaline properly increases.
Marco, do sins generate adrenaline only when they kill? I just tested now, and it's stange that at times, I didn't notice it going up. It clearly increases...
+1 per regular group
+10 for champs
Maybe the +1 per trash mob is what led me to believe that it's not increasing.
Anyway, I will do some more testing, cause now I'm curious to see how much each enemy type gives.
I just tried now, and it wasn't giving me double adrenaline in surprise state (eg, Chaos marine gave me +10 instead of +20).
I just tried now, and it wasn't giving me double adrenaline in surprise state (eg, Chaos marine gave me +10 instead of +20).
It will take time until I can confirm or deny whether its a bug.
On the other hand you can also notice that even if you hit an enemy your Adrenaline increases slightly.
It will take time until I can confirm or deny whether its a bug.
On the other hand you can also notice that even if you hit an enemy your Adrenaline increases slightly.
Because for regular mobs, I literally wouldn't be able to see any increase, seeing as how KILLING them all gives me +1.
Since champs give +10 on kill, maybe shooting them a bit will give me a couple of points.
I will check today after work.
I can confirm now, the Bodysurge does not work with Fabricatus Distortion Armour. This indeed is a bug, nice catch, we will fix it ASAP!
I can confirm now, the Bodysurge does not work with Fabricatus Distortion Armour. This indeed is a bug, nice catch, we will fix it ASAP!
Set this current order state as My default.