Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Encounter object is missing some items that are showing in combatant view #88

Closed
christianallred opened this issue Jun 26, 2017 · 14 comments

Comments

@christianallred
Copy link

Namely direct hit, direct crit hit, crit types.

Also the heal critical percent is not getting tallied correctly in either the comabatnt objects or the encounter objects

@christianallred
Copy link
Author

See this issue as reference
RainbowMage/OverlayPlugin#57

@christianallred
Copy link
Author

I am sure there are more like this. These are simply the ones I found. I can look into the code base tomorrow and possibly submit a pr

@christianallred
Copy link
Author

Oh never mind source code is private

@christianallred
Copy link
Author

V1.5.1.3

@ravahn
Copy link
Owner

ravahn commented Jun 26, 2017

To re-word what you are saying - some data that is visible within ACT's main window is not exposed as ACT variables for overlays. I will take a look. All of the Crit data is coming from original ACT code except for DirectHeals Crit, so I don't know anything about inconsistencies with those variables.

@christianallred
Copy link
Author

christianallred commented Jun 26, 2017

Yes.

When i got home from work today I will post what the object data that i am getting for each of the two objects that RainbowMage is pulling. I am writing a plugin overly for RainbowMages Overlay Plugin. And according to rainbow mage it is just grabing the objects from Your plugin.

His overplay plugin grabs 2 variables per encounter.

Encounter, Combatants(List)

Info in these two variables are inconsistant.

The HealsCrit seams to be broken in ACT itself, an di can see that by looking in the combatants table so thats not really what this Issue is about. Although I found it as a side note.

The real problem is what doesn't exist in the Ecounter object, that does exist on the individual Combatants Objects.

Namely the items listed in the in the issue that i linked above. It is my understanding the Encounter object is simply a totaling of the combatants list items.

@Squall-Leonhart
Copy link

i turned off crit types and enabled critdam% and critheal%
both work for the encounter view.

@christianallred
Copy link
Author

Is critdam% exit damage / total damage or crit hits / total hits

@christianallred
Copy link
Author

The later is much more useful

@ravahn
Copy link
Owner

ravahn commented Jun 27, 2017

It's the percent of crit hits, not crit damage. from the original ACT code:
return (float) ((double) this.CritHits / (double) this.Hits * 100.0);
for all outgoing damage

@christianallred
Copy link
Author

Man that is poor naming... come on ACT

@ravahn
Copy link
Owner

ravahn commented Jun 27, 2017

Working on this still, but it requires careful testing unfortunately. I'm not sure there is much value in general for encounter-level data for most players - is it useful to know the whole party's Direct Hit or overheal information vs. seeing it on the player level?

So, it may be a version or two before I add.

However, if you're writing an ACT plugin or have access to the Advanced_Combat_Tracker namespace in your Overlay plugin, you can add the encounter variables yourself. Just be sure to make sure it was not already added by checking the key, i.e:

if (!Advanced_Combat_Tracker.EncounterData.ExportVariables.ContainsKey("DirectHitCount"))
{
Advanced_Combat_Tracker.EncounterData.ExportVariables.Add(...)
}

@christianallred
Copy link
Author

Yeah no worries . I can actually roll it all up from the combatant list anyways. I just wanted to let you know it's missing

@ravahn
Copy link
Owner

ravahn commented Jun 28, 2017

Sounds good, thanks for the update. I did add Combatant export variables to 1.5.1.4 (just released) in case they are useful, but am going to hold off on the encounter-level ones.

@ravahn ravahn closed this as completed Jun 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants