DiabloFans

Wow! thank you, I look forward to possible changes in the future. Please take other community consideration into account. I am most definitely not the only one using the filter, hah.

In the long run this doesn't matter, just thought it interesting! I bet a few other players' and creator's builds are in the same situation.

A few of my builds were created before the patch "Season 18" became available. I recently updated them and they are now labeled as such.

One of my builds was upvoted to be within range, but only displays on the front page frame when the "this month" filter is selected.

"This patch" does not display the build on the homepage display frame.

At the time of this posting:

https://www.diablofans.com/builds/104635

Note: filter to wizard first by clicking the wizard icon.

Wildcard searches in build name would be nice, either that or have it search as a "Contains" method of search

Being able to select multiple options from the Group type dropdown would be nice. Often I think players are either grouping in season or they are mostly running solo, in either case they would often want to selecting one of: Solo or Group, and then also add in Hybrid to their selection.

load of the page each time I want to hit "Top - week" or "Top- month" or Top - all time" perhaps not the best method. Wait until hitting the filter button to reload perhaps?

As a user I tend to prefer to see "Top - All Time" or "Top - Month". I can imagine doing the week ends up saving the default load time, and improves performance, but this is likely increasing the traffic against this page, if most viewers are like me.

Can't think of anything else as yet. Perhaps other viewers can, if so please comment.

Thank you for the update, good to know it's at least being worked on.

It took awhile to make that one, and while it would be great to have it as soon as possible, not worth remaking at the moment (T13 build, and no backup text file on hand).

I'll check in later to see if it has been fixed. Thanks again for the update.

HELLO? anyone home?

Can I get a reply at least on the status of fix here?

This build I just edited, now reports an error. On latest Chrome version, though the other browsers show the same.

https://www.diablofans.com/builds/100458

https://imgur.com/RMy2O7D

Wow! thanks for the update, and the epic response time on that fix TuhMuffinMan. I should buy you a blueberry or poppyseed.

I've checked and all of my 2.6.1 builds now appear to be labeled 2.6.1 as expected. Thanks!

Is there a reason the builds that I've been creating and labeling as "PTR" during the 2.6.1 PTR now have that label removed, and instead are labeled 2.6?

I was expecting these build listings to get labeled 2.6.1 now that 2.6.1 is live.

If that version isn't available in DFans yet, they should still be labeled "PTR", but neither of these states are true.

Great guide. Well written, high detail, good analysis. So well done I've linked it near the top of my old posts. I hope this helps clear up some of the issues I have created by somewhat accurately, but sometimes imprecisely delivering concepts to the masses.

Especially the listed formulas will come in handy. Knowing about the speed coefficients, etc., and how to properly calculate your AS breakpoints is extremely important.

I had another laugh - The wording on the adjustment of the window from 2.5.0 with MH was worded so poorly. 'Number of procs generated has been reduced' is indicative of chance being reduced in some manner, which is very different from 'hey, we reduced duration of the MH window by 25%'. Hah!

Thanks also for linking the Fazula chart. I had been adhering to the recommendations already, but didn't know in that much detail the tradeoff. Definitely for solo you need the higher stack affix, even if non-ancient.

Love the content sVr. Thank you.

Ah, thanks for the clarification!

That makes Hydra MH proc damage significantly decreased in that case.

EDIT: Apologies, I read your initial post on the bnet forums wrong, hah! Mustve been out of my mind.

Here's the link if interested:

https://us.battle.net/forums/en/d3/topic/20758776120#post-8

It's much better to do what is required first on live, then make a character copy. Your effort will be wasted if they wipe the PTR otherwise.

It is labeled as PTR only, meaning it doesn't exist on live. The issue was an internal bug fix that was never exposed to players. That being said, they did change something to fix it.

sVr did some testing, and found that nothing appears to have been changed with paralysis / MH proccing, it still scales off of AS for both damage and cast rate.

My best guess is that it might have been the core skills' damage (the hydra itself) and not the MH proc that was wrong.

I find it helpful to aim at the feet of the target model. I don't wiggle per say, but sometimes i edge it in very slowly. Typically this helps with smaller monsters or the 'floating' monsters.

There is some amount of chance due to paralysis, but you can limit this with being at higher attack speeds. I also find repositioning helps find the better angles to deal damage in, and also keeps you alive more than not.

Thanks for clarifying Bagstone. I suppose I'll remake the build then and just delete the old one.

Awesome response time by the way.

Hi there, my build hasn't disappeared, but my issue appears related.

I created a build for the 2.6.1 PTR before the label was available. I can't see a way to edit it to label it as such now.

Now that there is a PTR label up, can this be adjusted on my build to label it as "PTR"?

http://www.diablofans.com/builds/94478

Thanks!