-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
E-scanner bug on 1.14 server #625
Comments
I am using only the minecraft connection so when you joined the server the connection worked and all needed ports are open. "Data loading" means the packet with research data never gets to the client, hmmm... |
What kind of information can I provide to help you? |
Please give me your forge version & installed mods. |
forge-1.14.4-28.2.0 and the only mod installed is futurepack |
Seems like I broke the packet handling somewhere... |
|
patched in the version of 28.0.17? |
no In 28.0.26 |
pushed to curseforge |
Scanning is fine but there is no GUI displayed for research progress and story. Only the text "data is loading" is showed but never really loads. Could this be the problem of the firewall on the server like some port should be opened,etc?
Below are some error infos on the server (might be irrelevant):
[23:16:28] [Netty Epoll Server IO #1/ERROR] [minecraft/ArgumentTypes]: Could not serialize futurepack.common.commands.DimensionArgument@2ac1922 (class futurepack.common.commands.DimensionArgument) - will not be sent to client! [23:16:28] [Netty Epoll Server IO #1/ERROR] [minecraft/ArgumentTypes]: Could not serialize net.minecraftforge.server.command.ModIdArgument@52bf986f (class net.minecraftforge.server.command.ModIdArgument) - will not be sent to client! [23:16:28] [Netty Epoll Server IO #1/ERROR] [minecraft/ArgumentTypes]: Could not serialize net.minecraftforge.server.command.EnumArgument@550cbac6 (class net.minecraftforge.server.command.EnumArgument) - will not be sent to client! [23:16:28] [Server thread/ERROR] [ne.mi.fm.ne.si.IndexedMessageCodec/SIMPLENET]: Received empty payload on channel fml:handshake
The text was updated successfully, but these errors were encountered: