(2.6.7a seems to have fixed the Flurry explosion not receiving the 6pc bonus when you manually stop channeling, but still doesn’t work with other skills like EP/SSS/etc) 6pc does affect ALL damage while channeling TR and does not require hitting 30 times within a short period to proc the size bonus as described in the initial patch notes. Then extra radius effect seems to last 2 seconds after stopping channeling, but the damage bonus does not seem to extend to match the visual. It is a 151x damage multiplier that is active while channeling TR. * The initial patch notes are incorrect, and the in-game 6pc is working slightly differently than as described.
Sweeping Wind damage is increased by 15000% (6 pc) Hitting with Tempest Rush while Sweeping Wind is active will temporarily increase the size of Sweeping Wind after hitting over 30 times within a short period.(there are some tick breakpoints involved but nothing worth getting into) So if you consistently stay above 2 APS may have trouble maintaining spirit without Epiphany & additional RCR. So the base 30 spirit cost is the cost at 1.0 APS with 0% RCR. * 50 Sprit Regen basically allows you to almost pick any TR rune you want… but keep in mind TR cost scales with APS. (4 pc) Attacking with Tempest Rush reduces your damage taken by 50% and increases Spirit Regen by 50.5% movement speed per stack = 65% movement speed bonus… nice, but still not In-Geom nice… You will still have to select the correct rune element to gain the +% element damage bonus. So you may want to hold off investing too much in a specific element until it gets fixed. * On PTR, the gain all runes worked except you didn’t gain the higher base % weapon damage unless you use Bladestorm. (2 pc) Sweeping Wind gains the effect of every rune, and movement is increases by 5% for each stack of Sweeping Wind.Patterns of Justice Mechanics (Updated to 2.6.7a) You lose it if you change zones however, so when using Kyo’s Belt = Meh! You can still snap-shot Mythic Rhythm with Sweeping Wind.Sweeping Wind does NOT proc AREA DAMAGE.Their spawn rate is still linked to the attacking skill’s proc coefficient (Fists of Fury + Electric Field are your go-to proc skills as sweeping wind by itself can’t proc tornadoes)
So even though they look sexy their damage is largely superficial. Damage of Lightning Tornadoes generated by Cyclone do not scale with # of stacks of Sweeping Wind or APS.APS still caps at 5! (TR channeling cost 5 aps is… high!) Damage scales with APS (ie - counts as its own multiplier) So Echoing Fury’s (75%), Seize the Initiative (30%), Flying Dragon (~2x APS) are all viable options for various builds.So generally all damage will be partial crits, which are evaluated at some internal frequency less than 60Hz (typically 4-12Hz depending on your APS) But since the damage is calculated at a higher frequency then displayed the color of the damage number is dependent on if > or < 50% of the sub-ticks crit or not. Internally each displayed tick is actually the sum of multiple sub-ticks that occur at 60Hz or so. Damage is displayed 1 time per second (1Hz) dealing the listed weapon damage to all enemies in range.Here is a link to my old thread on the old forums in case you want to read up on some possibly outdated monk mechanics like TR on page 16: As Blizzcon cut the PTR testing short and changes made before live, expect there may be quite a few undocumented changes that may not be listed in the patch notes… so please post if things don’t jive on live (I don’t do any datamining or coding… just excel & mspaint!). Now it makes sense.Since Patch 2.6.7 introduced a new Monk Set, got off my lazy butt to put together this brief refresher on the mechanics of sweeping wind and the new affixes I was able to test on PTR. When I tried to use this 20 msec pulse as a "Gate On" signal to my Mono/Poly, the resulting note would only be 20 msec long. But of course! The trigger is not intended to be a "gate on" signal (which would need to stay on for the entire duration of the intended tone) but it is merely a pulse that is supposed to mark the start of a discrete event.like of a drum sound. I found that the trigger is a +5V pulse (which is fine) and that is only 20 milliseconds long (whoa, short!). To trouble-shoot, I plugged the 707's "Trigger Out" into my oscilloscope and got the picture below. The problem was that note coming out the Mono/Poly was just a tiny little "blip". I was hoping that it would trigger the notes on my Mono/Poly so that I could create some sweet syncopated robo-rhythms. When I got the TR-707 home and out of the box, I first wired it up to the "Gate In" on my Korg Mono/Poly.
0 kommentar(er)
