Fix Fury cTrader cBot

@sdqtrades

As a seasoned developer and an automation specialist with several years of experience, I have worked extensively with cTrader's APIs and have developed numerous bots similar to Fury cBot. This gives me a deep understanding of the platform and any nuances in its updates, which is precisely what you need for this project. My skills allow me to identify deprecated or newly restricted API calls accurately, refactor or replace them as required, and deliver a well-tested, optimized bot that aligns seamlessly with your specifications. Notably, my proficiency in C# mirrors the language used in your existing codebase, which means a level of familiarity that will expedite the troubleshooting process. My approach to coding is clean, clear, optimized, and understandable - factors that facilitate efficient problem solving and seamless cooperation. I am confident that these qualities combined with my understanding of NDA requirements make me an ideal collaborator. Most importantly, I share your commitment to excellence and your drive for results that match or surpass pre-5.9.5 performance levels. As such, I will leave no stone unturned until your Fury cBot can complete an end-to-end backtest without any stalls and the expected profits are restored. Trust me not just for a quick fix but for a comprehensive resolution that provides continued efficacy for your trades. Thank you for considering my candidacy for this project. I look forward to putting my skills to work for your success!

@devbaloni1983

With over 15 years of expertise in API, C# programming and software development, I am confident that I can fix your Fury cTrader cBot issue efficiently. My extensive experience has honed my ability to identify and solve problems swiftly and accurately. Having worked with cTrader's APIs regularly, from version 5.9.4 to the most recent 5.9.10, makes me uniquely qualified to take on this task. I fully understand the urgency of getting your trading strategy back on track. Rest assured, I will conduct a thorough audit of your existing C# source code to identify any deprecated or newly restricted API calls that might be causing the issue on the latest platform versions. I will then proceed to refactor or replace these calls effectively, ensuring end-to-end functionality without any stalls during back-tests

@aktarujjamana7

As a professional Ctrader developer, i can assist you to fix it ASAP. I have 7 years of experience in Ctrader and i have completed a lot of projects here. Please send me a message to proceed.

@godesignpk

Hi there, I can help with your Fury cTrader cBot issue and ensure that the back-testing runs smoothly in the latest environment. My focus will be on auditing the existing C# code for any deprecated API calls and refactoring them to restore full functionality. I will deliver a compiled .algo along with the updated source code and release notes detailing the changes made. The bid is an opening estimate, and we can finalize the details once I understand the specific requirements and access needed. Do you have the current source code and any specific test cases you’d like to run? Best regards, Waqas & GoDesign Team

@mdabdullahallm5

I have extensive experience developing and debugging cTrader cBots across multiple platform versions, so I can systematically identify what changed between 5.9.4 and 5.9.10. I'll audit your C# source for deprecated APIs, blocking calls, or behavioral changes affecting the back-testing engine, refactor only the incompatible sections while preserving your trading logic, and validate the fix through end-to-end back-testing. You'll receive the updated source code, compiled .algo file, and concise release notes detailing every compatibility change to ensure results remain as close as possible to your original performance.

@gowthamsarathy

Hello, A cBot that compiles but freezes during back-testing is typically a compatibility issue introduced by API or runtime changes rather than a strategy problem. The goal is to isolate exactly what changed between cTrader 5.9.4 and 5.9.10, restore full back-testing functionality, and preserve the strategy's original behavior as closely as possible. Here's how I'd approach the project: I'll audit the existing C# code against the latest cTrader Automate API, focusing on deprecated calls, event handlers, data access, threading, timers, and any blocking operations that could stall the back-test engine. Since I actively trade myself, I understand the importance of reliable back-testing and consistent execution, which helps shape the overall debugging approach. After identifying the incompatibility, I'll refactor only the affected sections, validate the strategy through multiple back-tests, compare the results with your pre-5.9.5 performance, and provide release notes documenting every change. The final delivery will include the updated C# source code, compiled .algo file, testing results, release notes, and a hand-off session if you'd like to review the changes together. Relevant Work: https://www.freelancer.in/portfolio-items/11493278-algorithmic-trading-bot-for-mt5 https://www.freelancer.in/portfolio-items/11493462-nyse-and-nasdaq-algo-trading-platform https://www.freelancer.in/portfolio-items/11493491-mt4-mt5-trade-copier Kind regards, Gowtham

@rosscarter1011

