Cannot join servers with versions 123+ of JER
NielsPilgaard opened this issue ยท 14 comments
Joining a server that has JustEnoughResources-1.16.5-0.12.1.127 results in the player being kicked with the messaeg Internal Server Error. Reverting to JustEnoughResources-1.16.5-0.12.1.122 resolves the issue.
Last part of the server log: https://gist.github.com/NillerMedDild/5ef3d47739020d921fe363723da833e1
also had this issue. gives internal server issue. only indication was something about JER. removed it and was fine.
Can confirm this behaviour, we have the same problem. Reverting to .122 resolves the problem.
For me it only happens to OP'ed players (127). Brand new server build with only JEI and JER (JEI alone, no issue). Any survival player can play, log out and in, but as soon as you OP them, there in no broadcasted message, and on the server console I noticed it says:
"An unexpected error occurred trying to execute that command" instead of saying player has been op'ed.
They still retain OP though, but next time they try to login, and from then on, Internal Server Error. I have to delete my ops.json file on the server, restart it, then they can get back on (with no op).
The issue was caused by the following commits in any build after 122 that affects the api
when moving the api into the new folder and names, you broke quite a few mods that access this api as they do not acknowledge the directory changes. the one in major question is FTB Library and the FTB Ranks mod, which uses the ranking system to lock certain je-suite features from certain players.
here's the log file in question: https://pastebin.com/EahrJrBQ
to all participating in this thread, you can see that the commit is unfinished, that the implementation "will be done later"
because of this I fear @way2muchnoise will be ignoring this issue until they have finished implementation. stay downgraded to 122 (the builds get posted to curse automatically anyway) until further notice.
The bug seems to be mostly surrounding an issue where DEDICATED SERVER is invalid for some methods used.
this commit here is at fault in several ways
to all participating in this thread, you can see that the commit is unfinished, that the implementation "will be done later"
because of this I fear @way2muchnoise will be ignoring this issue until they have finished implementation. stay downgraded to 122 (the builds get posted to curse automatically anyway) until further notice.
