Hello everyone,

I’d love to work with the community to develop Trading System 3.0.

At the moment, this system is based on a single M2 timeframe, without considering other timeframes. However, the histograms use four timeframes, which is why I’m asking for help in understanding how to create a "4-in-1" solution and refine the code.

This system can be described as a "traffic light" system (referring to the histograms), and it’s important to remember that the highest timeframe in the group of four multi-timeframe (MTF) instances of a single oscillator dominates over all the others (this is basic knowledge, but worth reiterating).

My goal is to make this system as mechanical as possible, eliminating the need for overthinking or subjective interpretations. I’m not sure if the community is interested in this project, but I’d like to gauge whether we can all collaborate on defining the ultimate strategy.

For me, trading should be simple. The challenge lies in aligning the right confluences to tip the statistical odds in our favor. I see confluences like players in a soccer team: when they work together functionally toward a common goal—rather than individual glory—they achieve greatness. Think of Ranieri’s Leicester, Guardiola’s Barcelona, Luis Enrique’s PSG, Lippi’s early Juventus or etc.

This, I believe, should be everyone’s objective: simplifying trading and making it as mechanical as possible. Let’s work together on this 3.0 project and strive to improve it. My motivation isn’t personal glory—it’s about making a real difference for as many people as possible.

For now, I’d like to showcase the potential of this project with some screenshots, calling it "Magnum Opus Alchemicum." Its success will depend on you—because what I see may not be immediately clear to others.

Key components of this system are MTF histogram oscillators (preferably non-repainting) and a few select indicators for stronger confirmation.

I look forward to reading your thoughts and collaborating!

Best regards,
Thoth

Thank you for reaching out and inviting the community to collaborate on Trading System 3.0. It’s great to see your initiative and openness to work together on this project.

I want to mention that only a few members here have coding experience, so it might be a challenge to tackle the technical aspects quickly. However, we’ll do our best to support you however we can.

Could you please share the specific indicators you’re using and the current template? That way, those with coding skills will have a clearer idea of what needs to be improved and how we can move forward as a team.

Marco_Sousa wrote: Tue Jul 15, 2025 6:36 am Thank you for reaching out and inviting the community to collaborate on Trading System 3.0. It’s great to see your initiative and openness to work together on this project.....

Hello Mauro_Sousa. Thank you for your response. All of you are important and fundamental to the development of new trading systems. In my opinion, there are no "A-team" or "B-team" categories—everyone's contribution, whether in programming or testing, is crucial to improving a system. I strongly believe in the potential of this project and hope that we’ll support each other to make it the best one yet, without diminishing the value of other projects in the forum. I’ve borrowed elements that best fit "objective mechanical confluences" for this purpose.

Today, I don’t think I’ll manage to finish, as I’m still testing some indicators and want to create the best possible base package. It should be ready for testing tomorrow or within the next few days.

Quick update: I replaced a 4-in-1 oscillator with two independent ones for further testing.

Over time, I’ll also try to develop something for cTrader. Theoretically, apart from The Oracle—which is a complex system and impossible to reverse-engineer (By reverse engineering I mean carrying out a series of reasonings to understand the logic and therefore carrying out, precisely, reverse engineering and not decompilation)—I should be able to port other codes.
Best regards,
Thoth