[1.19.2] Internal Exception when Joining Vanilla Server
MetalBox47 opened this issue ยท 11 comments
Minecraft version
1.19.2
Farmer's Delight version
1.2.3
Forge version
43.2.23
Description
Upon joining a vanilla server, an internal exception occurs that reads:
Vanilla server is 1.19.2 with no modifications.
Steps to reproduce
- Launch Minecraft
- Go to Multiplayer Screen
- Click join server button on vanilla server
- Result
Mod list
Farmer's Delight v1.2.3
Logs
Minimal instance
- I have tested this on a minimal instance
Performance and shader mods
- I am using performance or shader mods
Farmer's Delight is a Forge mod, and therefore not compatible with vanilla servers. You can't join one with Forge mods installed.
Please make a separate vanilla client to join this server instead.
Assuming there is a specific issue with FD, the logs provided on the client will not show what it is.
If you can/have access, please provide the server logs in two scenarios:
- Connecting to the server with FD added onto the client;
- Connecting to the server without FD installed.
Also, just to iterate: Forge mods loading successfully in a vanilla server is usually an exception, as there's no explicit compatibility with that implemented. It should be assumed they won't work.
I understand. However, Forge clients with various mods installed can join vanilla servers without crashing the server or the client, as shown in the attached video.
2023-09-15.12-43-43.mp4
Normally this is impractical, but I have a server that uses a vanilla lobby so that players can connect to multiple servers, including a modded one. Farmer's Delight is the only mod that crashes whenever I do this.
I am more than willing to provide you with more information, and thank you for your time and patience! Its really appreciated.
farmer's delight isn't (only) a client-side mod, which means that it screws with servers upon joining them. other mods, like JEI, are exclusively client-side, so they can join vanilla servers without any issues. this is unavoidable behaviour coming from the nature of any mod that adds content.
Yes, the issue primarily stems from FD being a content mod. It must be present in both the client and the server, or else the client/server cannot understand each other, since items would be missing from registries.
Correct, I have no issues joining this server with mods such as mouse teaks and JEI. However, I also have no issue when joining with mods installed like refined storage, sophisticated backpacks, tetra, and more. This leads me to believe it is a problem on Farmer's Delight's end and not that I am attempting to join a vanilla server with mods installed.
Sorry if I am being unclear or misunderstanding!
strange behaviour, but this isn't a bug that needs to be fixed regardless; if you need to join a vanilla server with a forge profile, simply unload farmer's delight
Im not trying to be argumentative, but this is problematic whenever server administrators want to have a server network where players have to connect to a lobby server and then join from that server into the modded server with Farmer's Delight installed. This issue will prevent the clients from ever getting into the lobby so that they may join the modded server.
Logs are attached, and understood!
withfdserver.log
withoutfdserver.log
I also saved the client logs and client screenshot from this run if you would like those. It did give me a different error this time, however:
I've been informed that Netty exceptions are swallowed by Forge, thus it shows nothing on logs normally.
@MetalBox47, please add the following mod to your instance, and generate new logs after trying to connect again:
https://www.curseforge.com/minecraft/mc-mods/spit-it-out
It should reveal the exception, or at least give some detail as to why only FD is causing this issue.
I figured out what the issue is, but sadly, it's not fixable on my end; it's an issue in how Minecraft's enums are interpreted.
Please see this comment on another issue for more details: #805 (comment)