[BUG] Garbo Failing to determine diet - Invalid weight -1 for august scepter #1865
Comments
dizzydis
changed the title
|
my version of this error is:
Encountered when already full and re-running the script. Running |
|
I had the same error message as OP, then filled up on everything (food/drink/spleen), now get this message JavaScript exception: Error: Invalid weight -1 for distention pill |
|
Arashmin_20240502.txt for session log with this issue. Even if I try to put away all items that can potentially modify my diet into my collection case, I then start getting the negative weight error on cuppa Voraci tea, since those are able to be purchased and used - never mind that I did use one in my diet already. |
|
my version is: JavaScript exception: Error: Invalid weight -1 for designer sweatpants |
|
Fixed by #1867 |
Before Reporting
Ensure that KoLMafia and garbo are both up to date before reporting a bug. If you have installed mafia in a weird or non-standard way, let us know any details about that here. But also, if you've installed mafia in a weird or non-standard way, I'm telling you right now that that's your bug. Also, check existing github issues to see if this has already been reported. If it has, consider leaving a comment with any additional information you can give on that issue, instead of making a new one.
Also, read this.
Describe the bug
When running garbo, it errors with the message:
Error: Invalid weight -1 for august scepterTo Reproduce
Steps to reproduce the behavior:
Unsure - for me I just run garbo.
VOA is set to 6100.
Expected behavior
Garbo runs
Session Log
Additional context
First time seeing this.
Noticed there was a libram update to Garbo - and I see this check occurs in knapsack.
Autoscend finished a HC Standard S run, I pulled everything from Hangks, updated all scripts and ran garbo.
Before submitting the bug, I also made sure Mafia was up-to-date.
Encountered this on both versions:
I did get the new IOTM, bound it, and used it earlier before kicking off autoscend for the day.
The text was updated successfully, but these errors were encountered: