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

Heartsteel is missing its mythic passive #50

Open
rdavis0 opened this issue Dec 7, 2022 · 4 comments
Open

Heartsteel is missing its mythic passive #50

rdavis0 opened this issue Dec 7, 2022 · 4 comments
Labels
help wanted Extra attention is needed

Comments

@rdavis0
Copy link
Contributor

rdavis0 commented Dec 7, 2022

The new item Heartsteel 3084 is missing its mythic passive. It should have: passives[1].stats.health.percent: 1.0.

@jjmaldonis jjmaldonis added the help wanted Extra attention is needed label Dec 7, 2022
@rdavis0
Copy link
Contributor Author

rdavis0 commented Feb 9, 2023

This appears to be an issue with the way the mythic passive is formatted on the wiki. There's no existing stat defined for % hp bonuses, so Heartsteel's mythic is just defined as [spec]. I'm working with the wiki team to see if we can get a % hp bonus stat defined, which would then require updates to the parsing code to pick it up.

@rdavis0
Copy link
Contributor Author

rdavis0 commented Feb 9, 2023

After speaking with the wiki team, they don't want to create a new stat for %hp bonuses since Heartsteel is currently the only item that has one. The compromise we reached was to edit the mythic bonus in the wiki's item data module like so:

["mythic"]  = {
            	["hp"]  = "1%",
            	["spec"]  = "6% increased [[size]]",
     },

That leaves us with the problem of how to convert that 1% string to a passives.stats.health.percent value. I've been looking through the parsing code, and I'm not sure where's the best place to do that. Any ideas @jjmaldonis?

@jjmaldonis
Copy link
Member

Hey, I don't have my head in this right now. At the end of the day we will not be able to represent the entirety of the complexity of the items in this JSON, which means that some manual effort will be required by anyone who wants to use this JSON to represent items in their code.

This may be one of the unfortunate cases where user intervention is required. If the wiki team isn't willing to create a new stat then we may be out of luck for the time being.

After looking into the details of what this new item does, it is infeasible to represent what it actually does using just the JSON. The calculation for this part of the passive will have to be done using user intervention. So I don't think it's particularly important that we represent this information accurately in the JSON. In fact, representing this information in the current JSON structure may be misleading to someone who is only reading the JSON.

@rdavis0
Copy link
Contributor Author

rdavis0 commented Feb 10, 2023

To be clear, I'm just referencing the mythic 1% hp bonus, which is a typical mythic passive and does fit nicely in the JSON as currently structured: passives[1].stats.health.percent: 1.0. We just need to capture the value from the wiki. The mythic size bonus and the stacking hp passive are obviously more difficult to represent in the JSON as it stands, if at all.

I'll dig a little deeper and see if I can solve the %hp bonus. Thanks for the reply.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants