-
Notifications
You must be signed in to change notification settings - Fork 28
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
Mod stops working on a Mohist server #172
Comments
Was this mod working? As you said similar problem is sometimes reported but I couldn't reproduce it. I think this is because something override or cancel ParCool's sending permission. |
I also encountered the same problem, it is worth mentioning that I am also using a mohist server, maybe related to mohist? |
For moment, I fixed this. I need tests |
Please let me if the phenomenon reproduce again |
sorry it was not fixed actually. i have to research more about this |
Summary
So, basically I have a server that runs on Mohist idk if that's a problem? Anyway, the mod was working fine until me and a friend couldn't use the actions from the mod anymore, only 1 of us could (we're 3 players). When we press alt+p all the actions have X's on them both on server and client side. I saw a report on github saying entering the nether worked for them and I did that too, it worked. But when I leave the server it stops working again and entering the nether everytime I want the mod to work is quite annoying, specially when we have a rule that doesn't allow us to go to the nether.
I've seen this issue both in the comment section of the curseforge site and one here that was labeled as "fixed" in the 1.18 version.
Running Environment
Detail
As I said above, the mod seems to work when entering the nether and coming back to the overworld but the moment I leave the server, it's back to square one.
Additional Data
Such as Screenshots or Crash Reports
(I am happy and fix the bug more easily if you send me these)
https://github.com/alRex-U/ParCool/assets/86009550/d6222810-78df-42b8-91b1-3c93113c7915 (video of the issue)
The text was updated successfully, but these errors were encountered: