Modification and Optimization EA

Hello,

A month ago, an expert here wrote a custom EA for me based on a special indicator.
However, as I used the EA, problems arose—both bugs and condition paradoxes.
Unnecessary and untimely BUY-SELL conditions occurred. Correct and perfect orders closed unexpectedly... etc. Anyway, I have now modified this EA a bit. Some additions were made, and conditions were adjusted based on a new indicator. Adjustments were also made to AI modules. There is a proper flowchart, and the logic is good. However, now I have some issues in MetaEditor. I suspect certain codes are not working properly. Therefore, I need an expert who can quickly identify and fix these issues in the EA.
I kept the explanations long to explain EA and reduce the number of questions. I will also share all the documents.

EA1: old version (to be attached, does not give any error in Meta Editor.)
EA2: New version (to be attached, gives 7 errors in Meta editör and need to be optimize.)
Special İndicator: no problem. Will share. “147609_SP_06”

EA Summary:

·      The special indicator Track1 determines order placement based on the upward and downward movements of L2, L3, L4 lines, triggered by L1. Orders are executed at the market price (no pending orders).

·      Sto1 and Sto2 support buy/sell conditions with K period confirmation.

·      TP, SL, Trailing Stop, and _BE_TP conditions work with a trailing stop linked to Track1 LBE.

·      The EA checks the trading days of the week and adjusts parameters based on market conditions (ATR-based).

Tasks:

1.   Fix 7 errors found in MetaEditor during compilation (detailed in Note 3 below-attached file).

2.   Debug the mode where EA works with BE_Normal and _BE_TP, ensuring indicator-based TP and SL operate correctly (detailed in Note 1 below -attached file ).

3.   Ensure that indicator and condition queries refresh on each new bar instead of every tick to optimize EA performance.

4.   Verify the 12 BUY-SELL conditions in EA2 and correct their logic if necessary (simple explanation provided in Note 2 below -attached file ).

5.   Remove unnecessary and irrelevant code (not by hiding with "//", but completely deleting them).

6.   Check and correct parameters of two Stochastic Oscillators if there are any issues.

7.   Ensure TP, SL, Trailing Stop, BE, and RiskRewardRatio formulas are correctly implemented and compatible with each other.

8.   Verify if the following condition is working correctly, and fix it if necessary:

input bool   CloseOnOppositeSignal   = false;        // Close Position on Opposite Signal

9.   Simplify the code where possible (at the developer’s discretion).

10.            Ensure all transactions are based on points, not pips.

11.            Perform general optimization.