But aren't you super scared with every trade that it is going to put on an opposite position instead of the one you were intending and which is a thousand lots off, you know, due to minor development bugs as traditional in Zorro?

EDIT:
Thanks for the suggestions on the trouble shooting with Zorro. But I recently got multicharts .net and it does not require ritual dances around a fireplace while playing drums, to perform trivial operations like downloading historical data. Super happy about it!
It's funny, but it's only after being exposed to Zorro that one realizes just how much value multicharts actually offers! Like, best advertisement for multicharts: "Give Zorro a try! You'll be sure to love multicharts." hahaha

Once the program is tested and works as intended and paper traded - then it should continue to work in a version of Zorro in which it has been developed.
I also use strategy results from MC to validate results from Zorro.

I now use MC as a database for historical data and to quickly prototype some ideas.

Soo, for things that can be traded live with MC and Zorro, which one would you choose? While EasyLanguage may be slow, C# seems fast enough though.

It is unfortunately not that simple and depends on strategies.
For robustness and speed in production - SierraChart...but it has rudimentary backtesting capabilities and nothing about portfolio-level mngt...
MC is fast (Powerlanguage gets translated to C++ and runs as fast as C#) and more or less reliable in real-time, but lacks proper WFO/ML framework (and has several other quirks and limitations)...which brings us to Zorro.

I see, I guess there is a use case for everything out there, after all... Still skeptical though. A back test and paper trading have finite extent and who knows what kind of underwater mines are lurking in the depth of code, judging by what it looks like on the surface.

I know that coding and Zorro are not for anyone, but the topic of this thread is version 1.96. You can discuss your issues all day, but please somewhere else. We also have a Rants section on this forum. Thank you!

Agree, that was not the appropriate place, sorry.

Coming back to the issues, it would be great if you expressed your opinion on the posted logs and highlighted issues.

Will IB plugin get improved in this area?

Not sure if this is already fixed, but I'm using Zorro 1.96.4 and found that the time zone CST is problematic. All other time zones (e.g. UTC, EST) work fine, just if I use CST in a date time related function call like ldow(CST, 0), I get a "syntax error".

It's not about missing definition though. If I make up something that does not exist like ldow(CCST, 0), I get "undeclared identifier".

Thanks for help in advance!

I had this too, the support told me it is fixed now. Here is how to fix it: Edit with N++ the file include\trading.h, and in line 764 with the CST definition, delete the "tr" behind the "-6".

Since no bugs have been reported, Zorro 1.96.4 is now the new release and has moved to the Download page. Of course, if you encounter any problem with the new version, just contact Support with the details.