How modlaboratory/languageadder works
LanguageAdder is an Among Us plugin for loading user-authored languages and hard-coded text replacement rules. Players trigger example generation and configuration reload with hotkeys; the plugin reads language folders, adds language-menu choices, applies translations and replacements, and can migrate legacy configuration. The graph covers the sampled runtime and documented configuration workflow; unsampled implementation details are omitted.
Main entry points: LanguageManager.cs Language manager · Main.cs Plugin entry · KeyboardListener.cs Hotkey listener · Patch.cs Game patches
Components 9
Plugin startup
- Plugin entry
sources/Main.cs - Hotkey listener
sources/KeyboardListener.cs - Plugin metadata
sources/PluginInfo.cs
Language configuration
- Data paths
sources/ModConstants.cs - Language manager
sources/LanguageManager.cs
Game integration
- Game patches
sources/Patch.cs
Other components
- Player
- Among Us runtime
- Language_Data files
Connections 10
- Plugin entry → Hotkey listener: registers
sources/Main.cs - Plugin entry → Plugin metadata: uses metadata
sources/Main.cs - Player → Hotkey listener: presses hotkeys
- Hotkey listener → Language manager: requests generation or reload
sources/KeyboardListener.cs - Among Us runtime → Game patches: triggers patched hooks
sources/Patch.cs - Game patches → Language manager: selects and reads translations
sources/Patch.cs - Language manager → Data paths: uses data paths
sources/LanguageManager.cs - Language manager → Language_Data files: reads and writes configurations
sources/LanguageManager.cs - Language manager → Game patches: uses vanilla buttons
sources/LanguageManager.cs - Language manager → Plugin entry: logs status
sources/LanguageManager.cs