How does Leaf Mod Analyzer detect Glow_Mixin_Override?

Leaf Mod Analyzer performs static analysis of JVM bytecode and decompiled AST structures matching The detector inspects method-level annotations, identifying Mixin injection points (`@Inject`, `@ModifyReturnValue`, or `@ModifyExpressionValue`) whose target method matches entity glow predicates: - Intermediary methods: `method_5851` (`isGlowing`) and `method_27022` (`hasOutline`). - Named vanilla or Forge methods: `isGlowing`, `shouldGlow`, `isCurrentlyGlowing`, `hasOutline`, or `func_184195_f`. The detector flags bytecode interventions that directly alter the game's glowing state. Note that this rule matches any injection into `isGlowing`, whether used aggressively for full-player wallhacks (ESP) or selectively in utility mods (such as friendly player highlight tools). If a mod implements entity silhouettes via custom OpenGL/VBO shaders without modifying `isGlowing`, this signature will not trigger. in an isolated environment without executing untrusted JAR files.

Can server anticheats block Entity Glow / Wallhack ESP Mixin?

Server-side anticheats monitor movement and packet anomalies, while static analysis with Leaf Mod Analyzer identifies hostile and unfair code before mods are loaded.

Entity Glow / Wallhack ESP Mixin

🎮 Minecraft Gameplay Impact

In Minecraft, the Glowing status effect renders a bright colored outline around entities that remains visible through opaque terrain and solid walls. In vanilla gameplay, this effect is granted only through specific game events, such as spectral arrows or status potions applied by the server.

Glow_Mixin_Override detects modifications that hook Entity.isGlowing() (method_5851) via Mixin. In the FriendHighlight mod (net.maksaidev.friendhighlight.mixin.EntityGlowMixin), @Inject hooks into isGlowing at HEAD with cancellable = true. When the entity is a player (class_742), it queries FriendManager.isFriend(name). If confirmed, it calls cir.setReturnValue(true).

By returning true, the game engine renders the glowing outline through solid blocks, providing clear wallhack visibility. While the sample demonstrates a targeted utility use case (highlighting teammates), the identical bytecode pattern is employed by malicious ESP and wallhack cheats to reveal all opponents in competitive environments.

🔍 Functions & APIs Analyzed

Entity.isGlowing / method_5851

Vanilla predicate determining whether an entity should render an outline glow visible through solid blocks.

@Inject / @ModifyReturnValue (Mixin)

Mixin annotations injecting logic into Entity.isGlowing to force a true return value.

⚙️ Decompiled Representation (Vineflower View)

@Inject(method = "isGlowing", at = @At("HEAD"), cancellable = true)
private void friendhighlight$forceGlowForFriends(CallbackInfoReturnable<Boolean> cir) {
   class_1297 self = (class_1297)this;
   if (self instanceof class_742 clientPlayer) {
      String name = clientPlayer.method_7334().getName();
      if (FriendManager.isFriend(name)) {
         cir.setReturnValue(true);
      }
   }
}

🛡️ Bytecode Signature & Static Detection

The detector inspects method-level annotations, identifying Mixin injection points (@Inject, @ModifyReturnValue, or @ModifyExpressionValue) whose target method matches entity glow predicates:

Intermediary methods: method_5851 (isGlowing) and method_27022 (hasOutline).
Named vanilla or Forge methods: isGlowing, shouldGlow, isCurrentlyGlowing, hasOutline, or func_184195_f.

The detector flags bytecode interventions that directly alter the game's glowing state. Note that this rule matches any injection into isGlowing, whether used aggressively for full-player wallhacks (ESP) or selectively in utility mods (such as friendly player highlight tools). If a mod implements entity silhouettes via custom OpenGL/VBO shaders without modifying isGlowing, this signature will not trigger.