Add Codex Arena PvP bot with multibox support and HeroAI combat

[Copilot]

Implements automated Codex Arena PvP gameplay for 4-account multibox teams. Bot detects arena type, locates enemy spawn, navigates to enemy location, and uses HeroAI for automatic combat targeting.

Implementation

Core Logic (Bots/Codex_PvP_Bot.py)

• detect_arena_and_spawns(): Identifies map ID and calculates spawn coordinates from agent allegiances
• wait_for_arena_entry(): Monitors map transitions from outpost (796) to arena instances
• navigate_to_enemies(): Auto-paths to enemy location using existing pathfinding
• engage_combat(): Waits in combat area while HeroAI handles targeting and combat
• handle_loss_or_victory(): Detects outpost return and increments match counter

Spawn Detection

• Team spawn: Average position of all allied agents
• Enemy spawn: Average of visible enemies, or map boundary estimation if none visible

Match Flow

def codex_pvp_match_routine(bot: Botting) -> Generator:
    yield from wait_for_arena_entry(bot)
    map_id, team_spawn, enemy_spawn = detect_arena_and_spawns()
    yield from navigate_to_enemies(bot, enemy_spawn)
    yield from engage_combat(bot)  # HeroAI handles targeting
    yield from handle_loss_or_victory(bot)

Combat System

• Uses HeroAI (upkeep_hero_ai_active=True) for automatic targeting
• HeroAI targets enemy players and hostile henchmen in PvP
• No manual targeting logic required - multibox helper system manages combat
• Bot navigates to combat area and lets HeroAI handle all targeting and skill usage

Multibox Coordination

• Party management via bot.Multibox.InviteAllAccounts()
• All accounts run identical logic synchronously
• HeroAI handles combat for coordinated team fights

UI

• Real-time status: match count, arena name, spawn coordinates
• Supports 10 known arena maps (308, 314, 318, 319, 322, 339, 340, 343, 353, 354)

Files

• Bots/Codex_PvP_Bot.py: 318 lines, main implementation
• Bots/Codex_PvP_Bot_README.md: User documentation with setup, troubleshooting, technical details

Original prompt

make a bot that plays the Codex PvP mode in Guild Wars1. We will use the multi box library and run with four accounts. The issue is that codex has different random arenas. Once in the arena the bot will need to detect the arena, detect the players team/spawn location, then move on a path to the other teams location to kill them. It should also be able to handle a loss, where we are reset back to the Codex Arena outpost.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Ewoog]

@copilot what information do you need from me to complete this project? (MapIDs, Paths, Coords)

[Copilot]

@copilot what information do you need from me to complete this project? (MapIDs, Paths, Coords)

The current implementation uses dynamic detection and auto-pathing, which should work for basic functionality. However, to make the bot more reliable and efficient, the following information would be helpful for each Codex arena:

For each arena (308, 314, 318, 319, 322, 339, 340, 343, 353, 354):

1. Team Spawn Coordinates - Exact starting positions for each team (e.g., Red team spawn, Blue team spawn)

   • Format: (x, y) coordinates

2. Enemy Spawn Coordinates - Where the opposing team spawns

   • Format: (x, y) coordinates

3. Optimal Paths - Predefined waypoint paths from team spawn to enemy spawn

   • Format: [(x1, y1), (x2, y2), (x3, y3), ...] like in other bots
   • This avoids pathing errors and ensures efficient routes

4. Strategic Positions (optional) - Key positions for combat advantage

   • Choke points, high ground, flag locations (if applicable)

5. Map-Specific Notes (optional)

   • Obstacles to avoid
   • Best engagement positions
   • Arena layout quirks

Example format needed:

ARENA_DATA = {
    308: {  # Ascalon Arena
        "name": "Ascalon Arena",
        "team_spawns": {"red": (x1, y1), "blue": (x2, y2)},
        "paths": {
            "red_to_blue": [(x1, y1), (x3, y3), ..., (x2, y2)],
            "blue_to_red": [(x2, y2), (x4, y4), ..., (x1, y1)]
        }
    },
    # ... other arenas
}

Without this data, the bot will continue using:

• Dynamic spawn detection from ally/enemy positions
• Auto-pathing system (which may have issues in PvP arenas)
• Estimated enemy locations from map boundaries

Which specific arenas do you want to prioritize? I can update the bot to use predefined data once you provide coordinates for one or more arenas.

[Ewoog]

@copilot for ease of use, can we removing the targeting and combat logic and just use the Multibox helper in the Botting class. HeroAI now targets players and hostile henchman so it would work here.

[Copilot]

@copilot for ease of use, can we removing the targeting and combat logic and just use the Multibox helper in the Botting class. HeroAI now targets players and hostile henchman so it would work here.

Done in commit 455f107. Changes made:

1. Switched to HeroAI: Changed from upkeep_auto_combat_active=True to upkeep_hero_ai_active=True
2. Simplified combat logic: Removed all manual targeting code (GetEnemyAttacking, distance calculations, approach logic)
3. Updated engage_combat(): Now just waits in the combat area while HeroAI handles all targeting and skill usage
4. Updated documentation: README now reflects that HeroAI handles combat against enemy players and henchmen

The bot now:

• Navigates to enemy spawn area
• Waits there while HeroAI automatically targets and fights enemies
• Still handles death checks and match end detection
• Uses multibox helper system as intended

This makes the code cleaner and leverages HeroAI's PvP targeting capabilities.