[BUG] - Translator uses the wrong target language after Discord startup

[nathan60107]

Describe the bug

After restarting Discord, the Translator plugin does not detect the user's language correctly.

Instead of translating messages into my configured Discord language (Traditional Chinese), it translates them into English.

Disabling and re-enabling the Translator plugin fixes the issue immediately without changing any settings.

To Reproduce

1. Restart Discord.
2. Open a channel with a message that can be translated.
3. Click Translate.
4. Observe that the translation is shown in English instead of the user's configured language (Traditional Chinese).

I've attached a video demonstrating the issue. The video shows:

• Discord is freshly restarted.
• The Translator plugin translates a message into English instead of Traditional Chinese.
• Only the Translator plugin is enabled, and no themes are enabled.
• I then disable and re-enable the Translator plugin.
• Clicking Translate again now correctly translates the message into Traditional Chinese.

Expected behavior

The Translator plugin should detect the user's configured Discord language on startup and translate messages into that language without requiring the plugin to be re-enabled.

Screenshots

2026-08-04-214129_wpaYWdSo.mp4

Discord Build (stable, ptb or canary)

## Discord Info
Stable 587597 (1a0e2d0)
Host 1.0.9250 x64 (87263)
Windows 11 64-bit (10.0.26200)

## BetterDiscord
Stable 1.13.14 (acb982f)

### 21 Plugins (1 Enabled):
- BDFDB
- APlatformIndicators
- BetterMentions
- BetterSearchPage
- ChatButtonsBegone
- ChatFilter
- enhancecodeblocks
- Hide Channels
- ImageUtilities
- JumpToTop
- LinkConverter
- MoreQuickReacts
- MoreRoleColors
- RemoveBlockedUsers (Enabled)
- StaffTag
- StartUpPage
- Translator
- FavoriteMedia
- MessageLoggerV2
- PeekMessageLinks
- ViewProfilePicture

### 3 Themes (0 Enabled):
- ClearVision V7 for BetterDiscord
- midnight (catppuccin macchiato)
- My

Additional context

The issue only occurs immediately after Discord starts. Re-enabling the Translator plugin causes it to detect the correct language, suggesting that the language may not be initialized or retrieved correctly during the plugin's startup.