Skip to content
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

Local NeoForge server crash during startup with any Fabric mod [1.21.1] #1346

Closed
rafik131313 opened this issue Aug 19, 2024 · 13 comments
Closed
Assignees
Labels
1.21.x Targets Minecraft 1.21 bug Something isn't working compat A mod is found to be incompatible

Comments

@rafik131313
Copy link

Mod Name

Ping Wheel

Mod Homepage

https://modrinth.com/mod/ping-wheel/version/EptlZW3F

Minecraft version

1.21.1

Describe the bug

Any Fabric mod causes the server to crash on startup.

Steps to reproduce

  1. Download NeoForge installer from the official site. (used for example version 21.1.16)
  2. Run the downloaded NeoForge installer and choose "Install server"
  3. Choose the empty folder on the disk
  4. Run the run.bat file created during installation
  5. Close the terminal, and change the EULA to true
  6. Run the run.bat file again to start the server
  7. Stop the server
  8. Put in the mods folder jar files:
    connector-2.0.0-beta.2+1.21.1-full
    ConnectorExtras-1.12.1+1.21.1
    forgified-fabric-api-0.102.0+2.0.12+1.21.1
    Any Fabric mod compatible with 1.21.1 version, for example Ping Wheel/Terrestria
  9. Run server again
  10. Expect crash with information of corrupted neoforge installation.

Logs

https://gist.github.com/rafik131313/15b94f7098e94883df8c16bc328db6df and https://gist.github.com/rafik131313/4deaf3971c9459d71e978536d0854954

Additional context

I would like to migrate my Fabric server with mods (just a few such as PingWheel) to NeoForge + Sinytra (1.21.1). The first thing I did was installing all the mods on a local client to check if they were compatible. The operation was successful. Next, I decided to install the NeoForge server locally to generate the necessary files, which would later be uploaded to the hosting service. I used the exact same versions of the mods and NeoForge. One of them was a Fabric mod (PingWheel), while the rest were NeoForge mods. Unfortunately, I noticed that adding the Fabric mod caused the server to crash on startup. To verify if the problem was with PingWheel, I replaced it with a mod that is officially supported, namely Terrestria, but with the same result. Changing the server version along with the add-ons to NeoForge 1.20.1 did not bring any changes.

@rafik131313 rafik131313 added the compat A mod is found to be incompatible label Aug 19, 2024
@KewlSage

This comment was marked as off-topic.

@rafik131313

This comment was marked as off-topic.

@sisby-folk
Copy link

sisby-folk commented Aug 24, 2024

can confirm FFAPI w/ connector is broken on dedicated servers. here's my sanity setup:

image

Totem Anywhere is the smallest mod i have or know, and doesn't require fapi to run.

https://mclo.gs/UHZVj3A for the above

I also tried with just totem + connector which crashed, but then discarded this when i realised connector alone also just crashes - i figure connector requiring ffapi outright is just the norm now.

From what i can tell, the underlying cause of this issue can create all kinds of red herring crash logs - I've seen "connector is not installed" unhelpful soft fails in singleplayer instances as well at times (specifically, when i have a fabric mod with its own missing dependency), so I guess they might be related?

@Bassote
Copy link

Bassote commented Aug 27, 2024

I'm also having the same problem without any mods, just Connector and FFAPI, tried with NoEmotecraft and just with base Connector and FFAPI and both errors were the same, "Your NeoForge installation is corrupted", tried with different versions of NeoForge, reinstalling, and different folders and it didn't work.

@parmerinha99
Copy link

It happened to me too. With any Fabric mod using the Connector

@Deveune250
Copy link

Deveune250 commented Sep 7, 2024

I am not alone, which is reassuring. I have exactly the same problem as you

@TDEnderP
Copy link

TDEnderP commented Sep 7, 2024

Ok glad im not crazy and this is a general issue. Hope this can be resolved soon.

@rafik131313
Copy link
Author

FYI guys, the issue is known and "will be fix in the future" :)

obraz_2024-09-13_114247248

@github-project-automation github-project-automation bot moved this from 🆕 New to ✅ Done in Connector Triage Sep 13, 2024
@rafik131313 rafik131313 reopened this Sep 13, 2024
@sisby-folk
Copy link

@Su5eD mentioning you again because this will be miscategorized in triage (see above)

@coco875
Copy link

coco875 commented Sep 13, 2024

I mention I am not a dev and the issue need to be open to be reference for other people who have the same issue

@Su5eD Su5eD self-assigned this Sep 13, 2024
@Su5eD Su5eD moved this from ✅ Done to 🔖 Confirmed in Connector Triage Sep 13, 2024
@Su5eD Su5eD added bug Something isn't working 1.21.x Targets Minecraft 1.21 labels Sep 13, 2024
@deadca763

This comment was marked as off-topic.

@sakurawald
Copy link

Confirmed, sinytra-connector can't work in dedicated-server.

@Su5eD
Copy link
Member

Su5eD commented Sep 29, 2024

Fixed by #1419

@Su5eD Su5eD closed this as completed Sep 29, 2024
@github-project-automation github-project-automation bot moved this from 🔖 Confirmed to ✅ Done in Connector Triage Sep 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.21.x Targets Minecraft 1.21 bug Something isn't working compat A mod is found to be incompatible
Projects
Status: ✅ Done
Development

No branches or pull requests