-
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
Buzzed on Distillate #1060
Buzzed on Distillate #1060
Conversation
…ods easier. This has a lot more that could be done
a586365
to
fef5878
Compare
Codecov Report
@@ Coverage Diff @@
## main #1060 +/- ##
============================================
+ Coverage 29.05% 29.07% +0.01%
- Complexity 13948 13956 +8
============================================
Files 1035 1035
Lines 160822 160807 -15
Branches 35200 35195 -5
============================================
+ Hits 46733 46750 +17
+ Misses 105595 105561 -34
- Partials 8494 8496 +2
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To confirm: entauntauned is correctly updated by the ConsequenceManager?
Yes but I'll add a test for that now |
…, as well as testing the rest of gaining Entauntauned working correctly
…nto buzzed-on-distillate
…uences.txt and then just trigger a visit to parse it
This tracks the current and next Buzzed on Distillate effect mods, as well as making it possible to track whole effect mods through consequences.txt
There is a bigger refactor to consequences.txt that should be done in my mind - make it o that each consequence knows how it can be checked and if it should be checked (effects that you have, items that you have or have equipped, skills you know etc) and then a single fn to check them all if necessary. Instead we have loads of repeated "check" functions. Anyway, that will come another time.