4. Nexus Configurator — Complete Guide
Using the Visual Configurator to set up every parameter
4.1 Overview
The Visual Configurator is a Windows desktop application that provides
a graphical interface for all 226+ parameters. Changes are written to config.json
which is read by NexusServer on startup or after saving. You do not need to restart the EA for
most setting changes.
config.json file
that NexusServer reads from the same directory.4.2 Telegram Tab — Detailed Guide
Enter API credentials
API ID (number) and API Hash (string) from my.telegram.org. See Section 1.4 for full instructions.
Phone number verification
Enter your number in international format (+country code). Wait for the Telegram verification code via SMS or in-app message.
Add channels
Use the "+" button to add channels. For public channels, use @username. For private channels, use the numeric ID (get it by forwarding a message to @userinfobot).
Configure per-channel options
Click each channel to configure: Pre-Signal templates, Force Symbol settings, enable/disable status.
4.3 Symbol Mapping Tab
Use the Global profile for mappings that apply to all accounts. Create account-specific profiles for brokers with different symbol naming conventions.
The Force Symbol If Missing toggle is also found here — enable it and set the target symbol for channels that don't include instrument names in their signals.
4.4 TP Profiles Tab
Create named TP close profiles (e.g., "Conservative 25/25/25/25", "Aggressive 50/50") and assign them to specific channels. When Use Server TP Profiles is enabled in the EA, it applies the matching profile instead of the local TP configuration.
4.5 Saving & Applying Configuration
Click "Save" in the Configurator
Writes all current settings to config.json.
NexusServer picks up changes
NexusServer detects the file change and reloads configuration automatically — no restart required.
EA continues without interruption
Changes to signal parsing and channel settings take effect immediately. EA input changes (risk, grid, protection) require reattaching the EA or using the Configurator to update the EA's config.json-linked settings.