Warner Bros. Games has released update 1.013 for LEGO Batman: Legacy of the Dark Knight on PlayStation 5, Xbox Series X/S, and PC. This patch, which arrived on November 12, 2026, introduces a new Menu Narration accessibility feature alongside platform-specific adjustments.
New Menu Narration Accessibility Feature
The primary addition in version 1.013 is the implementation of Menu Narration. This tool is designed to assist players by reading aloud menu text and UI elements. Currently, the feature is only available in English. Players can toggle this option within the accessibility settings to improve navigation across the game’s various systems and customization screens.
Platform Availability and Technical Requirements
While update 1.013 is available across all current consoles and PC, the new Menu Narration feature carries specific technical restrictions based on the platform:
- Nintendo Switch 2: Although the patch is live on the platform, Menu Narration is specifically excluded from the Switch 2 version at this time.
- PC Support: On PC, the narration feature is only supported on Windows versions of the game.
- Console Parity: The feature is fully functional on the PlayStation 5 and Xbox Series X/S versions of the game.
Additional details regarding these features can be found on the official WB Games Support page.
Reported Community Issues
While the 1.013 update focuses on accessibility, several high-priority issues continue to be reported by the community. These bugs remain active and can impact progression for those aiming for total completion:
- Tricorner Island Chest: A reported bug involves a WayneTech Chest on Tricorner Island that can disappear entirely. Because this chest is required for 100% game completion, it has become a primary concern for completionists.
- PS5 Local Co-op: Players on PlayStation 5 have specifically reported system crashes when playing in local co-op mode.
- PC Keybindings: A conflict with custom keybindings on the PC version can lead to character-switching inputs failing to register.
These issues follow concerns raised since Update 1.005, though version 1.013 does not explicitly list fixes for these specific community-reported bugs in its confirmed documentation.
