Curse of Ashes not applying to block broken (Neoforge 1.21.1) #35
Labels
No labels
Compat
Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Port
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Security
Status
Abandoned
Status
Blocked
Status
Need More Info
Status
Needs Triage
Testing
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Modding/enchiridion#35
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?
Curse of Ashes does not apply when breaking a block, only when using a tool/weapon with the curse to kill a mob. Unsure if this applies to fabric as well. I understand that you are moving forward past 1.21.1 but it'd be nice if this was fixed beforehand!
Sure thing. Should be simple enough to fix.
I did say on the Discord that I would actively fix bugs that involve the mod itself for a bit.
Won't fix? Is there something preventing this from being fixed, or do you not intend to fix bugs that involve the mod anymore on this version?
It's not like this issue doesn't exist or isn't reproducible so I'm very curious on the reasoning behind this.
@ManaStar wrote in #35 (comment):
I am burnt out on 1.21.1's codebase. I have zero interest in having to forever maintain a super old version of the codebase alongside the newer one I'm more interested in that has been cleaned up a ton.
At the end of the day, this is a hobby. I don't need to forever commit to what are ultimately chores.
I'd highly recommend you just go play with another more stable enchanting mod, and come back to Enchiridion later in its lifespan.
Frankly, 0.1.0/0.2.0 is terribly made, terribly designed, and I don't really have interest in updating for a 2 year old version of Minecraft that I had moved on from a year ago now.
This is a perfectly understandable approach, I think this is a much better way to leave off this issue thread than to have closed it without words. I hope that development on whatever version you are currently maintaining goes better than this one.