Will an AI gaming companion get you banned?

Type "AI gaming companion" into a search bar and the autocomplete finishes the thought for you: will it get me banned. That's not paranoia — it's the right instinct. Your account carries years of progress, purchases, rank, and a friends list. Anything that runs next to a competitive game deserves scrutiny before it earns a place on your PC.

So this page answers the question properly instead of waving it away. First: how anti-cheat actually decides something is a cheat. Then: exactly how Peranima — a voice AI companion that runs as a Windows desktop overlay — is built, including the things it never does. And because honesty is the whole point, a dedicated section on Minecraft, where the integration works through a genuinely different mechanism and there's a real nuance about other people's servers.

How anti-cheat actually works

Modern anti-cheat — Riot's Vanguard, Easy Anti-Cheat, BattlEye — often runs at kernel level, which sounds ominous but exists for a specific job: detecting software that tampers with the game. The detection surface comes down to three behaviors:

• Reading or writing game memory. Wallhacks and aimbots work by opening the game's process memory and reading data the game never put on your screen — enemy positions behind walls, exact hitboxes. Anti-cheat watches for processes that open handles into the game and peek inside.
• Injecting code or inputs. ESP cheats inject DLLs to draw inside the game's own renderer; aimbots and triggerbots send synthetic mouse and keyboard events into the game. Code injection and input automation are the second pillar of detection.
• Behavioral analysis. Even without catching the software, statistically impossible aim, inhuman reaction times, and machine-perfect input patterns get flagged on the server side.

Notice what's not on that list: "other programs running on your PC." You already game with a dozen of those — a browser on the second monitor, music, voice chat with friends, a screen recorder. Anti-cheat isn't hunting software that exists near the game. It's hunting software that reaches into it.

That distinction — touching the game versus running beside it — is the entire question. So here's where Peranima sits.

How Peranima works (and what it never does)

Peranima is a separate Windows desktop program. It draws a small always-on-top window on your desktop — the same way a voice-chat overlay or a stream timer sits above your game — and it listens to your microphone when you hold a push-to-talk key. That's the architecture. Concretely, here is what it does not do:

• It does not read game memory. No handles into the game process, no peeking at entity positions, no "knowing" anything the game didn't show on screen.
• It does not inject inputs. It never sends a mouse movement, click, or keypress into your game. There is no aim assist, no macro, no automation pathway — that capability simply doesn't exist in the app.
• It does not hook game processes. No DLL injection, no render-pipeline hooks, no code running inside the game. Its window is drawn on the desktop, not inside the game's renderer.
• It does not watch your screen passively. It takes a screenshot only when you explicitly ask it to look at something — one capture per request, never a continuous feed.

Now the part most marketing pages get wrong. We're not going to write "no anti-cheat will ever flag an overlay." That would be a guarantee about other companies' detection systems, and nobody outside those companies can honestly make it. What we can state are facts about architecture: there is no memory read, no input injection, and no process hook for an anti-cheat to detect, because none of those code paths exist. Peranima lives in the same category as a Discord-style overlay or a browser window open beside your game — software that runs next to your game, not inside it.

Minecraft is different — the honest part

One Peranima integration works through a different mechanism, and it deserves its own section rather than fine print.

In Minecraft, the companion doesn't watch from the outside. A bot client joins your world as an actual second player: you open your single-player Java world via "Open to LAN," and the companion connects the way a friend on your local network would — then mines, gathers, and fights alongside you. Nothing is installed into Minecraft and your game files are untouched, but there is a second player standing in your world, and that changes which question you should ask.

In your own LAN world, that's the end of the story. It's your world; the bot is your guest. Vanilla single-player has no anti-cheat and no rules except yours.

On someone else's multiplayer server, the rules aren't yours anymore. Many public servers prohibit bot clients, automation, or extra accounts — regardless of how politely the bot behaves — and that is entirely the server owner's call to make. If you ever bring the companion onto a public server, read that server's rules first. We say the same thing in the FAQ of our own comparison page, because it's true.

Note that these are two different gatekeepers, and keeping them straight is most of the answer. Anti-cheat (Vanguard, EAC, BattlEye) is software that detects tampering with a game's process — it is not what governs a Minecraft bot. Server rules are human policy about which clients may connect — they are exactly what governs a Minecraft bot.

The bottom line

Worried about your main account? Peranima runs beside your game, not inside it — no memory reads, no injected inputs, no process hooks, screenshots only when you ask. Worried about Minecraft? In your own LAN world you're fine by construction; on a public server the server's rules decide, so check them before you connect. That's the whole honest answer — no asterisks hiding underneath.