Learn · modules
What Is a Module Indicator in Minecraft?
A module indicator is a simple HUD overlay that lists which modules are currently active in your Minecraft client, updating in real-time.
What is a Module Indicator?
A module indicator is the small text list, usually parked in a corner of the screen, that tells you which modules are currently running in a Minecraft utility client. Turn a module on and its name shows up. Turn it off and the name is gone. That's the entire feature: a live readout of your own client state, nothing more. It plays the same role as an Array List, and in clients that ship both, the two are typically written as separate, independently coded features rather than one list with two visual styles.
How it works
Every frame, the client checks which modules are flagged as enabled and draws their names as a short list, usually anchored to a corner of the screen. Enable a module and a line gets added. Disable it and the line disappears immediately. There's nothing more to the mechanic than that.
Because the list only reads local client state and paints text over the game view, it never talks to the server. No packets go out, no gameplay logic gets touched, just a draw call layered on top of whatever you're already doing. It belongs in the same bucket as a coordinates HUD or an FPS counter: fully local, fully cosmetic, and invisible to anyone who isn't looking at your own screen.
Module indicator vs Array List
The overlap here isn't accidental. Both features exist to answer the same question: what's on right now? Where they diverge is scope and depth, not purpose.
| Aspect | Module Indicator | Array List |
|---|---|---|
| Purpose | Lists currently active modules | Same: lists currently active modules |
| Feature depth | Minimal, name-only list | Often fuller with sorting or styling |
| Build approach | Its own plain module, coded separately | Often the more developed "primary" version |
| Server interaction | None | None |
| Anticheat risk | None | None |
A client can ship one, the other, or both stacked in a corner. Which one you use, or whether you get both options, comes down to how the dev team structured their HUD.
Why a module indicator matters
A simple list of what's running is table stakes for a utility client. You need to know whether you left a combat module on when you meant to turn it off, or whether your movement settings are still active after closing the menu. A module indicator gives you that quick glance without diving into a settings screen.
The practical use case is avoiding mistakes. You toggle something intending to turn it off and forget. The indicator catches that at a glance instead of you finding out mid-fight when the module does something you didn't expect.
FAQ
No. It only draws text on your own screen and never touches movement, combat, or any other game logic.
No. It never sends anything to the server, so there's nothing for an anticheat to observe or flag.
They do the same job, listing active modules, but a module indicator is typically the plainer, separately coded version rather than sharing code with an Array List.
No. It renders only on your own client and is never sent to the server or shown to anyone else.