Patch Notes, Sunday, May 29th, 2011

[Troy]

Originally Posted by kanras [You must be logged in to view images. Log in or Register.]

Nothing about hate amount per proc changed. Proc rates were fixed to replicate some well-documented rules established from heavy parsing in these two threads:

http://www.evilgamer.net/forums/showthread.php?t=58

http://www.thesteelwarrior.org/forum...hp/t-5351.html

Main points:

<proc rate stats>

It's a little different here. Since our dex cap is 255, main hand proc rate scales from 0.5PPM @ 0 DEX -> 2.0PPM @ 255 DEX. The stock emu code that we were previously using would only increase the proc rate 0.5PPM across the 0->255 DEX range. It also was attempting to proc once per attack for the offhand, which was weird. Basically, make friends with a shaman.

Is this to say that proc rates are now the same for all weapons?

I remember (this experience is from p99 a month or so ago), for example, the Bonethunder Staff having its Ward Undead proc go off 1 in 3 swings if not more often as an Erudite Cleric with normal dexterity. That is like 5 PPM and the only reason the staff is useful at all really.

[Hagglebaron]

Thanks once again devs for the hard work.

[Uthgaard]

Originally Posted by Troy [You must be logged in to view images. Log in or Register.]

Is this to say that proc rates are now the same for all weapons?

No.

[Troy]

Originally Posted by Uthgaard [You must be logged in to view images. Log in or Register.]

No.

Cool. That would have been a little boring!

[PureLo]

yet it currently or as of the past 2 days prior to today feels as if that is the case, hence the noticing of a change. So not only does it feel that proc rates are off all together, but it also feels as if it has been plateau'd to all be the same due to in-game experience and Kanras' explanation of change. Considering the hate from proc's was also reduced this indicates changes that alter the class balance and disrupt the flow of the game from the patch that was implemented not too long ago.

Further explanation would be greatly appreciated, just so many know how it is they have to change to the style of programming again in order to be affective. Another thing is that having started the research to supply "proof" or "avoidance" of this change i did notice that the jump from proc effectiveness to non proc effectiveness that occurred here between this and another recent patch hadn't occurred according to patch notes from SoE.

[skorge]

I've been wanting to post on this awhile, but have held off to be totally sure of it, but it definitely seems like the buff "vampiric embrace" proc rate has been nerfed big time. I used to see it go off almost every fight, sometimes 3 or 4 times...now im lucky if it goes off just once in every 3 or 4 fights. I know this doesn't seem huge but when you are using a RoA to melee down mobs...the vampiric embrace buff is really nice, now - not so much.

[Uthgaard]

Originally Posted by PureLo [You must be logged in to view images. Log in or Register.]

Considering the hate from proc's was also reduced

Not sure where you're getting this idea. Update before last, there were two independent increases to proc threat. I increased it from the spell end, kanras increased it from the code end.

[Torven]

Well, proc hate relative to melee aggro is less if double attacks and backstab now add hate correctly. If melee aggro doubles then proc hate is going to be half as effective for keeping mobs off of rogues and monks.

[Rogean]

Interested in seeing if Kanras's potential crash fix had any impact on lowering the amount of crashes some of you are getting (If you were getting them a lot before).

[mwatt]

I haven't had a crash to desktop since Kanras put in his fix. However, I have made several changes to my system myself over these past few months, sometimes apparently licking that problem, but it always came back. So, I'd say it looks promising but too soon to tell.

On a probably but not certainly unrelated note, I'm having more zone and port crashes than I used to, and also wierd login timeouts and other login issues. It might be Comcast though. I dunno.