Copypasta from my other comment: Yeah it does appear limited to 1 kill per sweep, making it far less useful vs what’s described. I’m sure it’s by design but as usual, wrong description.
and the code
templates.ogryn_blo_melee = {
class_name = "proc_buff",
predicted = false,
proc_events = {
[proc_events.on_hit] = 1,
[proc_events.on_sweep_start] = 1,
},
specific_proc_func = {
on_hit = function (params, template_data, template_context, t)
if not template_data.allowed then
return
end
if not CheckProcFunctions.on_melee_kill(params, template_data, template_context) then
return
end
template_context.buff_extension:add_internally_controlled_buff("ogryn_blo_melee_active_buff", t)
template_data.allowed = false
end,
on_sweep_start = function (params, template_data, template_context, t)
template_data.allowed = true
end,
},
}
At a glance, this line limits it to 1 kill per sweep template_data.allowed = false as there is a check and a return at the top of the on_hit func if it’s false. Sweep start resets allowed to true.
I love nerds like you so interesting to see behind the scenes.
I think its just a poorly worded talent or a case of “bethesdas bug”- where bugs are so prevalent it becomes impossible to tell if things are working as intended or not.
LOL nothing quite like Bethesda Bugs in DT…so far.
You greenbeards are spoiled now, back in the Elder Scrolls: Daggerfall days, it took a PC Gamer CD to get the big-ass-for-back-then patch it for 30 mins (and pray it succeeded) as it was Buggy AF.
Here you just have to wait ~6 months …
the wording is pretty precise and different from “on melee killing blows” or “on melee kill” and it instead specificies “on attack” so one per attack. so to me it suggests it’s by design.
unless it says something different ingame? idk. to me when i read this pre-patch i immediately noted the wording and knew that this is how it would work
Fair point, but still a bit too ambiguous imho, it could be worded better to avoid any confusion . Something like “On one kill per attack” or whatever.
“On Killing Melee Attack” is not ambiguous in the slightest. It is a Melee Attack that has Killed. A Melee Attack has either Killed or it has not Killed. If your Melee Attack has Killed, then you get a stack. If not, you don’t get a stack.
Right, that’s why others were confused too in the other thread+, because it was unambiguous; MB.
FS is known for their precise, clear wording after all.
TBF that doesn’t necessarily suggest that THIS wording is inaccurate, just that descriptions don’t always match up generally, and that’s going to make everyone second guess everything (reasonably so).
I tend to agree with @GreyMaria that the wording of THIS talent is pretty precise and not misleading (doesn’t mean it couldn’t be EVEN more clear). Also understandable they don’t want you to get a free shot for attacking like twice with a BM weapon.