Serious bug with Fibo retracement

[l'andorrà]

I was testing fibo retracement for the first time and I found a serious bug. When a fibo is manually used on a chart, levels are wronly identified. This is the case I was studying:

https://fxdreema.com/shared/VO9IWEwKc

I created a manual fibo with the name you can see in block 3.

If that condition is true, a vertical line is plotted. Well, this is what I got:

The condition is clearly false but the line is plotted. I tried the opposite way (the correct one) so that candle ID 0's close was below level 100 and no vertical line is plotted.

Am I really the first one to find this terrible bug?

[roar]

@l-andorrà I dont know about fibonaccis, but the reason here might also be that the EA doesnt find the object and returns value 0. Zero is always below candle close.

Get 100% proof by putting the fibo in a comment block, so that you see what level its referring to

[l'andorrà]

@roar What do you exactly mean? How can a put a fibo in a comment block?

[roar]

@l-andorrà just like any other block

[l'andorrà]

@roar You are right. I get value 0. How can the object be found?

[roar]

@l-andorrà dont know, honestly. I've always found objects a bit buggy and unnecessary...

[seb 0]

@l-andorrà
I think you are just using fibo parameters wrongly. As you can see fibo levels are between 0 and 32. It is the ID if each level, not the value it self. So if the reference level is 100%, try to set : Property = price by level ; Fibonacci level = 6.
Level 100 doesn't exists thats probably why it returns a 0 value.

[l'andorrà]

@seb-0 I didn't know that. You're right, I was using the wrong value. However, the bug is still there, I'm afraid. This is the new EA:

https://fxdreema.com/shared/yeRbOdW1b

And this is the wrong result I get:

The Fibo value is correctly identified in the 'Comment' block. However, the condition block is true but apparently fxDreema doesn't identify it correctly.

Any other idea?

[roar]

@l-andorrà I think you want this option from the drop-down

[l'andorrà]

@roar You're right. I chose the wrong option. I confirm there ir no bug after all, LOL XD. Thank you very much to both of you.