hello, The single most useful clue is that the freeze is silent and only in back-testing, since live logic, compilation, and optimisation all still load. A back-test that hangs on the first tick with no error, while everything else works, almost always means the code is stuck in a loop or waiting on something that behaved differently before, a blocking call or a data-access pattern that Spotware tightened between 5.9.4 and 5.9.10. That it happens only in the historical tick loop and not live points straight at how the bot reads bars or ticks during back-testing, which is exactly the area they changed. So I would audit the source for the calls that run inside the tick handler, looking for anything now deprecated or restricted, or a wait that never resolves under the new engine, then refactor those to the current API so a full back-test completes. Since your C# is unchanged and only the platform moved, this is a version-compatibility fix rather than a strategy rewrite, so the trading logic stays intact and the results should track your pre-5.9.5 numbers. A quick screen-share to watch it freeze on your machine would let me confirm the exact stall point rather than guess. Does the back-test freeze instantly on the first tick, or run briefly then hang, since that separates an init problem from a loop issue? And can you share the source, since this is a read-the-code-then-fix job rather than one I can solve blind? have a nice day.

@toriquldev123

Hello There! I’m Md Toriqul Islam, and I’m excited to partner with you. I can dive into your project immediately. I have rich experience in C#, debugging, API compatibility, and troubleshooting existing software systems. I am skilled in C#, API migration, debugging, code refactoring, performance troubleshooting, and resolving version-specific compatibility issues. I understand you need to diagnose why your Fury cBot back-testing freezes on cTrader 5.9.10, identify API incompatibilities introduced after 5.9.4, update the existing code, and deliver the corrected source and compiled .algo. I’m ready to start immediately and would be happy to review the existing source and reproduce the back-test issue. Looking forward to hearing from you. Best regards, Md Toriqul Islam

@krupnovdenis

Hello! We can audit and fix your cBot so it back-tests correctly in the current cTrader version. 1. Can you share the current source and .algo build for review? 2. Would you like us to focus first on the backtest freeze or full compatibility cleanup? — About us We are dZENcode – a full-cycle IT company for digital product development: from design and programming to integrations and post-release support. We build projects from scratch and also work on existing solutions that need further development, improvements, or technical support. You can find detailed information about our services and rates on our official website: https://dzencode.com. Please review it – after that, we can discuss the details and agree on the next step. ⚠️ After clarifying all details, we will define the scope, the suitable cooperation format – task-based, outsourcing, or outstaffing – and the final cost. Projects are guaranteed to reach release with us: • 10+ years providing IT services; • 90+ in-house specialists; • 250+ public reviews since 2015; • We support products under SLA after launch; • We work under NDA and a company contract!

@mzdesmag

Hello sir, Did go through your job description and glad to share that I have enormous experience in working with Fix Fury cTrader cBot I'm a seasoned programmer and Engineer with quality experience in Flutter, React, Node.JS, SpringBoot, Frontend and Backend Development, Python, Matlab, R studio, C, C++, C#, OpenCV, OpenGL, Tesseract OCR, google vision, Statisticaal programming/R progamming data analysis Computing for Data Analysis Time Series & Econometric, Machine learning, AI, Deep learning, Matlab and Mathematica, 3D modeling, CAD/CAM,AutoCAD, 2D, Architectural Engineering, SolidWorks, Unity 3D, PCB, Electronics, Arduino, Automation, Embedded and Firmware , IOT, Electrical/Mechanical Engineering I am a TOP Rated Freelancer, and you can check my reviews here as well: https://www.freelancer.com/u/mzdesmag. Looking forward to potentially working together on this project. Thanks and Best regards, Adekunle.

@PINESCRIPTERR

Hi, I can audit the Fury cBot specifically for the transition from cTrader 5.9.4 to the current 5.9.10 back-testing engine, while preserving its trading rules. I would reproduce the first-tick stall with diagnostic instrumentation, then isolate the blocking path through controlled removal of indicators, event handlers, file/network access, timers, loops, symbol/timeframe requests, and asynchronous operations. The review would cover deprecated API usage, changed lifecycle behaviour, unavailable historical data, synchronous waits, thread-affinity assumptions, collection iteration, indicator initialisation, and code that behaves differently when `RunningMode` is back-testing. Any fix would be kept narrowly scoped and regression-tested against compilation, optimisation, live-mode startup, and multiple back-test date ranges. Delivery includes updated C# source, compiled `.algo`, concise release notes, and a reproducible test configuration. I would also compare trades, timestamps, and metrics against an exported pre-update baseline. Profit figures cannot be guaranteed to match exactly if Spotware changed historical data, spread modelling, fills, or the back-test engine, but any variance will be identified and explained rather than hidden. Relevant examples can be shared privately where client permissions allow. Regards, Houssame

@Algokage

Hello, I hope you're doing well. I am an experienced C# developer with a strong background in algorithmic trading and cTrader. I have successfully tackled similar issues, ensuring that strategies run smoothly across different cTrader versions. My approach involves a meticulous audit of the code, identifying and addressing any incompatibility introduced by the 5.9.4 to 5.9.10 update. I will refactor or replace deprecated API calls, ensuring the strategy's back-testing completes seamlessly in the current environment. I deliver clean, well-documented code, and I am confident that I can resolve this issue efficiently. I am ready to assist with your project. Please message me to discuss further and share relevant samples or a quick demo if needed. Thanks, Adegoke M.

