No memory access
No Tibia process memory reading or writing.
Safety
Can TibiaNexus get you banned?
TibiaNexus is designed to stay away from the categories Tibia players worry about most: client injection, automation, memory access, client patching, and gameplay input.
Why
TibiaNexus stays outside the Tibia client.
It uses OBS Studio capture, OCR, local folders you choose, public web lookups, and external overlay windows. It does not need to hook into Tibia to work.
No automation
No botting, macros, cavebot behavior, or gameplay input.
No injection
No DLL injection or code running inside the Tibia client.
No client editing
No Tibia file patching, asset editing, or client modification.
No keystroke reading
No keylogging or reading what you type.
Data model
Local by default. Shared only when you choose.
Hunt logs and screenshots are read from folders you select. Field Reports are opt-in. Translator sends selected chat screenshots or typed text for translation when you use it.
We are confident in the design, but we do not promise zero risk.
Final policy and enforcement decisions always belong to CipSoft and BattlEye. Our confidence comes from the design choices above, not from pretending any third-party tool has a permanent guarantee.
If you want the source material, start here.
- BattlEye support says non-hack programs such as overlays are not what their bans are for. Read BattlEye support
- BattlEye's privacy policy makes clear that it inspects processes and game-related system information. Read BattlEye privacy policy
- Tibia's own BattlEye notice points players to BattlEye and CipSoft privacy documents. Read Tibia's privacy page