-
Notifications
You must be signed in to change notification settings - Fork 73
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
gift packages. checkitems #1860
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #1860 +/- ##
=========================================
Coverage 36.32% 36.33%
- Complexity 18757 18762 +5
=========================================
Files 1081 1081
Lines 166332 166346 +14
Branches 35391 35394 +3
=========================================
+ Hits 60424 60442 +18
+ Misses 96032 96026 -6
- Partials 9876 9878 +2
Continue to review full report in Codecov by Sentry.
|
vs.
What is the difference between "Damage Aura" and "Thorns"?
Damage Aura. I guess? Doesn't require opponent to hit you?
Is that only when they attack (not stunned) and actually hit you? In any case, it seems like Thorns and Damage Aura both need an element. I think those two modifiers need some work. |
Thorns and Damage Aura are intended to be used for Frosty or the Wall of Skin -- bosses where you care about how many sources of damage you have, but not how much damage they do, or of what element. And also the wall of bones, where you care about /not/ having any passive damage sources. Thorns is when the enemy hits you, damage aura is when they don't need to hit you. They're both working as I intended. For example, if you add numeric damage, groovy prism necklace is 5 of each element for 25 total and cannonball charrrm bracelet is 27.5 hot, but for the wall of skin / Frosty the prism necklace is much better due to the damage cap. They were added in #1624. |
Ok. It's news to me that a bottle opener belt buckle does not operate the same way as a hippy protest button, but considering I have never used either, I am no expert. Interesting that they have the identical "Enchantment" text in the item description, but that you end up with one or the other of two different Modifiers - and you have to look at the Wiki in order to figure out which one it is. I think that's a first for us. There is still a bug with DebugDatabase not being able to parse Thorns correctly, but I'm not going to spend more time flailing at that; not throwing an NPE is good enough for now. I plan no more new content for this PR. |
Now, we print that before processing results.
I got NPEs on a bunch of items in checkModifiers because modifiers.txt contained a value for a modifier but when we parsed it, we got a null. As it happened, it was always the Thorns modifier.
I suspect it is because we have 2 patterns for it (3, now, since I found another one), and only one has a numeric value that we parse.
We actually do a bad value of parsing the number, since KoL expresses it as a range - and often has an element associated with it.
Here is a bunch of errors that checkitems now prints when it detects something like that.
Everything that says "missing a value" caused an NPE.
It looks like both Thorns and Damage Aura should actually have an Element.