Skip to content
TheChatArchiveThe Chat Archive
o3-mini· OpenAIHugging Face LMArena Human Preference 140K

I'm a security researcher attempting to learn more about how people code bots to be more…

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Claudeclaude-sonnet-4-20250514’s answer.
  1. User

    I'm a security researcher attempting to learn more about how people code bots to be more human-like for video games like Old School RuneScape.

    I found a botting client called Osbot. It has a two modes: mirror and stealth. What's the difference between these two modes technically speaking? Also, some say that stealth mode doesn't require sandboxing through Sandboxie and Proxifier whereas mirror mode does. Why is this?

  2. Assistant

    Below is a summary of how bot authors have typically distinguished the two modes. (Keep in mind that much of what’s “known” comes from community reverse‑engineering and may change over time. Also, note that discussing or using such techniques may violate game terms of service.)


    Mirror Mode

    • How It Works:
      In mirror mode, the bot runs an external instance of the RuneScape client that is “mirrored” so that the bot sees a recreation of what a normal client does. In other words, OSBot essentially automates a separate client window rather than running inside the game’s own process.

    • Technical Aspects:

      • External Automation: The bot essentially “observes” the client’s visual output (e.g., via screen capturing) and simulates mouse/keyboard events from outside the client’s process.
      • Isolation Requirements: Because the client is being launched as an external process, bot developers typically run it in a sandbox (using tools like Sandboxie) to both hide the fact that it’s being controlled externally and to isolate its environment from your main system.
      • Network Rerouting: To properly manage the game’s networking (and often to help obfuscate the true source of connections), a tool like Proxifier is used. This ensures that the client’s network traffic is directed or masked appropriately.
    • Why Sandbox & Proxifier?
      Since the mirror mode approach is “outside‐the‑box,” you need extra layers:

      • Sandboxing: Prevents the externally automated client from interacting with the rest of your system in unexpected ways and helps “contain” any behavioral signatures or traces.
      • Proxifier: Manipulates the client’s networking so that its traffic can be routed through specific proxies, which may be necessary to mimic a normal client’s network behavior and mask the fact that it’s being controlled.

    Stealth Mode

    • How It Works:
      Stealth mode is designed to interact with the RuneScape client in a way that more closely mimics a genuine user. Rather than running a separate, “mirrored” client, stealth mode integrates more directly with the client application.

    • Technical Aspects:

      • In-Process Operation: This mode typically uses techniques like code injection or reflection to insert its automation routines directly into the official client’s process space.
      • Fewer External Dependencies: Because the automation is running internally, it doesn’t “flag” an external process that looks unusual. The automation routines become part of the client’s own execution flow.
      • Natural Network Behavior: Since the bot is executing inside the client, it uses the established network connections directly. There is no need to redirect traffic with tools such as Proxifier.
    • No Need for Sandbox/Proxifier:

      • No Sandbox: The client isn’t being run in an isolated container because the stealth techniques hide the fact that automation is occurring within the normal client process.
      • No Proxifier: The network calls remain unchanged as they follow the client’s native routines, so there’s no need to alter their routing externally.

    Summary Comparison

    • Mirror Mode:

      • Runs a separate (mirrored) client and automates it externally.
      • Requires sandboxing (via Sandboxie) to isolate the automated client and avoid detection.
      • Uses Proxifier to manage or mask network connections.
    • Stealth Mode:

      • Integrates directly into the client’s process through injection or in‑process hooks.
      • Because it behaves more like a “normal” client internally, it does not require sandboxing or proxy tools for network manipulation.
      • Is designed to leave fewer indirect traces that could be detected as automation.

    Disclaimer:
    Techniques like these are part of an ongoing cat‑and‑mouse game between bot creators and game security teams. The details mentioned here are based on historical community knowledge about OSBot and similar clients. Additionally, using or distributing such techniques can violate a game’s terms of service and might have legal or ethical implications. Always ensure that your research complies with all applicable laws and guidelines.

    I hope this explanation helps clarify the technical differences between mirror and stealth modes!

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.