Conditions contain a list of statements which will be checked. The logic of the Condition only applies to the list of statements.
In an OR-Condition, only one contained statement needs to be true for the OR-Condition to return true.
In an AND-Condition every contained statement needs to be true for the AND-Condition to return true.
-> Statement 1,2 and 3 need to be true. The statements will be checked in the order as they appear in the list. If one returns false, the whole AND returns false.
-> Statement 1,2 or 3 needs to be true. The statements will be checked in the order as they appear in the list. If all return false, the OR returns false.
Every action that can contain conditions represents an AND-condition. For example while, if-then-else, ... So their list of conditions uses is connected with an AND already. So you don't need to add an AND to connect multiple statements.
I think that your problem is the "Tier", even tho I don't know what exactly it is, because I always work with the german editor and I can't find the tier condition just in the second, or the picked integer. The complete trigger would be very helpful.
Additionally you don't need extra "Or"s after each seperate condition. It just use more memory space.
And you can shorten the whole thing if you take "Math - Modulo (integer)": Tier of Player mod 10 == 1.
The issue is slightly more complex and it's caused by lazy implementation of GUI's IF and similar functions
You see in programming you can't do something like IF (A B C). You can only do IF (A and/or B and/or C).
Yet GUI allows multiple conditions without anything between them.
Question is: "What is between conditions by default". It's AND
Now Furthermore your single OR it's not actually OR in code. It is only with 2+ conditions.
OR and AND with single condition is equal to condition itself without anything. Something like OR(true) can't exist itself. As you saw before OR and AND are between conditions.