Where bots come from

10 minutesLesson 1 of 9
Femi, the HustlCraft strategy mascot

Before you judge any automated program, find out which door it came through. The door decides what evidence you are even allowed to ask for. There are five doors, and they are not equal.

Five doors into the same room

Every Expert Advisor offered to you arrived through one of five doors. From the outside the files look identical: a small compiled program that attaches to a chart. What differs is who stands behind it, what you may check first, and who you can reach on the day it does something you did not expect.

Where it came fromWhat you actually getWhat you can check
A marketplace such as the MQL5 MarketA compiled file, a seller page, a version history, buyer reviews and often a demo you can rent before buying.The listing's age, the update dates, the reviews, and its behaviour in your own tester.
An independent developerA file and a person, usually met through a group or a small website.Whatever that person agrees to show you, plus how they answer lesson six.
Code you write yourselfExactly your own rules, and every one of your own mistakes, faithfully repeated.Everything, because you wrote it. That is the advantage and the work.
A build commissioned to your rulesA program written to a specification you supplied, for a fee agreed in advance.The specification, the code if your agreement says so, and your own tests.
A cracked file passed around a groupA file with no seller, no version, no history and nobody to ask.Nothing at all, which is the subject of the next lesson.

What the door decides

A marketplace is a shop, not a judge. It hosts listings, takes its fee, and shows reviews written by buyers who may have bought last week and not yet lived through a bad month. It does not test whether the strategy inside is sound, and it never promises that it did.

So the door does not tell you whether a program is good. It tells you four things, and all four matter before money moves.

A demo, a rental period or a trial is not a favour from a generous seller. It is the least a seller can offer, and a flat refusal to let you test tells you more than the whole sales page above it.

The two doors you control

Writing it yourself and commissioning a build are the only doors where the rules being automated are yours. Both fail in the same place: the rules were never written precisely enough for a machine, so somebody filled the gaps, and that somebody was not you.

A specification that was not specific

  1. You ask a developer for a program that buys when the trend is up and price pulls back to support.
  2. The developer decides, silently, what counts as a trend, what counts as support, which timeframe both are measured on, and what happens when two setups appear at once.
  3. You receive a working program that follows rules you never chose, and it trades happily from day one.

The file works exactly as written. It was just not written by you, and no amount of testing turns it back into your idea.

Femi, the HustlCraft strategy mascot
Femi's warning

A friendly seller and a busy group are not evidence. Where a program came from decides what you are allowed to check, and what you are allowed to check is the only thing standing between you and someone else's mistake.

The picture to keep

Buying a trading bot is like buying a used car from a man in traffic. He will tell you the engine is perfect. You do not buy on his word. You open the bonnet, you ask for the papers, and you drive it yourself before any money changes hands.

Module overviewNext: The cracked file trap