I'm really sorry for such a delay in my response after you responded so quickly, been a bit crazy here atm.
That explains everything further, thank you so much!
However, it was almost perfect until it contradicted my main reasoning
for my questioning. But that would be my fault for having my examples
have the second condition as a sub-event.
One of the things I wanted to know was whether it would be better to
separate events with the same conditions to different areas,
as in your first example there, or whether that would reduce performance.
You explained that it was silly because it would have to check it twice,
answering me that I should keep them joined so I'll make sure to do
that in the future and keep it in mind when revising my event layout
in the current project.
Another question in my mind I tried to express, poorly, I'm sorry about that.
Was whether it would be more intensive for the project to have a large
number of sub-events under a single event, or whether it would be better
to keep them all separate and have that overall event as just another condition in each sub-event (making them main events), as is shown
in your last example.
Because you have said both in your explanation that it's better to
have it only check the condition once, but then your final example
it checks it both when global variable 1, and 2 are true alongside it.
So may I please ask, which is your preferred solution of these examples?
=========== #1 =
Event one:
Global variable = 1
Sub event one:
Sub event two:
=========== #2 =
Event one:
Global variable = 1
Global variable = 2
Event two:
Global variable = 1
Global variable = 3