Closed DrMedic29 closed 1 year ago
Hi, could you try to copy those folders from your client into the server: config
, mods
, kubejs
?
This would ensure you have the same exact files. Then let me know if you still cannot join your local server
I did that and I am having the same problem still.
I deleted the world on the server and it is still giving me the error after reloading the server with a new world.
Can you add the server's log / client logs? If you load it & test locally you don't need to remove the ip addresses in the logs, but otherwise if it's over the internet (like an online host) please do so before posting it here
Server: latest.log Client: latest.log
Wow, that's all there is for the client log? It should be much longer than that... Are you using the FTB App to start the game?
The client log is in the logs
folder, called latest.log
. When you launch the game it should quickly fill up and become hundreds of lines long
I download it from ftb and them create a new instance in the regular mc launch and launch it from there. And ya that is the latest.log I was confused as well
The other person playing with me gets this issue as well. So I'm 99% sure it is server based
Try clicking the settings in the MC launcher (bottom left) and clicking the option similar to "open game output when game starts". That way you can have (all?) of the client log there and hopefully towards the end when it disconnects you from the server there will be more information about the error
That client log shows [net.minecraftforge.network.HandshakeHandler/FMLHANDSHAKE]: Starting new vanilla impl connection.
for some reason. How are you starting the server, and how does your start script look like?
@echo off IF EXIST eula.txt ( goto CHECKEULA ) ELSE ( goto ASKEULA ) IF %errlevel% EQU 1 goto END :CHECKEULA
nul find "eula=false" eula.txt && ( goto ASKEULA ) || ( goto END ) :ASKEULA echo "Do you agree to the Mojang EULA available at https://account.mojang.com/documents/minecraft_eula ?" set /p EULA=[y/n] IF /I "%EULA%" NEQ "y" GOTO END echo eula=true>eula.txt :END start "FTB Server" "jre\jdk-17.0.2+8-jre\bin\java.exe" -javaagent:log4jfix/Log4jPatcher-1.0.0.jar -XX:+UseG1GC -XX:+UnlockExperimentalVMOptions -Xmx6144M -Xms4096M @user_jvm_args.txt @libraries/net/minecraftforge/forge/1.18.2-40.1.84/win_args.txt nogui The one that is installed atomaticlly with the server files for the modpack
That is the correct start script, give me a few minutes to test this locally. Also, it's that same chickens error that you have on all tries?
Yes and the other person trying to connect to the server as well
Trying to upload all my server files in a compressed folder to dropbox and get you a link soon incase you can't recreate it
I get the same error on 1.1.0, so my guess is there's something going on with the chickens mod and the recent Minecraft outage / or just the recent outage does this https://twitter.com/MojangStatus/status/1589822938995621888
I'd suggest waiting in that case... Thanks for your patience in advance
Np ty for helping me I had no clue about the outage I thought it might be something getting corrupted
I thought the same thing at first, no worries!
Is this also an issue on 1.1.1?
Is this also an issue on 1.1.1?
Yes, I can confirm it's also doing it in 1.1.1. We just updated the server, and I updated my client, and still getting the same exact issue, still not syncing chickens at 1.0.25, showing the same on both sides. I even uninstalled the modpack and installed it fresh entirely to no avail.
Okay i just tested myself, so i only have this issue if i use other launchers then FTB APP What launcher you using?
I get this on 1.1.1 using the vanilla launcher with correct version of forge installed and working directory set to the Instance directory from the FTB App.
Please use the FTB App to launch
It does seem to work fine when launched from the FTB App. What communications does the FTB app permit that the vanilla launcher doesn't? Odd one.
Well we are not sure, we know that MC launcher had a update and so did CurseForge APP and it seems to have broken things, but some how our app is working fine, i guess due to that we launch the game in a different way
I changed the FTB App to launch using the same version of the JRE that I use in the vanilla launcher configuration and that setup still works as well. 😕
I am having this registry sync issue with AE2. Picture attached below:
EDIT: I am launching with the FTB App on Linux. Client Java version 17.0.4 Server Java version 17.0.1
FWIW the vanilla launcher update appears to have been rolled back. SB3 is working again launching with forge+FTB App working directory method.
Edit: MCL-22685 seems to be the root cause of all this mess. Glad FTB was able to escape the blast radius of it.
Me and my friend are having the exact same issue but with KubeJs. we are using version 1.2.1 and even tried to replace the mod with one from curseforge. we are using FTB app
Modpack
StoneBlock 3
Modpack version
1.0.0 and 1.1.0
Log Files
No response
Describe the bug
Steps to reproduce
Unknown
Expected behaviour
Connect to server normal
Screenshots
Additional information
I have been playing on 1.0.0 stoneblock 3 with no problems since the launch of stoneblock 3, today I got this error. I tried updating to 1.1.0 and still have this problem.