009testReporthttps://hub.spigotmc.org/jenkins/job/BungeeCord/net.md-5$bungeecord-proxy/1036/mavenArtifacts/false#1036183366352BungeeCord » BungeeCord-Proxy #10362015-01-12_03-23-49falsefalse1036-1SUCCESS1421051029000https://hub.spigotmc.org/jenkins/job/BungeeCord/net.md-5$bungeecord-proxy/1036/proxy/src/main/java/net/md_5/bungee/ServerConnector.javaproxy/src/main/java/net/md_5/bungee/forge/ForgeClientHandler.javaproxy/src/main/java/net/md_5/bungee/UserConnection.javaproxy/src/main/java/net/md_5/bungee/connection/InitialHandler.javaproxy/src/main/java/net/md_5/bungee/forge/ForgeConstants.java4809f1f80ace9ae87b91453c8887c70f5e098bd01421011387000https://hub.spigotmc.org/jenkins/user/md_5md_5git@md-5.netUpdate IP forwarding to ignore FML and other null character delimited tokens (for now) For Forge 1.8, a new \0FML\0 token is included in the handshake packet host field. Whilst from a Forge <-> Bungee standpoint, this is good in the long run (we can detect Forge/FML clients right from the off, allowing us to expose a reliable API for detecting modded 1.8+ clients), it plays havoc with IP forwarding on Spigot servers, as they expect a very specific format. Until we can look at improving this situation (probably by creating an updated IP forwarding protocol on the server side), this removes the FML marker from the handshake whenever IP forwarding is on. If you have a FML 1.8 network, IP forwarding MUST be off. With thanks to @geNAZt for finding the issue. 2015-01-12T08:23:07+11004809f1f80ace9ae87b91453c8887c70f5e098bd0Update IP forwarding to ignore FML and other null character delimitededitproxy/src/main/java/net/md_5/bungee/connection/InitialHandler.javaeditproxy/src/main/java/net/md_5/bungee/forge/ForgeConstants.javaeditproxy/src/main/java/net/md_5/bungee/UserConnection.javaeditproxy/src/main/java/net/md_5/bungee/ServerConnector.javaeditproxy/src/main/java/net/md_5/bungee/forge/ForgeClientHandler.javaapi/src/main/java/net/md_5/bungee/api/connection/ProxiedPlayer.javaproxy/src/main/java/net/md_5/bungee/UserConnection.java28496e0471237448db017115c769e684ecd76abc1421011387000https://hub.spigotmc.org/jenkins/user/md_5md_5git@md-5.netAdd API for getting whether the user is a Forge user. For Minecraft+Forge 1.8 we can detect whether the user is a Forge user before we get the mod list, due to the changes to the initial (not FML|HS) handshake that are now made (which is for vanilla client support). Bungee can exploit this to detect FML clients from the off, but it still does not tell us what the mod list is. Thus, creating this API method for users who simply need to know whether the user is connected via FML is no longer a duplication of the getModList api method. 2015-01-12T08:23:07+110028496e0471237448db017115c769e684ecd76abcAdd API for getting whether the user is a Forge user.editapi/src/main/java/net/md_5/bungee/api/connection/ProxiedPlayer.javaeditproxy/src/main/java/net/md_5/bungee/UserConnection.javahttps://hub.spigotmc.org/jenkins/user/md_5md_5https://hub.spigotmc.org/jenkins/job/BungeeCord/net.md-5$bungeecord-proxy/1036/mavenArtifacts/