Jump to content
  • [Bug] World Delay spikes drastically when AI Playerbot engages in combat


    mmlong
    • Main Category: Core / Mangos Daemon
      Sub-Category: Core Crash
      Version: 22.x (Current Master Branch)

    Description:
    When I enable the AI Playerbot module and command a bot to attack a creature, the server's World Delay spikes drastically (reaching 2000ms+), causing severe lag and stuttering.

    Steps to reproduce:

    1. Enable AI Playerbots.

    2. Summon a bot (.bot add <name>).

    3. Engage in combat with any creature.

    4. Check the server console (server info), and the World Delay will skyrocket from ~10ms to over 2000ms.

    Environment:

    • Core Version: Mangos One v0.22 (Built on 2026-09-02, Commit: b208357)

    • OS: Windows (x64)

    • Hardware: i5-14400 (The CPU usage is not maxed out, but the main thread seems to be blocked).

    • Bots: Only 1 bot is active.

    • Config: MapUpdateThreads = 4, mmap.enabled = 1

    Additional Context:
    The server runs perfectly fine when no bots are in combat. However, the moment the bot enters combat, the entire world freezes for a few seconds. There are no continuous error logs spamming the console. It seems like the 2010-era ike3 Playerbot AI logic is blocking the main map update thread when it tries to calculate combat actions (possibly pathfinding or spell casting).


    User Feedback

    Recommended Comments

    mmlong

    Posted

    • Environment: Mangos One v0.22 (Commit b208357, built on 2026-09-02)

    • Symptom: When a Playerbot enters combat, the server's World Delay spikes to over 2000ms. The core runs extremely smoothly (0-1ms) when the bots are idle.

    • Evidence:

      1. The startup log shows Playerbot: Using configuration file playerbot.conf, but there is absolutely no VMap support included message.

      2. The mangosd.conf lacks the vmap.enableLOS and vmap.enableHeight options.

      3. Providing extracted vmaps folder to the DataDir has no effect, meaning the core was compiled without VMap support.

    • Hypothesis: The old Playerbots module aggressively calls IsWithinLOSInMap() or similar VMap-dependent functions. Since the core lacks VMap support, it fails silently or returns false, causing the bot AI to break into a main-thread blocking loop.



    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use