-
-
Notifications
You must be signed in to change notification settings - Fork 201
Hang on connecting to server using vanilla client #510
Comments
Vanilla clients connecting might be possible in 1.8, this is something that we want to do but requires re-writing the entire network protocol. |
Lex, I have reason to believe a lot of people want vanilla clients to be able to connect to modded servers in 1.7. Join #nextstep on espernet IRC, you'll see what I mean. Hasn't @cpw come up with a working draft of it, by the way? |
I managed to do vanilla compat for 1.7 in a seperate mod. The only problem is it doesn't ask mods what they think about it. It should however be fine. If there is any block the client doesn't know they are just invisible |
1.7 may be in the future, we will have to discuss this. However as it sits everything is WAY to early to try to discuss things as everything is up in the air. |
@jk-5 Does that happen to be open source? |
When I connect to a FML server using a vanilla client, my client just stops at the "Logging in" screen. The cancel button works, though. This happens regardless of whether I'm running pure FML or am running Forge.
On the server, this is repeatedly displayed:
[10:56:26] [Netty IO #3/INFO] [FML]: Unexpected packet during modded negotiation - assuming vanilla or keepalives : net.minecraft.network.play.client.C00PacketKeepAlive
If I abort the connection, the server displays a "Disconnected" message, and states that I have left the game.
This shouldn't be happening. If memory serves, in 1.6 I would have been kicked from the server with a "not modded" error message, or something along the lines of that.
Also, with recent events, shouldn't work be done on allowing vanilla clients to connect without bungeecord?
The text was updated successfully, but these errors were encountered: