It is C#, not C++

Can you give a real example from the indicators? It would help to explain better.

Secondly, previous bar value comes in to play in the logic calculation, where trading signals are raised. In some custom indis you might find PBV cut out and taken into account already in the indi value calculation block.

Thirdly, if only open prices are used in the calculation, PBV is not used, in FSB PBV is automatically switched off. If, for example, there are other price points used in addition (or without open prices), PBV is a must.

Taking into account those points above, in your abstract example case nr 1 doesn't seem to need the use of PBV, but the 2nd case needs it.

Finally, I would not describe it as a "shift". It is extremely vital necessity for having a reliable and reproducible backtest result. It is a matter of using the latest confirmed datapoints! It doesn't shift, but uses latest closed values, which do not change.

Thanks for detailed answers!

Example of indicator 1) - Pinbar M (uses only Bar-1 values):
for (int iBar = 1; iBar < Bars; iBar++)
            {
                if (Math.Abs(Close[iBar - 1] - Open[iBar - 1]) < iPERCENT * 0.01 * (High[iBar - 1] - Low[iBar - 1]))
                    doji[iBar] = 1;

Example of indicator 2) - ATR (AverageTrueRange) - (uses High[bar], Low[bar]):
for (int bar = 1; bar < Bars; bar++)
            {
                atr[bar] = Math.Max(High[bar], Close[bar - 1]) - Math.Min(Low[bar], Close[bar - 1]);
            }

            atr = MovingAverage(period, 0, maMethod, atr);

Can you give a real example from the indicators? It would help to explain better.

Secondly, previous bar value comes in to play in the logic calculation, where trading signals are raised. In some custom indis you might find PBV cut out and taken into account already in the indi value calculation block.

Thirdly, if only open prices are used in the calculation, PBV is not used, in FSB PBV is automatically switched off. If, for example, there are other price points used in addition (or without open prices), PBV is a must.

Taking into account those points above, in your abstract example case nr 1 doesn't seem to need the use of PBV, but the 2nd case needs it.

Finally, I would not describe it as a "shift". It is extremely vital necessity for having a reliable and reproducible backtest result. It is a matter of using the latest confirmed datapoints! It doesn't shift, but uses latest closed values, which do not change.

I have noticed 2 different versions of indicators by C++ code:
1) Indicator [bar] = Function of O, H, L, C [bar-1, bar-2, bar-3…..]
2) Indicator [bar] = Function of O,H, L, C [bar, bar-1, bar-2, bar-3,...]

Question:
If we use UPBV=true and indicator 1): will the result be shifted by 2 bars ? (1 bar in C++ code and 1 bar by means of UPBV = true)