They are in fact 4 lines printed on the chart.
0_1613316388520_57ecc03e-7e3a-4d58-a38e-ff8beb9bf886-image.png
fxd_line_5_0 is the one that appears first on candle 1. Eventually id3_thirdline appers on top of it.
Well, as @miki says, there is right and wrong code in this particular situation. But the thing is that there could be a reason for "// Set variables (in)" to be at the bottom, and this is because in that Variables window you could use those P1, P2, P3 things, which are shortcuts for ObjName, ObjectType, ObjColor and the others. It's like the chicken and egg problem.
It looks that my assumption was that in the Variables window we should be able to use the Px values after they are modified. And there could be an use case where we want this, for example:
https://fxdreema.com/shared/5zi3oorD
0_1613319210950_29fdf18f-54bc-42af-b934-44854e770b51-image.png
But when I'm thinking about it, this use case is less intuitive and less possible from the one @roar stumbled upon, so I decided to fix the problem by moving "Set variables (in)" at the top. This means that the example that I'm giving above will be wrong.
I hope that this update doesn't change anyone's project, because it is always possible that someone is doing the things in the way my example works.