@carlosd178

Hello, As a result of a detailed review of your project requirements, I fully understand the scope and expectations. I have experience debugging C# trading systems, API compatibility issues, and back-testing failures, and I’m available to start your project right away. In my opinion, the key challenge is identifying exactly what changed between cTrader 5.9.4 and 5.9.5+ that causes the Algo back-tester to stall on the first tick without generating an exception. I’ll audit the Fury cBot source for deprecated, restricted, or behaviour-changed cTrader API calls, reproduce the freeze under 5.9.10, and isolate the blocking code path before making targeted changes. I’ll keep the trading logic intact wherever possible so historical performance remains comparable to the pre-5.9.5 results. The final delivery will include the updated C# source, compiled .algo file, and concise release notes covering every compatibility change. I have a couple of quick questions. • Can you provide the original C# source and the last working .algo build? • Which symbol, timeframe, and back-test date range reliably reproduce the freeze? I would be glad to discuss further details and am ready to start immediately. Looking forward to hearing from you. Best regards, Carlos

@vashishtrupinder

I understand the cBot back-test freezes on the first tick after the cTrader update, and it's likely a deprecated API call in the code. I can audit the source against the current API and refactor what's needed so it runs cleanly on 5.9.10. I've handled similar version compatibility issues before, and I'm confident I can get it working end-to-end on your machine. Unlimited revisions until you're completely satisfied. Let me know if you'd like to start with a small piece of the demo work to see how we work together. I'm available to start immediately and would be happy to discuss your requirements in detail. Best Regards, Azad

@chiragpipal

⚠️ If you're not happy, you don’t pay. ⚠️ Hi, Thank you for checking my proposal and sharing the detailed project brief. I can audit and refactor your cBot using C# with a high-performance design tailored for cTrader 5.9.10. I will deliver: • Comprehensive audit of existing C# code for deprecated API calls • Refactoring of incompatible calls for seamless back-testing • A compiled .algo file and updated source code • Brief release notes outlining the change set You will also receive: • Ongoing support during testing • Quick revisions based on your feedback I am confident I can resolve these issues efficiently and restore back-testing functionality. Looking forward to discussing the timeline and next steps. Best regards, Chirag Pipal

@richard031596

Your Fury cBot needs a focused C# compatibility audit so it can back-test again on cTrader 5.9.10 without freezing after the first tick. I can review the existing cBot source, trace the back-test execution path, identify deprecated or restricted API usage after 5.9.4, and refactor only the affected logic so the live strategy behavior stays as close as possible to the original. I’ve worked with C# trading/automation code and version-related API fixes before, where the priority was preserving existing calculations while removing the platform-specific stall. My process would be to reproduce the freeze, inspect event handlers, indicators, market data access, timers, file/network calls, and any back-test-only paths, then deliver the updated source, compiled .algo, and short release notes. Can you provide the current C# source plus a previous 5.9.4 back-test report for comparison?

@sekai1116

As an experienced Senior Full-Stack Engineer, I am well-versed in a wide range of programming languages, including C#, and have a deep understanding of software development. This vast knowledge base makes me capable of confidently addressing the issue you are experiencing with your Fury cBot, especially since my core expertise extends to software testing and debugging. I've fixed numerous similar bugs before, so I understand the frustration and impact your current stalled back-testing has on your trading operations. My thorough approach combined with my emphasis on clean code translate to cleaner solutions and better performance - which ultimately leads to optimal profits for you. I'm confident in delivering you an updated source code and functional files that produce results reasonably close to your pre-5.9.5 figures consistently. Having little or no downtime is crucial for algorithmic trading and rest assured, your issue will be treated with utmost priority and dealt with promptly irrespective of time zones - flexibility is one of the values I treasure most in my work relationships. So let's debug and get you back on track!

@Olywebart

The issue appears tied to API changes post-5.9.4 affecting back-testing flow. I'll audit the C# source against the latest cTrader API updates focusing on deprecated or restricted calls causing the freeze. Refactoring will target stable execution during back-tests in 5.9.10 while preserving original trading logic and performance. Delivery includes updated source and compiled .algo with concise release notes. Can you provide the current source code repo or files to directly assess the cBot's API usage and incompatibilities?

@codeandcommand

Is your bot running on a self-hosted cBot or through cTrader Automate? The 5.9.5 update usually breaks things by changing the Symbol or Bars API signatures, so the fix is normally quick once I see the error log. I can start now and have it debugged and backtested within 2 days. The budget and timeline here are early estimates from the post. Once I look at the actual code and error, I will confirm real numbers, could go either way depending on what broke. Send over the log or the .algo file and I will get started.