- A watermark module draws a client's name or logo over the game screen for branding.
- It's a local draw call after the frame is built: no packets, no game state.
- Players use it to brand clips and confirm which client build they're running.
- Zero gameplay effect means zero anticheat risk, server side or client side.
A watermark, in a Minecraft utility client, is a small piece of branding, usually a name or logo, drawn onto a fixed spot on your screen while you play. It works the same way a watermark on a photo or a video does: it stamps the source onto whatever gets recorded, without touching the actual content underneath. As a module, watermark is a HUD element and nothing more. It doesn't move your character, doesn't read the world state, and doesn't send anything extra to the server. It exists so a clip circulating online, or a screenshot dropped in a Discord, is unmistakably tied to whatever client produced it.
How it works
Watermark sits in the same family as any other HUD overlay: a coordinates readout, a potion timer, a keystroke display. The client renders a piece of text or a small logo image on top of the finished game frame, usually anchored to a corner (bottom right is the common default), after everything else on screen has already been drawn.
Because it's a draw call and nothing else, it has no read access to anything that matters for gameplay: no player position, no block data, no entity list. It just paints pixels in the same place every frame. Most implementations expose a handful of controls, position or offset, size, and an on/off toggle, none of which touch a single outbound packet. That last detail is what makes the next section short.
Is it safe to use
Watermark is about as low-risk as a module gets. Anticheat, whether it's server-side detection on a competitive server or client-side integrity checks, works by inspecting what the client sends or how its behavior lines up with the game state: movement deltas, attack timing, packet sequencing. Watermark touches none of that. It's a local drawing operation with no network footprint and no interaction with game logic, so there's nothing for a detection system to compare against.
That puts it in the same bucket as other display-only modules, HUD customization, an FPS counter, a keystroke display, rather than anything resembling an aimbot or a reach extender. If a server ever banned someone over a logo in the corner of their screen, that would be a policy call, not a detection one.
Where this fits at Opal
Opal doesn't ship a module under this name. If branding your footage is the goal, that's a recording-software job, not a client one. What Opal's Visual category does cover is the broader HUD and overlay space: on-screen elements that report on your game, not on the client that made them.
FAQ
No. It only draws text or a logo on screen and has zero connection to movement, combat, or anything the server processes.
No. It never sends anything to the server, so there's nothing for a server-side anticheat to observe about a purely local overlay.
Mostly branding and identification: it makes clips and screenshots recognizable, and lets you confirm at a glance which client, or which build, you're running.
Usually, yes. Most implementations let you reposition it, resize it, or disable it outright, though the exact controls depend on the client.
