OTClient is a fully functional open-source alternative client for the MMORPG Tibia, implemented in C++20 and Lua. It is a cross-platform desktop application that renders a 2D tile-based game world using OpenGL, communicates with game servers via a custom TCP protocol (with encryption, compression, and version negotiation), and provides a rich Lua-scripted user interface built on a custom UI framework (OTML). The repository contains the complete client engine (graphics, networking, audio, input, platform abstraction), game-specific modules (action bars, minimap, market, NPC trade, skill wheel, etc.), and a significant set of bot/automation mods (cavebot, targetbot, loot system). The architecture follows a hybrid C++/Lua model where the core engine is in C++ and all game logic and UI are implemented in Lua, allowing extensive customization and module loading. While the codebase is generally well-structured with reusable components (event dispatcher, layout system, protocol abstraction), it also carries technical debt from accumulated version-specific conditionals, a large bot subsystem that may violate game terms of service, and some duplication between Lua modules.
This repository is a heavily modified fork of the RuneLite client for Old School RuneScape (OSRS), extended with a comprehensive automation and botting framework branded as 'Microbot'. The system provides a full game client with a plugin architecture, overlays, configuration system, and event bus, plus a large set of automation scripts for questing, combat, walking, banking, and inventory management. The core application is a Java desktop client using Swing, Guice dependency injection, and LWJGL for GPU rendering. Key entry points include the RuneLite main class, the Microbot plugin (which orchestrates script execution), and an HTTP agent server that exposes client state and allows remote control. The architecture is modular with composite Gradle builds for the cache, API, and client modules, but the microbot automation code is tightly coupled to game internals and relies on hardcoded IDs and reflection, making it fragile to game updates. The codebase integrates a vendored shortest-path planner (upstreamPlanner) for pathfinding, a quest helper subsystem with hundreds of quest-specific step classes, and a natural mouse movement library for human-like input simulation. External dependencies include OkHttp for network requests, Gson for serialization, and FlatLaf for UI theming. The project also includes cache-reading tools for extracting game definitions (items, NPCs, objects, interfaces, scripts) and a crowdsourcing plugin for collecting gameplay data. While the official RuneLite plugins are preserved, the majority of development effort appears focused on the automation layer, which introduces significant maintenance risk and potential policy violations.