[Bug] Crash MC 1.21.1 client when MC-577 is ON
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 215
- Forks
- 50
- Avg merge
- 9d 6h
- Merged PRs (30d)
- 1
Description
Bug Description
Client crashes whenever mass drop straight from crafting result slot is attempted but mouse is clicked next to the item (or somewhere else entirely). Turning off MC-577 fixes the crash, but no longer supports using mouse to drop items from crafting slot. Lose/lose. :^/
How to Reproduce?
- Turn on MC-577.
- Go to crafting grid (or elsewhere, crash happens in many places).
- Try to use mouse button to mass drop items straight from the crafting result slot (works), but miss the slot (click anywhere other than the slot item).
- Client crashes.
Expected Behavior
- Turn on MC-577
- Open crafting grid with no room in inventory for crafted items.
- Craft all items, throwing them instead of placing them in (full) inventory.
- Client doesn't crash. Items on the ground.
Version
Debugify 1.21.1+1.0
Fabric/Quilt Loader Version
0.16.10 for 1.21.1
Logs or additional context
Sample crash report: https://mclo.gs/TXSEg0D
Has not been reported.
- I made sure this bug hasn't already been reported.
Is on most update to date version.
- I made sure I am using the most up to date fabric/quilt loader and mod version.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the sample crash report at https://mclo.gs/TXSEg0D, then reproduce the failure with MC-577 enabled by missing the crafting result slot or clicking elsewhere. Trace the crash across the crafting grid and other reported locations; done means mass-dropping crafted items with a full inventory still throws items without crashing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100