-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Bugfix - dissection drop rate #62433
Bugfix - dissection drop rate #62433
Conversation
I did think that it was odd that I was successfully harvesting with things like 95% failure chances - but thought maybe that was intentional, in that certain things would always drop based on config. |
So, this does appear to be the correct change after some play testing in the discord. What we need is to go here: Cataclysm-DDA/data/json/harvest_dissect.json Line 686 in 6957090
and add something like
to each entry in zomborg and broken_cyborg in that file. if someone could add that to this PR or a clone of this PR and test it, I'd be much obliged... preliminary reports are that this should work. |
Adding scale numbers to dissection JSON and reopening |
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
I will try to review the JSON end tonight or tomorrow |
Please include the typo fix mentioned earlier, in case this ends up being the preferred solution.
|
A nice to have would be a test that makes sure result numbers are within expectations. Doesn't necessarily have to be part of this PR, though. |
…alpern/Cataclysm-DDA into bugfix/dissection-drop-rate
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
There's nothing wrong with leaving the debug messages in. |
Eh, they were mostly just for checking the numbers as I was testing - don't want to spam the logs with stuff that wouldn't be super meaningful. If other people think the min/max and roll values would be helpful, I can make the messages a little more explicit and add them back. Also instinctive reaction to what felt like leaving a bunch of console.logs in my finalized code haha |
There's a filter for debug messages and I wouldn't consider it spam in the first place. But of course there's also nothing wrong with removing them. And making them more compact and more meaningful is obviously also a good thing. |
Summary
Bugfixes "Dissection drop rate"
Purpose of change
Fixes #61423
Describe the solution
Previously, the section to set roll value had a condition where the value was being set, except in cases where the action was dissection. So, the roll value was always 0 for dissection, causing items to never be dropped in some cases. Removing the check that the action is not dissection allows the roll value to get set.
Describe alternatives you've considered
I'm just doing what the smart people said to do
Testing
Debug spawned and killed 10 prototype cyborgs. Was able to successfully harvest a Power Storage CBM from all.