Version Updates
FXNook Vendor Guide
Download Vendor Guide (PDF)
Updates & Version Rules
Vendors are responsible for maintaining their products after approval. This page explains how updates work, how versions should be managed, and when re-verification is required.
Why Updates Matter
- Fix bugs and technical issues
- Maintain compatibility with MT4 / MT5 updates
- Improve stability or logic (without misleading changes)
- Protect customer experience
Version Numbering Rules
| Update Type | Example Version | Verification Required |
|---|---|---|
| Bug Fix | v1.0 → v1.1 | No (Quick Check) |
| Minor Improvement | v1.1 → v1.2 | Partial Review |
| New Features | v1.x → v2.0 | Full Review |
| Strategy Change | Any → New Major | Mandatory Full Review |
How to Submit an Update
- Upload new compiled file (.ex4 / .ex5)
- Keep FXNook Licensing unchanged
- Update version number clearly
- Add a clear changelog
- Do not remove existing features without notice
Best Practice
Keep updates backward compatible whenever possible. Breaking changes should be released as a new major version.
When Re-Verification Is Required
- Core trading or calculation logic changes
- Risk or money management changes
- Licensing behavior changes
- Performance claims updated
Warning
Uploading major changes without declaring them may result in delisting or temporary suspension.
Impact on Existing Customers
- Updates are provided to existing customers automatically
- License validity remains unchanged
- Major changes must be clearly communicated
Need Full Rules?
Refer to the complete Vendor Guide for update and compliance policies.