I have a crafted 658 one-handed weapon that is not counting towards Carved of the Undermine. Just had a veteran one-handed weapon drop, upgraded it to 645, no Feat of Strength. I rechecked my gear, equipped all the bad 645s just to make sure every slot was filled, nothing.
Edit: I have now acquired a 652 weapon, still no Feat of Strength.
Edit 2: After nearly 3 hours it finally triggered.
Edit 3: It was a Charged Slicer.
A single one-handed weapon is not enough to trigger the requirement, although the rules have gotten muddier since DF. You should still only need to spend crests on one weapon regardless of what level it is, but to gain credit for the feats of strength at a crest threshold, you need at least the equivalent of two hands’ of weapons at the target item level.
This can be in the form of:
- One two-hander
- Two one-handers
- One one-hander, one shield
- One one-hander, one offhand
The only combo which doesn’t count here is two offhands/shields, as they can only be equipped in one slot.
Your achievement likely triggered once the 652 weapon you looted became bound (trade timer expired, or equipped).
1 Like
Can’t tell if you didn’t read my post or are a chatbot. I crafted a 1h weapon, I looted another and upgraded. Did not trigger. Looted another weapon and upgraded. Did not trigger for hours. The problem is that the crafted weapon was not counting, not just that the stupid FoS is also buggy.
Yeah, I missed that. No need to be a dick about it.
Odds are the item you crafted might be glitchy itself, as my own crafted items did not cause an issue with awarding the FoS. It’ll be helpful to provide that information on which specific item so they know what to possibly look at, as otherwise they have almost nothing to go off of here.
1 Like
Your equipped neck is only 632
Yes, because the 645 neck I have has worse stats. Please, I beg, think before you reply.
It still didn’t work after receiving 2 additional weapons, so I don’t know if you can say the crafted weapon had a problem at all.
It did work after the second dropped weapon, it just took a couple hours to finally trigger at that point. Why can’t you people read the entirety of what I wrote before making judgment calls?
Your main post says you got a weapon upgraded to 645, and then edited to say you got a 652 weapon, and then edited again to say after 3 hours it triggered. The implication here is that 3 hours after you got a 652 weapon, the achievement triggered. Which at that point, you can’t even narrow it down to any specific weapon not working.
A further 3 hours had passed, yes, but more than that had passed between getting the weapon I upgraded to 645. I am not trying to run a controlled experiment, I am trying to relay information about a possible bug to a bug report forum. I only have one data set.
Did you run a potentially misleading script to verify this?
If you mean that script that supposedly tells you what you are missing, then yes I did, but it was gibberish, talking about like 150s and stuff.
That’s because weapon types are split into a few different categories: Twohand, MainhandWeapon, Offhand, OnehandWeapon, and OnehandWeaponSecond. For enhancement, only OnehandWeapon and OnehandWeaponSecond are and it may populate two hand, main hand, and offhand as lacking. I’m curious to know exactly what the script spit out.
Unfortunately I did not screenshot it. I do know it didn’t have the 658 for my Charged Slicer.
The script, if you’re using the one I’m thinking up, prints out item slots that are not high enough level for the achievement. So if it only said like 150 main hand, 150 offhand, but didn’t print out onehandweapon or onehandweaponsecond, then those 2 categories would’ve been counted, with the charged slicer occupying one of those slots.
A simple way to know is to just dump all the item slots. You should theoretically see 662 for OnehandWeapon and 658 for OnehandWeaponSecond if the carved slicer is being counted.
/run local n=tInvert(Enum.ItemRedundancySlot),a;for i=0,16 do a = C_ItemUpgrade.GetHighWatermarkForSlot(i); print(a, n[i]) end
It’s counting it with that script. All I can say is that with the 658 and 645, I had over 4 hours and multiple logouts and full client restarts with no luck. I got the 652, still didn’t pop, so I went on my merry way getting stuff done. After a further 3 hours and some character swaps, it finally triggered.
Sounds like the achievement was just being grumpy or something, not that the crafted weapon wasn’t being counted