[Bug]: Error preventing players from leaving planet on server
Tempest-5ky opened this issue · 12 comments
Bug Description
Players on the server are unable to launch into space- the following error pops up on the client when they try: https://mclo.gs/8UfruTM
They get stuck with the spaceship on the top of the left loading bar and cannot ascend or descend further.
No errors are present on the server console and launching into space works perfectly fine in singleplayer with the same modpack. This is absolutely baffling me, and I've been unable to reproduce it in singleplayer at all.
How to Reproduce?
No response
Expected Behavior
Players should be able to launch and get to space without issue.
Version
1.15.18
Mod Loader Version
1.20.1 - 0.15.7
Mod Loader
Fabric
Logs or additional context
https://mclo.gs/8UfruTM <- Error (clientside)
https://mclo.gs/1eYS9HJ <- Client latest.log
https://mclo.gs/hvxP2Z3 <- Server latest.log
The modpack is pretty large, but because I've been unable to reproduce it in singleplayer I'm not able to do a binary search to try and find a culprit.
Code of Conduct
- I have searched the issue tracker and confirmed that the issue has not been reported
- I have checked the FAQ (if one is present) and my issue is not listed
- I have verified that I am using the latest version of the mod
- I have verified that I have installed all the required dependencies for the mod
- I have verified that I do not have Optifine installed. We will close issues if we detect Optifine is in your pack. We cannot fix Optifine issues. Please do not report issues with Optifine present.
Weird, can you try deleting the <world>/data/adastra_launching_dimensions.dat file on the server? Seems to not be sending the launching data correctly.
The launchingdimensions.dat is completely empty except for the dataversion if I check with nbtviewer, if that's significant?
As far as I can tell you need OP to view the planets menu on a server for some reason
oh ffs I know EXACTLY what this might be if that's the case- you're genuinely a lifesaver, thank you so so so much, I never would have caught that. I'll close this once I get a chance to test it if that's the case
Sorry, I've been quite busy recently and haven't got a chance to look into this. But if that's the issue, please don't close this as there seems to be a deeper issue with how this whole system works, which I want to investigate further.
Got it, I'll leave it open! I'm pretty sure it might have something to do with how your permissions system interfaces with luckperms, but I'll have to check that to be entirely sure so I'll get back to you later today on that. In theory, if it was set up on your end so players would have permission by default to see that screen, this shouldn't have been an issue, because I left that completely untouched- so evidently something went wrong somewhere when it comes to default perms for Ad Astra's content. Maybe.
Sorry for the delay! Just got a chance to check on this now.
So, luckperms doesn't appear to interface with Ad Astra's permissions systems at all, so I have no way of manually giving players the permission to use the planet panel, and due to having a custom permissions system for admins, mods, etc, the functionality for 'op' is disabled on the server. It's... very bizarre that this would cause issues, given that the planet selection panel shouldn't be an OP-only thing in the first place, and even after re-enabling the OP functionality and setting myself as OP I was still unable to get the planet screen to pop up, so... colour me baffled once again.
Hello im having the same issue and it's very annoying, did anyone figure out how to fix this?