So it could be that you haven't put the condition-set, called 'break', in the top of your list. He hasn't explained it in my topic, but I gather it has something to do with an inner hierarchy, where condition-set#1 goes first. If none of the conditions match it will move to #2 and so forth.
That's correct. This
is actually explained in the user manual.
So the process is to compare the Property Set conditions with the current tournament conditions, starting at the top of the Property Set list and working down until a match is reached. If none is found, we use the Default (which is at the bottom of the list, in 3.0 at least). More than one Property Set may match the current tournament conditions, so once the first match is reached, we stop looking.
The reason for what you are seeing is that even during a break, the round number is still valid. That is, if Break 1 is directly after Round 3, during Break 1 the Round Number is still 3. Thus, when checking Round Number, those conditions would still match during that break. However, when checking for Break Number, the code makes sure not only that the Break Number matches, but the tournament is currently in a break as well. This is a legacy item, and I can't remember why it was not done the same way when comparing the Round Number, but I'm sure I had a reason, as I even commented the code as such (but omitted the reason in the comments; not good practice).