alRex-U / ParCool

A Minecraft Forge Mod for action of Cool Parkour
GNU General Public License v3.0
41 stars 30 forks source link

Mod stops working on a Mohist server #172

Open BeginingToCode opened 1 year ago

BeginingToCode commented 1 year ago

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)

alRex-U commented 1 year ago

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. If I made explicit permission synchronization command, it could be helpful?

dangehub commented 1 year ago

I also encountered the same problem, it is worth mentioning that I am also using a mohist server, maybe related to mohist?

alRex-U commented 10 months ago

For moment, I fixed this. I need tests

alRex-U commented 10 months ago

Please let me if the phenomenon reproduce again

alRex-U commented 10 months ago

sorry it was not fixed actually. i have to research more about this