MQL5 doesn’t allow posting multiple "versions" of the same robot. - page 2

New comment
 
Samuel Cavalcanti Costa:

I ran into issues trying to post different versions of my robots (1.0, 2.0, 3.0, and so on). I had to reach out to support because even other robots that had nothing to do with it got taken down from the marketplace.

If we’re not allowed to post updates or versions, how do you guys go about posting multiple versions of the same robot?

MQL5 is very aggressive when it comes to "duplicate products."
If the robots look too similar in logic, settings, description, branding, or even presentation style, their moderation system can flag them as copies or reuploads - even when they're your own products.

That's why many developers don't upload "V1, V2, V3" as separate robots anymore.

Usually the better approach is:

• Keep one main product
• Push updates through version releases
• Or make the strategy genuinely different enough to justify a separate listing

Because from MQL5's perspective:
Changing a few settings or adding minor tweaks doesn’t create a "new EA."

And this is why a lot of serious developers started building brand ecosystems instead of endless cloned versions of the same bot.

Different identity.
Different logic.
Different execution profile.
Different market behavior.

Otherwise the moderation team sees it as marketplace spam and starts taking things down fast
 
Samuel Cavalcanti Costa #:

So in that case, whoever buys my current robot won’t have access to the previous version anymore?

Yes, that is my understanding based on Buyers' comments in the Forum (I've never actually purchased anything from the Market─only sold in the past).

Update notices are automatically pushed out by mql5.com. Best practice is to update the change log when posting a new version so that Buyers can make an informed decision as whether they want to update or not.  In this way, it's on the Buyer if they're not happy with an update (price can be increased as well─even for a formerly free product).

12
New comment