-
Notifications
You must be signed in to change notification settings - Fork 5
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
UseHoeEvent doesn't take event state into account #3
Comments
I'll try to make a PR, so you don't need to do the work |
Should be as simple as adding something like: if (e.getResult() != Result.DEFAULT || e.isCancelled())
return; to the top of |
@SimonMeskens Thanks for pointing out the issue. I can't do anything right now, actually, because my computer died recently, so if you create a pull request that would be great. |
Gotcha, I'll try out what squeek suggests, play around with it a little bit to make sure it works out fine. |
Small update: This issue bubbled up to the top of my todo, so I'll be testing some stuff this weekend hopefully |
@squeek502 EB's hoe event is firing first, at which point I can't tell if it was dirt or grass. Ideas? |
That is determined by the priority of the event subscription. Other mods can use This change is just the first step towards compatibility with HO. After this, HO will need to add special compatibility for EB grass/dirt. See my comment in the HO issue:
|
just a note: EB has custom dirt, grass AND farmland |
I lowered event priority on the default hoe-ing behavior. As a vanilla mimic, it should have as low of a priority as possible anyway, any event should surpass it. Seemed a bit cleaner than requiring elevation of Hunger Overhaul priority. The commit is in the PR. |
progwml6/HungerOverhaul#107
The text was updated successfully, but these errors were encountered: