-
Notifications
You must be signed in to change notification settings - Fork 1
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
Continous flow of warning causing timeout on log in #85
Comments
Same issue here. Running a server with interact me, eureka, Valkyren skyes: clockwork and create on 1.20.1 forge 47.2.32 In my case i was able to log in, but the server would run only for 1-2 hours until it crashed due to insufficient RAM |
Same issue |
|
I deleted all ships and now its gone, for now |
I'm having this problem too, even on a world with no ships! |
Same issue here. MC 1.20.1, Fabric 0.15.11, Create Interactive 1.0.3 beta 2, VS 2.3.0 beta 5. There are no ships in the world. I even deleted all moving contraptions from the world. Every time I restart the server a new "ship" is added to the log with IDs 4 apart: e.g. ID 24, 28, 32, etc. |
Commenting as I have the same problem! As Create, Create: Clockwork and Create: Interactive are all for 1.20.1, we can't update to newer version of VS2 if it is only for later version of the game. |
Same issue here, kind of surprised that this hasn't been adressed yet. The mod spams massless ships until restart. I found out that killing all ship entitites fixes the problem for a short while. The problem appears on a completely fresh world. This problem need more attention (or at least any attention) Environment: Fabric 0.15.11, MC 1.20.1 |
same in 1.20.1 forge |
To fix it do /vk delete @v and it should fix the problem. hop this helps |
sure it is a valid solution but has a few major flaws:
|
Version : 1.0.2 beta.2 1.20.1 Forge 47.2.0
I have a server with almost 200 mods. I created 2 or 3 farms using interact me block.
On restart, i have this warning that loop and the login is now impossible:
[12:51:08] [Server thread/WARN] [or.va.co.im.ne.NetworkChannel/]: Ship with ID 78 has a mass of 0.0, not creating a ShipObject [12:51:08] [Server thread/WARN] [or.va.co.im.ne.NetworkChannel/]: Ship with ID 79 has a mass of 0.0, not creating a ShipObject [12:51:08] [Server thread/WARN] [or.va.co.im.ne.NetworkChannel/]: Ship with ID 80 has a mass of 0.0, not creating a ShipObject [12:51:08] [Server thread/WARN] [or.va.co.im.ne.NetworkChannel/]: Ship with ID 81 has a mass of 0.0, not creating a ShipObject
The text was updated successfully, but these errors were encountered: