Mining spawner modpack bugs #1047
Labels
No labels
Area-Assets
Area-Backend
Area-Conduits
Area-Datapacks
Area-Lang
Area-Mod Compat
Area-Parity
Area-Rendering
Good first issue
MC-1.19.2
MC-1.20.1
MC-1.20.4
MC-1.20.6
MC-1.21
MC-1.21.1
Modtoberfest
P-0-High
P-1-Medium
P-2-Low
Status-Awaiting Response
Status-Behind-Flag
Status-Blocked
Status-Cannot Reproduce
Status-Duplicate
Status-Help Wanted
Status-Incomplete Report
Status-Invalid
Status-Needs LTS Backport
Status-Needs Updating
Status-Stale
Status-To Implement
Status-Triage
Status-Wontfix
Status-Wontmerge
Type-Backport
Type-Bug
Type-Documentation
Type-Enhancement
Type-Question
Type-RFC
Type-Suggestion
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Team-EnderIO/EnderIO#1047
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Is there an existing issue for this?
Current Behavior
When some players on my server mine
minecraft:spawners (vanilla and modded) the spawner doesn't break and a Ticking Entity exception my occur crashing the server or the spawner may just not break.Crashlog Ex1: https://pastebin.com/mMKbEQ38 (ad astra lunarian spawner, wouldn't break, crashed server)
Error Log Ex2: https://pastebin.com/EJ0GxFZJ (blaze spawner, wouldn't break)
It may be noted that the crashes occured when Person1 mines any spawner, after installing Neruina mod it would only kick Person1
The error log occured with Person2, they never crashed or were kicked, just couldnt mine the spawner
Person3 had no problems mining spawners
Expected Behavior
EnderIO Broken Spawner drops as normal
How to Test
Unable to reproduce reliably outside the server
Local Environment
Any Additional Information?
No response
I regret to say that we no longer officially support Minecraft 1.20.1 - as such we will not be officially fixing this issue.
If any community member wishes to submit a pull request to address this issue, feel free to open a PR and we will review and merge it.
I will close outstanding 1.20.1 issues in a little while, to keep the issue list clear.
Thanks again for your report.