From 372a3b28bd3bbaebf5934b4582dbb2feba70a93e Mon Sep 17 00:00:00 2001
From: Shane Freeder <theboyetronic@gmail.com>
Date: Thu, 8 Jan 2026 17:13:08 +0000
Subject: [PATCH] Conformity

---
 .../proxy/protocol/netty/MinecraftVarintFrameDecoder.java     | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/proxy/src/main/java/com/velocitypowered/proxy/protocol/netty/MinecraftVarintFrameDecoder.java b/proxy/src/main/java/com/velocitypowered/proxy/protocol/netty/MinecraftVarintFrameDecoder.java
index 31ddda0e7..35016c312 100644
--- a/proxy/src/main/java/com/velocitypowered/proxy/protocol/netty/MinecraftVarintFrameDecoder.java
+++ b/proxy/src/main/java/com/velocitypowered/proxy/protocol/netty/MinecraftVarintFrameDecoder.java
@@ -76,13 +76,13 @@ public class MinecraftVarintFrameDecoder extends ByteToMessageDecoder {
     }
 
     // skip any runs of 0x00 we might find
-    int wLength = in.readableBytes();
+    int wlen = in.readableBytes();
     int packetStart = in.forEachByte(FIND_NON_NUL);
     if (packetStart == -1) {
       in.clear();
       // Apply a more strict check in serverbound direction, we really shouldn't be seeing this many 0x00s
       // even from the server, the only reason we even allow these is due to bugged servers
-      if (direction == ProtocolUtils.Direction.SERVERBOUND && wLength > 16) {
+      if (direction == ProtocolUtils.Direction.SERVERBOUND && wlen > 16) {
         throw INVALID_PREAMBLE;
       }
       return;