Why hasn't penetration of the soul been fixed yet?

Warhammer 40,000: Darktide Bugs
1

Issue Type (Required):

Talents

Issue Description (Required):

As of writing this it has been nearly 6 months since penetration of the soul was added to psyker’s skill tree, and it has been functional for none of that.

What I don’t understand is how it’s been this long without fatshark fixing it, when the fix would literally only take 5 seconds.

defallt here identified the cause of the bug, pretty amateurish imo but I’m not a programmer Penetration of the Soul fails to apply rending - #13 by defallt

Below I will provide what I believe is the fixed code, based on defallt’s report

function _rending_multiplier(attacker_stat_buffs, target_stat_buffs, is_backstab, is_flanking, is_critical_strike, is_target_staggered, is_warp_attack, attack_type)
local attacker_multiplier = attacker_stat_buffs.rending_multiplier or 1
local target_multiplier = target_stat_buffs.rending_multiplier or 1
local attacker_backstab_multiplier = is_backstab and attacker_stat_buffs.backstab_rending_multiplier or 1
local target_backstab_multiplier = is_backstab and target_stat_buffs.backstab_rending_multiplier or 1
local attacker_flanking_multiplier = is_flanking and attacker_stat_buffs.flanking_rending_multiplier or 1
local target_flanking_multiplier = is_flanking and target_stat_buffs.flanking_rending_multiplier or 1
local attacker_crit_multiplier = is_critical_strike and attacker_stat_buffs.critical_strike_rending_multiplier or 1
local target_crit_multiplier = is_critical_strike and target_stat_buffs.critical_strike_rending_multiplier or 1
local warp_attack_rending = is_warp_attack and attacker_stat_buffs.warp_attacks_rending_multiplier or 1
local attacker_vs_staggered_multiplier = is_target_staggered and attacker_stat_buffs.rending_vs_staggered_multiplier or 1
local is_melee = attack_type and attack_type == attack_types.melee
local melee_rending_multiplier = is_melee and attacker_stat_buffs.melee_rending_multiplier or 1
local rending_multiplier = attacker_multiplier + target_multiplier + attacker_backstab_multiplier + target_backstab_multiplier + attacker_crit_multiplier + target_crit_multiplier + attacker_flanking_multiplier + target_flanking_multiplier + attacker_vs_staggered_multiplier + melee_rending_multiplier + warp_attack_rending - 10

rending_multiplier = math.min(rending_multiplier, 1)

return rending_multiplier, rending_multiplier > 0

end

from here: Darktide-Source-Code/scripts/utilities/attack/damage_calculation.lua at master · Aussiemon/Darktide-Source-Code · GitHub

fatshark please actually fix the bugs in your code, especially when they’re as easy as adding “+ warp_attack_rending”, if this isnt the correct code the team at fatshark should at least know what is

Steps to Reproduce (Required):

  1. equip the penetration of the soul talent on psyker

Reproduction Rate (Required):

Constant (100%)

Platform (Required):

PC - Steam

15 Likes
2

Thank you for re-posting! Hopefully this gets fixed in the next hotfix update!

8 Likes
3

Obligatory “first time” gif.

FirstTime

5 Likes
4

At this point it feels like wishful thinking, but I hope so too.

1 Like
5

the game still crashes if you press X too quickly in the inventory Id say thats more important than a mid talent not working

6

i think fatshark not bothering to take 5 seconds to add a tiny bit of code to their game to make a talent actually work is more worrying

7 Likes
7

Book? Book.

3 Likes
8

theyll get to it eventually

9

Ogryn vaulting has been broken on fences for a full year. There’s stuff like zealot talents that work differently from what the tooltip says since the early access beta. They won’t necessarily ever get to it

1 Like
10

I’ll bring this up in my next call with QA. :+1:

10 Likes
11

Thank you!

12

Fatshark has QA?

1 Like
13

Why now ? why not 6 months ago ?

14

It would have been raised to our database at the time of the initial report, but by bringing it to QA’s attention we can hopefully speed up a resolution. :slightly_smiling_face:

4 Likes
15

Thank you for looking into this Julia! On another note though, I’m in complete shock that the developers have been aware of this since October and it hasn’t been fixed. It’s a super easy ticket completion for whoever picks it up. This sounds like a serious mismanagement issue with your engineering managers/product owners that deserves a look by higher ups.

3 Likes
16

are QA the ones who should’ve fixed this? i’m not familiar with how game dev studios work

17

It’s probably so that their QA can confirm the issue, then push it to the devs via their development pipeline.

18

Of course, resolving it within one day before the game closes and all players leave counts as resolved