Re: Settings files vs hardcoded inputs: managing EA parameters across accounts
Posted: Sat Oct 31, 2026 2:45 pm
Naming set files clearly saves a lot of confusion. Including the EA name, the symbol, the account type and the date in the file name means you can tell at a glance which settings are which. Something like EA_EURUSD_raw_2026-10.set is much better than settings_final_v2.set. When you have several accounts and several versions, a good naming convention is the difference between loading the right file and loading last month's test settings onto a live account by mistake. That mistake is surprisingly easy to make on a busy morning. A short readme next to the set files, saying which account uses which, helps too.