Lothrik (MaXiMiUS)

The main reason filters like this weren't implemented is simply because you rapidly run out of valid seeds. Each jewel only has a few thousand possible combinations, and out of...

I'm aware the glyph values are off. Blizzard nerfed them fairly drastically on June 5th, which broke a few key assumptions I made about glyph scaling. Unfortunately I've been too...

Glyphs should be updated now, as per build 42131: https://news.blizzard.com/en-us/diablo4/23964909/diablo-iv-patch-notes Let me know if you notice any remaining inconsistencies between in-game glyph values and what my calculator shows!

Tags and enchantments are now localized/translated. Skill name labels I could technically enable right now, but for a lot of languages it looks horrendous as the text is 2-3 times...

Unfortunately that's unlikely to change, at least in the immediate future. Allowing pathing down below the starting board would mean I'd need to handle the "origin" board positions in a...

> One related issue is that once you've attached a Paragon board and it changed its location, and finally decide you don't want to use that board, you can't move...

Those values are listed here: ```js "Rend": { values: [ "35", "33" ], }, ```` Cooldown and lucky hit values are not included as part of the description itself, as...

Those values are in ``barbarian.js``: https://github.com/Lothrik/diablo4-build-calc/blob/ebe888387dafc8f00db4444f8b346192f29afa4f/data/barbarian.js#L1173

It's easier to maintain if they're separated, particularly when the total number and/or position of unparsed variables changes from one build to the next. As an example, take Rend's current...

``#1``: I'm fairly certain what you're referring to is a parsing limitation. Blizzard frequently describes similar stats in an inconsistent manner, and beyond "exact matches" I have no real way...