Procs - Level Limit
Found a small bug today. I am not sure if this was something introduced with the newer source or not, no one noticed it with our old source Back in January 2015. Using something like a Throneblade of Ykesha (sp), which is a level 47 proc on lets say a level 41 Necro pet it will proc sometimes. Most of the time you get a "Your pets will is not sufficient", other times it gets right through. I have done multiple parses and with this combination it is around 1/5 times the proc makes it past some check.
|
Okay dug further into the code. When the weapon is failing proc, it is failing where it should. When the weapon is actually procing, it is here...
This is around line 3845 in attack.cpp Code:
if (!rangedattk) { |
Here is a hit.
Code:
[Fri Jan 22 10:52:54 2016] [Combat] Proc chance 0.11 (9.75 from bonuses) Code:
[Fri Jan 22 10:53:15 2016] Zibekn slashes a giant skeleton for 59 points of damage. |
So, spell '945' is proc'ing ok..but, spell '445' is not?
|
Yep. Still digging into the issue though
|
Almost sounds like a required vs recommended level thing.
|
|
My line in my source looks just like that? May have to spell it out for me Demonstar.
|
That's where the proc is added to the npc.
You could probably add a level check there to eliminate level-based failures. |
I think I have it, adding some code in now.
|
It's adding the proc to the "PermaProcs" for some reason. I have no idea why, but it looks like that gives the NPC 2 chances to proc a proc from a weapon.
|
Quote:
|
Are you saying that client pets should not be processing this: https://github.com/EQEmu/Server/blob...ables.cpp#L224
EDIT: What I'm seeing is the possibility of two calls to this function..one with the primary weapon, the other with the secondary weapon. This would allow a proc from each weapon to be added to the pet's weapon proc list. EDIT2: There is a log message for debug > '11' here: https://github.com/EQEmu/Server/blob...ables.cpp#L234 |
Code:
if (foundslot == MainPrimary) { This appears to be working. Is this safe or is there a better way of doing it? |
Quote:
|
All times are GMT -4. The time now is 02:53 AM. |
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.