I came to the conclusion that during combat it was better to see damage sorted by dps because it is more dynamic.
If you are the person who died half way through a long fight and was revived, if it was sorted by total damage you would be stuck at the bottom of the pile indefinitely. It really boils down to what people expect and unfortunately what people expect often changes based on the context. I have asked this of my raid group's DPS on many occasions and always get a different answer. Sorry for my english, im no native Speaker and quite lazy when it Comes to thinking about formulations in foreign languages In this case playerB should be leading, not playerAī) Will there be those fancy bars to visualize the relative dmg done like torparse did? I think it should be sorted by DMG done, we often had some weird results like
#Parsec swtor parser professional
U did a great job with providing this wonderful tool to the community! My whole guild has recently switched from torparse to parsec because of ist superiority in Terms of stability, Performance and professional Features like filtering Options!Ī) Currenty the raid dmg popout list is sorted by DPS. I believe this will normalize the damage taken between fights since it will no longer be variable based on absorb shields effects applied to you.Īfter both of these changes were made the numbers line up with TorParse except for some rounded decimal place differences.Īnyway, thanks for your feedback and you should see these changes make it into the next release of PARSEC this week. So after reviewing your data I have decided to make two changes to PARSEC:ġ) Combat end events will be handled the same way but calculations based on time will now use the last combat end event time instead of including the floating combat window.Ģ) Damage taken will now automatically include absorbed damage.
Obviously this skews the numbers by 1 second. PARSEC opens a 1 second window after a combat end event in order to pick up any out of order combat events. Because of the out of order logging that occurs with the combat end event each parser has a different approach to combat end. This difference is explained by how PARSEC deals with the combat end event. Yes some of the other numbers are slightly different. Damage done, APM, healing recieved, etc is different. Unfortunately, they are still not identicle. And if you have any feelings about it, share them and convince me to change it As a tank myself I can see the value in both calculations. This difference in calculation affects all of the damage taken numbers. If you add the Abs and total column from PARSEC you get 303614 which is the same as TorParse's numbers. The difference you are seeing is that TorParse's damage taken calculations include absorbed damage. PM would probably be the best way to contact me.Īctually, they are identical. If there is more information I can give, I would be happy to. One of them reads horribly inaccurate, the question is which. While I can confirm they are the same fight. I am submitting the log here for your inspection, along with the Torparse link.Įdit: Upon further inspection, almost no information from the two fights are the same. While I found the tanking information quite nice I have found some pretty large discrepancies between parsec and torparse.
You could have the database automatically, provisionally classify attacks based on circumstantial evidence (if you see it dodged it is M/R, if shielded it is M/R or K/E, if resisted it is F/T, etc.) and then let some of the other number crunchers post more authoritative classifications that get marked in the database as confirmed. I feel like a database of attack types would be so useful to be worth it. It is possible to build a database of attacks and their attack type based on mitigation results over time, but this is more work than it is worth since it would be useless on new content. With this in mind, i designed parsec to display total mitigation rates like this:Īs a tank myself i find these statistics usefull in determining my performance and gear effectiveness even though they are not ideal. These limitations along with the complexity of the mitigation rules make it impossible to accurately display mitigation in seperate buckets.
Second, if an attack is avoided its damage type is not reported in the log. First, log files do not specify ranged/melee vs force/tech. Unfortunately, the log files have some limitations when it comes to damage types and attack types.
0 kommentar(er)
